From: Valentin Schneider <valentin.schneider@arm.com>
To: Aubrey Li <aubrey.li@linux.intel.com>
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, mgorman@techsingularity.net,
qais.yousef@arm.com, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com,
tim.c.chen@linux.intel.com, linux-kernel@vger.kernel.org,
Aubrey Li <aubrey.li@intel.com>, Mel Gorman <mgorman@suse.de>,
Jiang Biao <benbjiang@gmail.com>
Subject: Re: [RFC PATCH v4] sched/fair: select idle cpu from idle cpumask for task wakeup
Date: Wed, 18 Nov 2020 12:06:36 +0000 [thread overview]
Message-ID: <jhjlfeyx41f.mognet@arm.com> (raw)
In-Reply-To: <20201116200428.47359-1-aubrey.li@linux.intel.com>
On 16/11/20 20:04, Aubrey Li wrote:
> From: Aubrey Li <aubrey.li@intel.com>
>
> Add idle cpumask to track idle cpus in sched domain. When a CPU
> enters idle, if the idle driver indicates to stop tick, this CPU
> is set in the idle cpumask to be a wakeup target. And if the CPU
> is not in idle, the CPU is cleared in idle cpumask during scheduler
> tick to ratelimit idle cpumask update.
>
> 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.
>
> Benchmarks were tested on a x86 4 socket system with 24 cores per
> socket and 2 hyperthreads per core, total 192 CPUs. Hackbench and
> schbench have no notable change, uperf has:
>
> uperf throughput: netperf workload, tcp_nodelay, r/w size = 90
>
> threads baseline-avg %std patch-avg %std
> 96 1 0.83 1.23 3.27
> 144 1 1.03 1.67 2.67
> 192 1 0.69 1.81 3.59
> 240 1 2.84 1.51 2.67
>
> Cc: Mel Gorman <mgorman@suse.de>
> Cc: Vincent Guittot <vincent.guittot@linaro.org>
> Cc: Qais Yousef <qais.yousef@arm.com>
> Cc: Valentin Schneider <valentin.schneider@arm.com>
> Cc: Jiang Biao <benbjiang@gmail.com>
> Cc: Tim Chen <tim.c.chen@linux.intel.com>
> Signed-off-by: Aubrey Li <aubrey.li@linux.intel.com>
That's missing a v3 -> v4 change summary
next prev parent reply other threads:[~2020-11-18 12:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 20:04 [RFC PATCH v4] sched/fair: select idle cpu from idle cpumask for task wakeup Aubrey Li
2020-11-18 12:06 ` Valentin Schneider [this message]
2020-11-19 1:13 ` Li, Aubrey
2020-11-18 13:36 ` Vincent Guittot
2020-11-19 1:34 ` Li, Aubrey
2020-11-19 8:19 ` Vincent Guittot
2020-11-19 11:41 ` Li, Aubrey
2020-11-22 14:03 ` [sched/fair] 8d86968ac3: hackbench.throughput 51.7% improvement kernel test robot
2020-11-25 9:09 ` [sched/fair] 8d86968ac3: netperf.Throughput_tps -29.5% regression kernel test robot
2020-11-26 6:57 ` Li, Aubrey
2020-11-26 12:13 ` Mel Gorman
2020-12-02 14:29 ` Li, Aubrey
2020-12-02 14:29 ` Li, Aubrey
2020-12-02 14:48 ` Mel Gorman
2020-12-02 14:48 ` Mel Gorman
2020-12-02 16:22 ` Vincent Guittot
2020-12-02 16:22 ` 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=jhjlfeyx41f.mognet@arm.com \
--to=valentin.schneider@arm.com \
--cc=aubrey.li@intel.com \
--cc=aubrey.li@linux.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=mgorman@techsingularity.net \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.