From: "Li, Aubrey" <aubrey.li@linux.intel.com>
To: Qais Yousef <qais.yousef@arm.com>
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
valentin.schneider@arm.com, tim.c.chen@linux.intel.com,
linux-kernel@vger.kernel.org, Aubrey Li <aubrey.li@intel.com>,
Jiang Biao <benbjiang@gmail.com>
Subject: Re: [RFC PATCH v3] sched/fair: select idle cpu from idle cpumask for task wakeup
Date: Thu, 12 Nov 2020 20:12:01 +0800 [thread overview]
Message-ID: <713b4681-3bdb-b25c-9afb-5896ca255309@linux.intel.com> (raw)
In-Reply-To: <20201112105713.xz3f52tcvjhk7si5@e107158-lin.cambridge.arm.com>
On 2020/11/12 18:57, Qais Yousef wrote:
> On 10/21/20 23:03, Aubrey Li wrote:
>> From: Aubrey Li <aubrey.li@intel.com>
>>
>> Added idle cpumask to track idle cpus in sched domain. When a CPU
>> enters idle, its corresponding bit in the idle cpumask will be set,
>> and when the CPU exits idle, its bit will be cleared.
>>
>> When a task wakes up to select an idle cpu, scanning idle cpumask
>> has low cost than scanning all the cpus in last level cache domain,
>> especially when the system is heavily loaded.
>>
>> v2->v3:
>> - change setting idle cpumask to every idle entry, otherwise schbench
>> has a regression of 99th percentile latency.
>> - change clearing idle cpumask to nohz_balancer_kick(), so updating
>> idle cpumask is ratelimited in the idle exiting path.
>> - set SCHED_IDLE cpu in idle cpumask to allow it as a wakeup target.
>>
>> v1->v2:
>> - idle cpumask is updated in the nohz routines, by initializing idle
>> cpumask with sched_domain_span(sd), nohz=off case remains the original
>> behavior.
>
> Did you intend to put the patch version history in the commit message?
>
> I started looking at this last week but got distracted. I see you already got
> enough reviews, so my 2p is that I faced some compilation issues:
>
> aarch64-linux-gnu-ld: kernel/sched/idle.o: in function `set_next_task_idle':
> /mnt/data/src/linux/kernel/sched/idle.c:405: undefined reference to `update_idle_cpumask'
> aarch64-linux-gnu-ld: kernel/sched/fair.o: in function `nohz_balancer_kick':
> /mnt/data/src/linux/kernel/sched/fair.c:10150: undefined reference to `update_idle_cpumask'
> aarch64-linux-gnu-ld: /mnt/data/src/linux/kernel/sched/fair.c:10148: undefined reference to `update_idle_cpumask'
>
> Because of the missing CONFIG_SCHED_SMT in my .config. I think
> update_idle_cpumask() should be defined unconditionally.
Thanks to point this out timely, :), I'll fix it in the next version.
-Aubrey
prev parent reply other threads:[~2020-11-12 12:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 15:03 Aubrey Li
2020-11-03 19:27 ` Valentin Schneider
2020-11-04 11:52 ` Li, Aubrey
2020-11-06 21:22 ` Valentin Schneider
2020-11-06 7:58 ` Vincent Guittot
2020-11-09 6:05 ` Li, Aubrey
2020-11-06 21:20 ` Valentin Schneider
2020-11-09 13:40 ` Li, Aubrey
2020-11-09 15:54 ` Valentin Schneider
2020-11-11 8:38 ` Li, Aubrey
2020-11-12 10:57 ` Qais Yousef
2020-11-12 12:12 ` Li, Aubrey [this message]
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=713b4681-3bdb-b25c-9afb-5896ca255309@linux.intel.com \
--to=aubrey.li@linux.intel.com \
--cc=aubrey.li@intel.com \
--cc=benbjiang@gmail.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=qais.yousef@arm.com \
--cc=rostedt@goodmis.org \
--cc=tim.c.chen@linux.intel.com \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.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
Powered by JetHome