mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: xunlei <xlpang@linux.alibaba.com>
To: Jiang Biao <benbjiang@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Wetp Zhang <wetp.zy@linux.alibaba.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched/fair: Fix wrong cpu selecting from isolated domain
Date: Tue, 25 Aug 2020 17:27:42 +0800	[thread overview]
Message-ID: <495238bd-ea0d-56c6-4a9c-7b18deafcc8f@linux.alibaba.com> (raw)
In-Reply-To: <CAPJCdBnTm0=Nazi2w9a6mBcKNv=_66UwvMfTNg6vLNKqW6qfwQ@mail.gmail.com>

On 2020/8/25 下午2:37, Jiang Biao wrote:
> On Mon, 24 Aug 2020 at 20:31, 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.
>>
>> 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>
>> Signed-off-by: Xunlei Pang <xlpang@linux.alibaba.com>
>> ---
>>  kernel/sched/fair.c | 9 +++++----
>>  1 file changed, 5 insertions(+), 4 deletions(-)
>>
>> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
>> index 1a68a05..fa942c4 100644
>> --- a/kernel/sched/fair.c
>> +++ b/kernel/sched/fair.c
>> @@ -6075,7 +6075,7 @@ static int select_idle_core(struct task_struct *p, struct sched_domain *sd, int
>>  /*
>>   * Scan the local SMT mask for idle CPUs.
>>   */
>> -static int select_idle_smt(struct task_struct *p, int target)
>> +static int select_idle_smt(struct task_struct *p, struct sched_domain *sd, int target)
>>  {
>>         int cpu;
>>
>> @@ -6083,7 +6083,8 @@ static int select_idle_smt(struct task_struct *p, int target)
>>                 return -1;
>>
>>         for_each_cpu(cpu, cpu_smt_mask(target)) {
>> -               if (!cpumask_test_cpu(cpu, p->cpus_ptr))
>> +               if (!cpumask_test_cpu(cpu, p->cpus_ptr) ||
>> +                   !cpumask_test_cpu(cpu, sched_domain_span(sd)))
> Maybe the following change could be better, :)
> for_each_cpu_and(cpu, cpu_smt_mask(target), sched_domain_span(sd))
> keep a similar style with select_idle_core/cpu, and could reduce loops.
> 

I thought that, but given that smt mask is usually small, the original
code may run a bit faster?

> Just an option.
> Reviewed-by: Jiang Biao <benbjiang@tencent.com>
> 

Thanks :-)

  reply	other threads:[~2020-08-25  9:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 12:30 Xunlei Pang
2020-08-24 13:38 ` Srikar Dronamraju
2020-08-25  2:11   ` xunlei
2020-08-25  2:59     ` Srikar Dronamraju
2020-08-25  6:37 ` Jiang Biao
2020-08-25  9:27   ` xunlei [this message]
2020-08-25 12:46     ` Jiang Biao
2020-08-28  2:53 ` 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=495238bd-ea0d-56c6-4a9c-7b18deafcc8f@linux.alibaba.com \
    --to=xlpang@linux.alibaba.com \
    --cc=benbjiang@gmail.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

all inboxes | Powered by JetHome®