From: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
To: Preeti U Murthy <preeti@linux.vnet.ibm.com>
Cc: svaidy@linux.vnet.ibm.com, Peter Zijlstra <peterz@infradead.org>,
rjw@rjwysocki.net, lizefan@huawei.com,
Anton Blanchard <anton@samba.org>, Tejun Heo <tj@kernel.org>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@kernel.org>,
cgroups@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpusets: Make cpus_allowed and mems_allowed masks hotplug invariant
Date: Thu, 09 Oct 2014 15:12:30 +0530 [thread overview]
Message-ID: <54365886.7010506@linux.vnet.ibm.com> (raw)
In-Reply-To: <54361922.8070808@linux.vnet.ibm.com>
On 10/09/2014 10:42 AM, Preeti U Murthy wrote:
> Hi Raghu,
> remove_tasks_in_empty_cpuset() is called on the legacy hierarchy when
> the cpuset becomes empty, hence we require it. But you are right its not
> called on the default hierarchy.
My point was if legacy hierarchy follows unified hierarchy in effective
cpuset handling, we will never endup with a empty effective cpuset and
hence your patch could remove the remove_tasks_in_empty_cpuset() part
too..
next prev parent reply other threads:[~2014-10-09 9:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 14:54 Raghavendra KT
2014-10-09 5:12 ` Preeti U Murthy
2014-10-09 9:42 ` Raghavendra K T [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-08 7:07 Preeti U Murthy
2014-10-08 8:07 ` Peter Zijlstra
2014-10-08 9:37 ` Preeti U Murthy
2014-10-08 10:18 ` Peter Zijlstra
2014-10-09 8:20 ` Preeti U Murthy
2014-10-09 8:30 ` Peter Zijlstra
2014-10-09 8:32 ` Peter Zijlstra
2014-10-09 13:06 ` Tejun Heo
2014-10-09 13:47 ` Peter Zijlstra
2014-10-09 13:59 ` Tejun Heo
2015-04-02 6:56 ` Preeti U Murthy
2015-04-06 17:47 ` Tejun Heo
2015-04-09 21:13 ` Serge E. Hallyn
2015-04-10 14:14 ` Preeti U Murthy
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=54365886.7010506@linux.vnet.ibm.com \
--to=raghavendra.kt@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=rjw@rjwysocki.net \
--cc=svaidy@linux.vnet.ibm.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
Powered by JetHome