From: Waiman Long <longman@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: Li Zefan <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] cgroup: Add a hint to allow v1 controller to use v2 behavior
Date: Thu, 17 Aug 2017 14:56:03 -0400 [thread overview]
Message-ID: <bbc17fa5-3321-39a0-a98b-b57ed0381fb9@redhat.com> (raw)
In-Reply-To: <20170817184844.GB491396@devbig577.frc2.facebook.com>
On 08/17/2017 02:48 PM, Tejun Heo wrote:
> Hello, Waiman.
>
> On Thu, Aug 17, 2017 at 02:25:38PM -0400, Waiman Long wrote:
>> For some cgroup controllers, the behavior on cgroup v1 differs somewhat
>> from cgroup v2. To indicate that a controller can use v2 behavior
>> in cgroup v1, a new cgroupfs mount option "v2_mode" is added. This
>> is essentially a hint, there is no obligation for a controller to
>> comply with this semantics.
> Heh, I don't think we can make it a generic flag. We can't have one
> kernel interpreting the option one way and later kernels doing
> differently. Let's just make it cpuset specific - something like
> cpuset_v2_mode.
>
> Thanks.
>
That is fine for me. I will update the patchset accordingly.
Thanks,
Longman
next prev parent reply other threads:[~2017-08-17 18:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 18:25 [PATCH v2 0/2] cpuset: Allow v2 behavior in v1 cgroup Waiman Long
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 [this message]
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=bbc17fa5-3321-39a0-a98b-b57ed0381fb9@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
all inboxes | Powered by JetHome®