From: Peter Zijlstra <peterz@infradead.org>
To: Cheng Jian <cj.chengjian@huawei.com>
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
chenwandun@huawei.com, xiexiuqi@huawei.com, liwei391@huawei.com,
huawei.libin@huawei.com, bobo.shaobowang@huawei.com,
juri.lelli@redhat.com, vincent.guittot@linaro.org
Subject: Re: [PATCH] sched/fair: Optimize select_idle_cpu
Date: Thu, 12 Dec 2019 16:24:06 +0100 [thread overview]
Message-ID: <20191212152406.GB2827@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20191212144102.181510-1-cj.chengjian@huawei.com>
On Thu, Dec 12, 2019 at 10:41:02PM +0800, Cheng Jian wrote:
> Fixes: 1ad3aaf3fcd2 ("sched/core: Implement new approach to scale select_idle_cpu()")
The 'funny' thing is that select_idle_core() actually does the right
thing.
Copying that should work:
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 08a233e97a01..416d574dcebf 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -5828,6 +5837,7 @@ static inline int select_idle_smt(struct task_struct *p, int target)
*/
static int select_idle_cpu(struct task_struct *p, struct sched_domain *sd, int target)
{
+ struct cpumask *cpus = this_cpu_cpumask_var_ptr(select_idle_mask);
struct sched_domain *this_sd;
u64 avg_cost, avg_idle;
u64 time, cost;
@@ -5859,11 +5869,11 @@ static int select_idle_cpu(struct task_struct *p, struct sched_domain *sd, int t
time = cpu_clock(this);
- for_each_cpu_wrap(cpu, sched_domain_span(sd), target) {
+ cpumask_and(cpus, sched_domain_span(sd), p->cpus_ptr);
+
+ for_each_cpu_wrap(cpu, cpus, target) {
if (!--nr)
return si_cpu;
- if (!cpumask_test_cpu(cpu, p->cpus_ptr))
- continue;
if (available_idle_cpu(cpu))
break;
if (si_cpu == -1 && sched_idle_cpu(cpu))
next prev parent reply other threads:[~2019-12-12 15:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 14:41 Cheng Jian
2019-12-12 14:56 ` chengjian (D)
2019-12-12 15:04 ` Peter Zijlstra
2019-12-13 1:51 ` chengjian (D)
2019-12-13 8:10 ` Peter Zijlstra
2019-12-12 15:24 ` Peter Zijlstra [this message]
2019-12-12 15:44 ` Valentin Schneider
2019-12-13 9:47 ` chengjian (D)
2019-12-13 9:57 ` chengjian (D)
2019-12-13 11:28 ` Valentin Schneider
2019-12-13 12:09 ` Peter Zijlstra
2019-12-13 12:20 ` Valentin Schneider
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=20191212152406.GB2827@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bobo.shaobowang@huawei.com \
--cc=chenwandun@huawei.com \
--cc=cj.chengjian@huawei.com \
--cc=huawei.libin@huawei.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liwei391@huawei.com \
--cc=mingo@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=xiexiuqi@huawei.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®