From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Li Zefan <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
Balbir Singh <bsingharora@gmail.com>
Subject: [GIT PULL] cgroup fixes for v4.8-rc4
Date: Tue, 30 Aug 2016 11:57:42 -0400 [thread overview]
Message-ID: <20160830155742.GA12660@htj.duckdns.org> (raw)
Hello, Linus.
Two fixes for cgroup.
* There still was a hole in enforcing cpuset rules, fixed by Li.
* Recent switch to global percpu_rwseom for threadgroup locking
revealed a couple issues in how percpu_rwsem is implemented and used
by cgroup. Balbir found that the read locking section was too wide
unnecessarily including operations which can often depend on IOs.
With percpu_rwsem updates (coming through a different tree) and
reduction of read locking section, all the reported locking latency
issues, including the android one, are resolved.
It looks like we can keep global percpu_rwsem locking for now. If
there actually are cases which can't be resolved, we can go back to
more complex per-signal_struct locking.
Thanks.
The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc:
Linux 4.8-rc1 (2016-08-07 18:18:00 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-4.8-fixes
for you to fetch changes up to 568ac888215c7fb2fabe8ea739b00ec3c1f5d440:
cgroup: reduce read locked section of cgroup_threadgroup_rwsem during fork (2016-08-17 09:54:52 -0400)
----------------------------------------------------------------
Balbir Singh (1):
cgroup: reduce read locked section of cgroup_threadgroup_rwsem during fork
Zefan Li (1):
cpuset: make sure new tasks conform to the current config of the cpuset
kernel/cpuset.c | 15 +++++++++++++++
kernel/fork.c | 4 ++--
2 files changed, 17 insertions(+), 2 deletions(-)
--
tejun
reply other threads:[~2016-08-30 15:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160830155742.GA12660@htj.duckdns.org \
--to=tj@kernel.org \
--cc=bsingharora@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).