From: Aubrey Li <aubrey.li@intel.com>
To: 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
Cc: tim.c.chen@linux.intel.com, linux-kernel@vger.kernel.org,
Aubrey Li <aubrey.li@intel.com>
Subject: [RFC PATCH v1 0/1] select idle cpu from idle cpumask in sched domain
Date: Thu, 10 Sep 2020 13:42:02 +0800 [thread overview]
Message-ID: <20200910054203.525420-1-aubrey.li@intel.com> (raw)
I'm writting to see if it makes sense to track idle cpus in a shared cpumask
in sched domain, then a task wakes up it can select idle cpu from this cpumask
instead of scanning all the cpus in the last level cache domain, especially
when the system is heavily loaded, the scanning cost could be significantly
reduced. The price is that the atomic cpumask ops are added to the idle entry
and exit paths.
I tested the following benchmarks on a x86 4 socket system with 24 cores per
socket and 2 hyperthreads per core, total 192 CPUs:
uperf throughput: netperf workload, tcp_nodelay, r/w size = 90
threads baseline-avg %std patch-avg %std
96 1 1.24 0.98 2.76
144 1 1.13 1.35 4.01
192 1 0.58 1.67 3.25
240 1 2.49 1.68 3.55
hackbench: process mode, 100000 loops, 40 file descriptors per group
group baseline-avg %std patch-avg %std
2(80) 1 12.05 0.97 9.88
3(120) 1 12.48 0.95 11.62
4(160) 1 13.83 0.97 13.22
5(200) 1 2.76 1.01 2.94
schbench: 99th percentile latency, 16 workers per message thread
mthread baseline-avg %std patch-avg %std
6(96) 1 1.24 0.993 1.73
9(144) 1 0.38 0.998 0.39
12(192) 1 1.58 0.995 1.64
15(240) 1 51.71 0.606 37.41
sysbench mysql throughput: read/write, table size = 10,000,000
thread baseline-avg %std patch-avg %std
96 1 1.77 1.015 1.71
144 1 3.39 0.998 4.05
192 1 2.88 1.002 2.81
240 1 2.07 1.011 2.09
kbuild: kexec reboot every time
baseline-avg patch-avg
1 1
Any suggestions are highly appreciated!
Thanks,
-Aubrey
Aubrey Li (1):
sched/fair: select idle cpu from idle cpumask in sched domain
include/linux/sched/topology.h | 13 +++++++++++++
kernel/sched/fair.c | 4 +++-
kernel/sched/topology.c | 2 +-
3 files changed, 17 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2020-09-11 16:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 5:42 Aubrey Li [this message]
2020-09-10 5:42 ` [RFC PATCH v1 1/1] sched/fair: select idle cpu from idle cpumask in sched domain Aubrey Li
2020-09-11 16:28 ` Qais Yousef
2020-09-11 23:04 ` Li, Aubrey
2020-09-11 23:16 ` Li, Aubrey
2020-09-14 10:31 ` Valentin Schneider
2020-09-14 11:08 ` Qais Yousef
2020-09-14 11:26 ` Valentin Schneider
2020-09-14 11:31 ` Qais Yousef
2020-09-13 3:59 ` Jiang Biao
2020-09-14 12:26 ` Vincent Guittot
2020-09-15 8:47 ` Jiang Biao
2020-09-15 9:23 ` Vincent Guittot
2020-09-15 13:38 ` Li, Aubrey
2020-09-14 12:32 ` Vincent Guittot
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=20200910054203.525420-1-aubrey.li@intel.com \
--to=aubrey.li@intel.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=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