linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zefan Li <lizefan@huawei.com>
To: Tejun Heo <tj@kernel.org>, <hannes@cmpxchg.org>
Cc: <cgroups@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<kernel-team@fb.com>
Subject: Re: [PATCHSET] cgroup: use static_keys for subsystem enabled and on_dfl tests
Date: Fri, 18 Sep 2015 17:14:07 +0800	[thread overview]
Message-ID: <55FBD5DF.7060501@huawei.com> (raw)
In-Reply-To: <1442368285-16306-1-git-send-email-tj@kernel.org>

On 2015/9/16 9:51, Tejun Heo wrote:
> cgroup_subsys->disabled and cgroup_on_dfl() tests are likely to be
> used in hot paths and seldom change.  The former is set once during
> boot and the latter only when a controller is migrated between the
> default hierarchy and traditional ones.
>
> This patchset makes these tests static_key based and contains the
> following four patches.
>
>   0001-jump_label-make-static_key_enabled-work-on-static_ke.patch
>   0002-cgroup-implement-static_key-based-cgroup_subsys_enab.patch
>   0003-cgroup-replace-cgroup_subsys-disabled-tests-with-cgr.patch
>   0004-cgroup-replace-cgroup_on_dfl-tests-in-controllers-wi.patch
>
> 0001 is a prep patch in jump_label.  0002 adds the needed static_keys.
> 0003-0004 convert the existing usages and drop the old tests.
>
> This patchset is on top of v4.3-rc1 and is availalbe in the following
> git branch.
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git review-jump-labels
>
> diffstat follows.  Thanks.
>
>   block/blk-throttle.c           |    2
>   block/cfq-iosched.c            |    4 -
>   include/linux/cgroup-defs.h    |    1
>   include/linux/cgroup.h         |   79 +++++++---------------------
>   include/linux/hugetlb_cgroup.h |    4 -
>   include/linux/jump_label.h     |   18 +++---
>   include/linux/memcontrol.h     |    4 -
>   kernel/cgroup.c                |  113 ++++++++++++++++++++++++++++++++++++++---
>   kernel/cpuset.c                |   23 ++++----
>   mm/memcontrol.c                |    4 -
>   10 files changed, 157 insertions(+), 95 deletions(-)
>

Acked-by: Zefan Li <lizefan@huawei.com>


  parent reply	other threads:[~2015-09-18  9:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16  1:51 [PATCHSET] cgroup: use static_keys for subsystem enabled and on_dfl tests Tejun Heo
2015-09-16  1:51 ` [PATCH 1/4] jump_label: make static_key_enabled() work on static_key_true/false types too Tejun Heo
2015-09-17  8:59   ` Peter Zijlstra
2015-09-17 15:27     ` Tejun Heo
2015-09-17 15:37       ` Peter Zijlstra
2015-09-16  1:51 ` [PATCH 2/4] cgroup: implement static_key based cgroup_subsys_enabled() and cgroup_subsys_on_dfl() Tejun Heo
2015-09-16  1:51 ` [PATCH 3/4] cgroup: replace cgroup_subsys->disabled tests with cgroup_subsys_enabled() Tejun Heo
2015-09-16  1:51 ` [PATCH 4/4] cgroup: replace cgroup_on_dfl() tests in controllers with cgroup_subsys_on_dfl() Tejun Heo
2015-09-18  9:14 ` Zefan Li [this message]
2015-09-18 15:55 ` [PATCHSET] cgroup: use static_keys for subsystem enabled and on_dfl tests Tejun Heo

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=55FBD5DF.7060501@huawei.com \
    --to=lizefan@huawei.com \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=kernel-team@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.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).