From: Yicong Yang <yangyicong@hisilicon.com>
To: <peterz@infradead.org>, <mingo@redhat.com>,
<juri.lelli@redhat.com>, <vincent.guittot@linaro.org>,
<tim.c.chen@linux.intel.com>, <gautham.shenoy@amd.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Cc: <dietmar.eggemann@arm.com>, <rostedt@goodmis.org>,
<bsegall@google.com>, <bristot@redhat.com>,
<prime.zeng@huawei.com>, <yangyicong@hisilicon.com>,
<jonathan.cameron@huawei.com>, <ego@linux.vnet.ibm.com>,
<srikar@linux.vnet.ibm.com>, <linuxarm@huawei.com>,
<21cnbao@gmail.com>, <song.bao.hua@hisilicon.com>,
<guodong.xu@linaro.org>
Subject: [PATCH v2 0/2] sched/fair: Wake task within the cluster when possible
Date: Wed, 26 Jan 2022 16:09:45 +0800 [thread overview]
Message-ID: <20220126080947.4529-1-yangyicong@hisilicon.com> (raw)
This is the follow-up work to support cluster scheduler. Previously
we have added cluster level in the scheduler for both ARM64[1] and
X86[2] to support load balance between clusters to bring more memory
bandwidth and decrease cache contention. This patchset, on the other
hand, takes care of wake-up path by giving CPUs within the same cluster
a try before scanning the whole LLC to benefit those tasks communicating
with each other.
[1] 778c558f49a2 ("sched: Add cluster scheduler level in core and related Kconfig for ARM64")
[2] 66558b730f25 ("sched: Add cluster scheduler level for x86")
Change since v1:
- regain the performance data based on v5.17-rc1
- rename cpus_share_cluster to cpus_share_resources per Vincent and Gautham, thanks!
Barry Song (2):
sched: Add per_cpu cluster domain info and cpus_share_resources API
sched/fair: Scan cluster before scanning LLC in wake-up path
include/linux/sched/sd_flags.h | 7 ++++++
include/linux/sched/topology.h | 8 +++++-
kernel/sched/core.c | 12 +++++++++
kernel/sched/fair.c | 46 +++++++++++++++++++++++++++++++---
kernel/sched/sched.h | 2 ++
kernel/sched/topology.c | 15 +++++++++++
6 files changed, 85 insertions(+), 5 deletions(-)
--
2.24.0
next reply other threads:[~2022-01-26 8:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 8:09 Yicong Yang [this message]
2022-01-26 8:09 ` [PATCH v2 1/2] sched: Add per_cpu cluster domain info and cpus_share_resources API Yicong Yang
2022-01-27 15:26 ` Gautham R. Shenoy
2022-01-26 8:09 ` [PATCH v2 2/2] sched/fair: Scan cluster before scanning LLC in wake-up path Yicong Yang
2022-01-27 1:14 ` Tim Chen
2022-01-27 2:02 ` Yicong Yang
2022-01-27 2:30 ` Tim Chen
2022-01-27 2:36 ` Tim Chen
2022-01-27 3:05 ` Yicong Yang
2022-01-27 15:41 ` Gautham R. Shenoy
2022-01-27 20:21 ` Barry Song
2022-01-28 7:13 ` Srikar Dronamraju
2022-01-27 18:40 ` Barry Song
2022-02-01 9:38 ` Srikar Dronamraju
2022-02-01 20:20 ` Barry Song
2022-02-04 7:33 ` Srikar Dronamraju
2022-02-04 10:28 ` Barry Song
2022-02-04 10:49 ` Barry Song
2022-02-04 17:41 ` Tim Chen
2022-02-05 17:16 ` Chen Yu
2022-02-06 0:26 ` Barry Song
2022-02-07 15:14 ` Gautham R. Shenoy
2022-02-08 5:42 ` Barry Song
2022-02-16 9:12 ` Barry Song
2022-02-16 9:19 ` Song Bao Hua (Barry Song)
2022-02-16 10:00 ` Yicong Yang
2022-02-17 18:00 ` Tim Chen
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=20220126080947.4529-1-yangyicong@hisilicon.com \
--to=yangyicong@hisilicon.com \
--cc=21cnbao@gmail.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=ego@linux.vnet.ibm.com \
--cc=gautham.shenoy@amd.com \
--cc=guodong.xu@linaro.org \
--cc=jonathan.cameron@huawei.com \
--cc=juri.lelli@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=prime.zeng@huawei.com \
--cc=rostedt@goodmis.org \
--cc=song.bao.hua@hisilicon.com \
--cc=srikar@linux.vnet.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).