From: Xunlei Pang <xlpang@linux.alibaba.com>
To: Vincent Guittot <vincent.guittot@linaro.org>,
Xunlei Pang <xlpang@linux.alibaba.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Jiang Biao <benbjiang@tencent.com>,
Wetp Zhang <wetp.zy@linux.alibaba.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND] sched/fair: Fix wrong cpu selecting from isolated domain
Date: Thu, 24 Sep 2020 16:54:42 +0800 [thread overview]
Message-ID: <aa06b988-e2bd-4ff9-caab-def399698bf2@linux.alibaba.com> (raw)
In-Reply-To: <CAKfTPtAgzcSZekb1D_Gm55vHpm4-9z5OyUxuoRTzx-_5icf5Ew@mail.gmail.com>
On 9/24/20 3:18 PM, Vincent Guittot wrote:
> On Thu, 24 Sep 2020 at 08:48, Xunlei Pang <xlpang@linux.alibaba.com> wrote:
>>
>> We've met problems that occasionally tasks with full cpumask
>> (e.g. by putting it into a cpuset or setting to full affinity)
>> were migrated to our isolated cpus in production environment.
>>
>> After some analysis, we found that it is due to the current
>> select_idle_smt() not considering the sched_domain mask.
>>
>> Steps to reproduce on my 31-CPU hyperthreads machine:
>> 1. with boot parameter: "isolcpus=domain,2-31"
>> (thread lists: 0,16 and 1,17)
>> 2. cgcreate -g cpu:test; cgexec -g cpu:test "test_threads"
>> 3. some threads will be migrated to the isolated cpu16~17.
>>
>> Fix it by checking the valid domain mask in select_idle_smt().
>>
>> Fixes: 10e2f1acd010 ("sched/core: Rewrite and improve select_idle_siblings())
>> Reported-by: Wetp Zhang <wetp.zy@linux.alibaba.com>
>> Reviewed-by: Jiang Biao <benbjiang@tencent.com>
>> Signed-off-by: Xunlei Pang <xlpang@linux.alibaba.com>
>
> Reviewed-by: Vincent Guittot <vincent.guittot@linaro.org>
>
Thanks, Vincent :-)
next prev parent reply other threads:[~2020-09-24 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 6:48 [PATCH RESEND] sched/fair: Fix wrong cpu selecting from isolated domain Xunlei Pang
2020-09-24 7:18 ` Vincent Guittot
2020-09-24 8:54 ` Xunlei Pang [this message]
2020-09-29 7:56 ` [tip: sched/core] " tip-bot2 for Xunlei Pang
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=aa06b988-e2bd-4ff9-caab-def399698bf2@linux.alibaba.com \
--to=xlpang@linux.alibaba.com \
--cc=benbjiang@tencent.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.org \
--cc=wetp.zy@linux.alibaba.com \
/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