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 v3 0/2] cpuset: Allow v2 behavior in v1 cgroup
Date: Fri, 18 Aug 2017 09:46:20 -0400 [thread overview]
Message-ID: <5081078e-fe00-dca6-92a4-c6b3d3094794@redhat.com> (raw)
In-Reply-To: <20170818112950.GC491396@devbig577.frc2.facebook.com>
On 08/18/2017 07:29 AM, Tejun Heo wrote:
> On Thu, Aug 17, 2017 at 03:33:08PM -0400, Waiman Long wrote:
>> v2->v3:
>> - Change the generic CGRP_ROOT_V2_MODE flag to a cpuset specific
>> CGRP_ROOT_CPUSET_V2_MODE flag.
>>
>> 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
> Waiman, patches look good to me but can you please take care of the
> kbuild warnings on 32bit and maybe merge the two patches into one?
The kbuild warning is in the __init code of the v1 patch for checking
the boot time argument. The __init code was gone in the v3 patch. So if
there is no further kbuild warning after a couple of days, I think it
should be OK.
Cheers,
Longman
prev parent reply other threads:[~2017-08-18 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 19:33 Waiman Long
2017-08-17 19:33 ` [PATCH v3 1/2] cgroup: Add mount flag to enable cpuset to use " Waiman Long
2017-08-17 19:33 ` [PATCH v3 2/2] cpuset: Allow " Waiman Long
2017-08-18 15:25 ` Tejun Heo
2017-08-18 11:29 ` [PATCH v3 0/2] " Tejun Heo
2017-08-18 13:46 ` Waiman Long [this message]
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=5081078e-fe00-dca6-92a4-c6b3d3094794@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®