From: Valentin Schneider <valentin.schneider@arm.com>
To: "chengjian (D)" <cj.chengjian@huawei.com>,
Peter Zijlstra <peterz@infradead.org>
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: Fri, 13 Dec 2019 11:28:00 +0000 [thread overview]
Message-ID: <6d188305-66ab-81cf-6340-34d155dcaf3b@arm.com> (raw)
In-Reply-To: <d40ac385-626f-e86f-b2cb-69adf10a193a@huawei.com>
On 13/12/2019 09:57, chengjian (D) wrote:
>
> in select_idle_smt()
>
> /*
> * Scan the local SMT mask for idle CPUs.
> */
> static int select_idle_smt(struct task_struct *p, int target)
> {
> int cpu, si_cpu = -1;
>
> if (!static_branch_likely(&sched_smt_present))
> return -1;
>
> for_each_cpu(cpu, cpu_smt_mask(target)) {
> if (!cpumask_test_cpu(cpu, p->cpus_ptr))
> continue;
> if (available_idle_cpu(cpu))
> return cpu;
> if (si_cpu == -1 && sched_idle_cpu(cpu))
> si_cpu = cpu;
> }
>
> return si_cpu;
> }
>
>
> Why don't we do the same thing in this function,
>
> although cpu_smt_present () often has few CPUs.
>
> it is better to determine the 'p->cpus_ptr' first.
>
>
Like you said the gains here would probably be small - the highest SMT
count I'm aware of is SMT8 (POWER9). Still, if we end up with both
select_idle_core() and select_idle_cpu() using that pattern, it would make
sense IMO to align select_idle_smt() with those.
>
>
>
next prev parent reply other threads:[~2019-12-13 20:36 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
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 [this message]
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=6d188305-66ab-81cf-6340-34d155dcaf3b@arm.com \
--to=valentin.schneider@arm.com \
--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=peterz@infradead.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®