From: Li Zefan <lizefan@huawei.com>
To: Tejun Heo <tj@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Cgroups <cgroups@vger.kernel.org>,
Containers <containers@lists.linux-foundation.org>,
Glauber Costa <glommer@parallels.com>
Subject: Re: [PATCH 09/10] cpuset: allow to keep tasks in empty cpusets
Date: Sat, 20 Apr 2013 09:22:09 +0800 [thread overview]
Message-ID: <5171EDC1.4070805@huawei.com> (raw)
In-Reply-To: <20130419205821.GA15543@mtj.dyndns.org>
On 2013/4/20 4:58, Tejun Heo wrote:
> Hello,
>
> On Fri, Apr 19, 2013 at 08:29:24PM +0800, Li Zefan wrote:
>> +static void update_tasks_cpumask_hier(struct cpuset *root_cs,
>> + bool update_root, struct ptr_heap *heap)
>> +{
>> + struct cpuset *cp;
>> + struct cgroup *pos_cgrp;
>> +
>> + if (update_root)
>> + update_tasks_cpumask(root_cs, heap);
>> +
>> + rcu_read_lock();
>> + cpuset_for_each_descendant_pre(cp, pos_cgrp, root_cs) {
>> + /* skip the whole subtree if @cp have some CPU */
>> + if (!cpumask_empty(cp->cpus_allowed)) {
>> + pos_cgrp = cgroup_rightmost_descendant(pos_cgrp);
>> + continue;
>> + }
>> +
>> + update_tasks_cpumask(cp, heap);
>> + }
>> + rcu_read_unlock();
>
> I don't think we can call update_tasks_cpumask() under
> rcu_read_lock(). It calls into set_cpus_allowed_ptr() which may
> block, so you'll probably have to punt it to a work item like how
Oh, will fix.
> migration is being done. Another approach would be converting cgroup
> to use SRCU instead, which would lessen pain on other places too. The
> only problem there would be that srcu_read_lock() is a bit more
> expensive than rcu_read_lock(). I'm not sure whether that'd show up
> in some hot path or not. Ideas?
>
I guess we can live with rcu_read_lock() for now, and see if we can
change it to srcu when other significant changes are done in all
cgroup controllers. (hierarchy support in blkcg, etc..)
next prev parent reply other threads:[~2013-04-20 1:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 12:25 [PATCH 00/10] cpuset: implement sane hierarchy behaviors Li Zefan
2013-04-19 12:25 ` [PATCH 01/10] cpuset: remove redundant check in cpuset_cpus_allowed_fallback() Li Zefan
2013-04-19 12:25 ` [PATCH 02/10] cpuset: cleanup guarantee_online_{cpus|mems}() Li Zefan
2013-04-19 12:26 ` [PATCH 03/10] cpuset: remove unnecessary variable in cpuset_attach() Li Zefan
2013-04-19 12:26 ` [PATCH 04/10] cpuset: remove cpuset_test_cpumask() Li Zefan
2013-04-19 18:27 ` Tejun Heo
2013-04-19 12:27 ` [PATCH 05/10] cpuset: don't update tasks' cpumask and nodemask in an empty cpuset Li Zefan
2013-04-19 18:36 ` Tejun Heo
2013-04-20 1:06 ` Li Zefan
2013-04-21 1:42 ` Tejun Heo
2013-04-19 12:27 ` [PATCH 06/10] cpuset: re-structure update_cpumask() a bit Li Zefan
2013-04-19 12:28 ` [PATCH 07/10] cpuset: record old_mems_allowed in struct cpuset Li Zefan
2013-04-19 12:28 ` [PATCH 08/10] cpuset: introduce effective_{cpumask|nodemask}_cpuset() Li Zefan
2013-04-19 12:29 ` [PATCH 09/10] cpuset: allow to keep tasks in empty cpusets Li Zefan
2013-04-19 20:58 ` Tejun Heo
2013-04-20 1:22 ` Li Zefan [this message]
2013-04-21 1:41 ` Tejun Heo
2013-04-19 12:29 ` [PATCH 10/10] cpuset: allow to move tasks to " Li Zefan
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=5171EDC1.4070805@huawei.com \
--to=lizefan@huawei.com \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=glommer@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--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