public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zefan Li <lizefan@huawei.com>
To: Waiman Long <longman@redhat.com>, Tejun Heo <tj@kernel.org>,
	"Johannes Weiner" <hannes@cmpxchg.org>,
	Jonathan Corbet <corbet@lwn.net>
Cc: <linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] cpuset: Allow v2 behavior in v1 cgroup
Date: Wed, 16 Aug 2017 09:20:27 +0800	[thread overview]
Message-ID: <59939DDB.8010205@huawei.com> (raw)
In-Reply-To: <1502818040-9967-1-git-send-email-longman@redhat.com>

On 2017/8/16 1:27, Waiman Long wrote:
> Cpuset v2 has some valuable attributes that are not present in
> v1 because of backward compatibility concern. One of that is the
> restoration of the original cpu and memory node mask after a hot
> removal and addition event sequence.
> 
> This patch adds a new kernel command line option "cpuset_v2_mode=" to
> allow cpuset to have v2 behavior in a v1 cgroup when using a non-zero
> value. This enables users to optionally enable cpuset v2 behavior if
> they choose to.
> 
> Signed-off-by: Waiman Long <longman@redhat.com>

I have no strong objection. I have received quite a few requests for
this in the past, and some were from other departments in my company.

  reply	other threads:[~2017-08-16  1:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15 17:27 [PATCH] cpuset: Allow v2 behavior in v1 cgroup Waiman Long
2017-08-16  1:20 ` Zefan Li [this message]
2017-08-16 14:29 ` Tejun Heo
2017-08-16 14:34   ` Waiman Long
2017-08-16 14:36     ` Tejun Heo
2017-08-16 14:39       ` Waiman Long
2017-08-17 21:05 ` kbuild test robot
2017-08-17 21:14 ` kbuild test robot

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=59939DDB.8010205@huawei.com \
    --to=lizefan@huawei.com \
    --cc=corbet@lwn.net \
    --cc=hannes@cmpxchg.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.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