The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Waiman Long <longman@redhat.com>
To: Tejun Heo <tj@kernel.org>, Li Zefan <lizefan@huawei.com>,
	Johannes Weiner <hannes@cmpxchg.org>
Cc: linux-kernel@vger.kernel.org, Waiman Long <longman@redhat.com>
Subject: [PATCH v2 0/2] cpuset: Allow v2 behavior in v1 cgroup
Date: Thu, 17 Aug 2017 14:25:37 -0400	[thread overview]
Message-ID: <1502994339-21668-1-git-send-email-longman@redhat.com> (raw)

v1->v2:
 - Drop the kernel command line option and use cgroupfs mount option
   instead to enable v2 controller behavior in v1 cgroup.

v1: https://lkml.org/lkml/2017/8/15/570

This patchset adds a new cgroupfs mount option "v2_mode" that serves
as a hint that a v1 controller can use v2 hehavior, if applicable.
The cpuset controller is then modified to observe this mode.

Patch 1 adds the v1 cgroupfs mount option "v2_mode" which set a flag
in the cgroup_root flags.

Patch 2 modifies the cpuset controller to check the cgroup_root flag
and switch to v2 behavior even in a v1 cgroup.

Waiman Long (2):
  cgroup: Add a hint to allow v1 controller to use v2 behavior
  cpuset: Allow v2 behavior in v1 cgroup

 include/linux/cgroup-defs.h |  5 +++++
 kernel/cgroup/cgroup-v1.c   |  6 ++++++
 kernel/cgroup/cpuset.c      | 33 ++++++++++++++++++++-------------
 3 files changed, 31 insertions(+), 13 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2017-08-17 18:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17 18:25 Waiman Long [this message]
2017-08-17 18:25 ` [PATCH v2 1/2] cgroup: Add a hint to allow v1 controller to use v2 behavior Waiman Long
2017-08-17 18:48   ` Tejun Heo
2017-08-17 18:56     ` Waiman Long
2017-08-17 18:25 ` [PATCH v2 2/2] cpuset: Allow v2 behavior in v1 cgroup Waiman Long

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=1502994339-21668-1-git-send-email-longman@redhat.com \
    --to=longman@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --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