From: Zefan Li <lizefan@huawei.com>
To: Jason Low <jason.low2@hp.com>
Cc: Tejun Heo <tj@kernel.org>, Peter Zijlstra <peterz@infradead.org>,
<linux-kernel@vger.kernel.org>, <cgroups@vger.kernel.org>,
<aswin@hp.com>, <scott.norton@hp.com>, <chegu_vinod@hp.com>
Subject: Re: [RFC][PATCH] cpuset, sched: Fix cpuset sched_relax_domain_level
Date: Fri, 30 Jan 2015 12:13:16 +0800 [thread overview]
Message-ID: <54CB04DC.3090405@huawei.com> (raw)
In-Reply-To: <1422478025.4111.31.camel@j-VirtualBox>
On 2015/1/29 4:47, Jason Low wrote:
> The cpuset.sched_relax_domain_level can control how far we do
> immediate load balancing on a system. However, it was found on recent
> kernels that echo'ing a value into cpuset.sched_relax_domain_level
> did not reduce any immediate load balancing.
>
> The reason this occurred was because the update_domain_attr_tree() traversal
> did not update for the "top_cpuset". This resulted in nothing being changed
> when modifying the sched_relax_domain_level parameter.
>
> This patch was able to address that problem by having update_domain_attr_tree()
> allowing updates for the root (top_cpuset) in the cpuset traversal.
>
> Signed-off-by: Jason Low <jason.low2@hp.com>
Thanks for finding this bug!
Please Add:
Cc: <stable@vger.kernel.org> # 3.9+
Fixes: fc560a26acce ("cpuset: replace cpuset->stack_list with cpuset_for_each_descendant_pre()")
I'll prepare a different fix for 3.10.y when this patch hits mainline.
> ---
> kernel/cpuset.c | 12 +++++++-----
> 1 files changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/kernel/cpuset.c b/kernel/cpuset.c
> index 64b257f..0f58c54 100644
> --- a/kernel/cpuset.c
> +++ b/kernel/cpuset.c
> @@ -541,15 +541,17 @@ update_domain_attr(struct sched_domain_attr *dattr, struct cpuset *c)
> }
>
> static void update_domain_attr_tree(struct sched_domain_attr *dattr,
> - struct cpuset *root_cs)
> + struct cpuset *root_cs, bool update_root)
> {
> struct cpuset *cp;
> struct cgroup_subsys_state *pos_css;
>
> rcu_read_lock();
> cpuset_for_each_descendant_pre(cp, pos_css, root_cs) {
> - if (cp == root_cs)
> - continue;
I don't think this fix is correct. We should simply remove these two lines,
and no other changes are needed.
> + if (cp == root_cs) {
> + if (!update_root)
> + continue;
> + }
>
> /* skip the whole subtree if @cp doesn't have any CPU */
> if (cpumask_empty(cp->cpus_allowed)) {
> @@ -644,7 +646,7 @@ static int generate_sched_domains(cpumask_var_t **domains,
> dattr = kmalloc(sizeof(struct sched_domain_attr), GFP_KERNEL);
> if (dattr) {
> *dattr = SD_ATTR_INIT;
> - update_domain_attr_tree(dattr, &top_cpuset);
> + update_domain_attr_tree(dattr, &top_cpuset, true);
> }
> cpumask_copy(doms[0], top_cpuset.effective_cpus);
>
> @@ -752,7 +754,7 @@ restart:
> if (apn == b->pn) {
> cpumask_or(dp, dp, b->effective_cpus);
> if (dattr)
> - update_domain_attr_tree(dattr + nslot, b);
> + update_domain_attr_tree(dattr + nslot, b, false);
>
> /* Done with this partition */
> b->pn = -1;
>
next prev parent reply other threads:[~2015-01-30 4:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 20:47 [RFC][PATCH] cpuset, sched: Fix cpuset sched_relax_domain_level Jason Low
2015-01-30 4:13 ` Zefan Li [this message]
2015-01-30 18:35 ` Jason Low
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=54CB04DC.3090405@huawei.com \
--to=lizefan@huawei.com \
--cc=aswin@hp.com \
--cc=cgroups@vger.kernel.org \
--cc=chegu_vinod@hp.com \
--cc=jason.low2@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=scott.norton@hp.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