[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f1f02718-c7e7-f6b3-be7b-3d7c2f2ffa50@redhat.com>
Date: Mon, 23 Apr 2018 12:32:12 -0400
From: Waiman Long <longman@...hat.com>
To: Mike Galbraith <efault@....de>, Tejun Heo <tj@...nel.org>,
Li Zefan <lizefan@...wei.com>,
Johannes Weiner <hannes@...xchg.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>
Cc: cgroups@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, kernel-team@...com, pjt@...gle.com,
luto@...capital.net, torvalds@...ux-foundation.org,
Roman Gushchin <guro@...com>,
Juri Lelli <juri.lelli@...hat.com>
Subject: Re: [PATCH v7 0/5] cpuset: Enable cpuset controller in default
hierarchy
On 04/20/2018 04:23 AM, Mike Galbraith wrote:
> On Thu, 2018-04-19 at 09:46 -0400, Waiman Long wrote:
>> v7:
>> - Add a root-only cpuset.cpus.isolated control file for CPU isolation.
>> - Enforce that load_balancing can only be turned off on cpusets with
>> CPUs from the isolated list.
>> - Update sched domain generation to allow cpusets with CPUs only
>> from the isolated CPU list to be in separate root domains.
> I haven't done much, but was able to do a q/d manual build, populate
> and teardown of system/critical sets on my desktop box, and it looked
> ok. Thanks for getting this aboard the v2 boat.
>
> -Mike
Thank for the testing.
Cheers,
Longman
Powered by blists - more mailing lists