From: Meelis Roos <mroos@linux.ee>
To: Barry Song <song.bao.hua@hisilicon.com>,
valentin.schneider@arm.com, vincent.guittot@linaro.org,
mgorman@suse.de, mingo@kernel.org, peterz@infradead.org,
dietmar.eggemann@arm.com, morten.rasmussen@arm.com,
linux-kernel@vger.kernel.org
Cc: linuxarm@openeuler.org, xuwei5@huawei.com,
liguozhu@hisilicon.com, tiantao6@hisilicon.com,
wanghuiqiang@huawei.com, prime.zeng@hisilicon.com,
jonathan.cameron@huawei.com, guodong.xu@linaro.org
Subject: Re: [PATCH v2] sched/topology: fix the issue groups don't span domain->span for NUMA diameter > 2
Date: Wed, 3 Feb 2021 13:57:35 +0200 [thread overview]
Message-ID: <d3ec7706-6560-70dd-d968-26460ce0c666@linux.ee> (raw)
In-Reply-To: <20210203111201.20720-1-song.bao.hua@hisilicon.com>
03.02.21 13:12 Barry Song wrote:
> kernel/sched/topology.c | 85 +++++++++++++++++++++++++----------------
> 1 file changed, 53 insertions(+), 32 deletions(-)
>
> diff --git a/kernel/sched/topology.c b/kernel/sched/topology.c
> index 5d3675c7a76b..964ed89001fe 100644
> --- a/kernel/sched/topology.c
> +++ b/kernel/sched/topology.c
This one still works on the Sun X4600-M2, on top of v5.11-rc6-55-g3aaf0a27ffc2.
Performance-wise - is the some simple benhmark to run to meaure the impact? Compared to what - 5.10.0 or the kernel with the warning?
drop caches and time the build time of linux kernel with make -j64?
--
Meelis Roos
next prev parent reply other threads:[~2021-02-03 11:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 11:12 [PATCH v2] sched/topology: fix the issue groups don't span domain->span for NUMA diameter > 2 Barry Song
2021-02-03 11:57 ` Meelis Roos [this message]
2021-02-03 21:31 ` Song Bao Hua (Barry Song)
2021-02-09 12:55 ` Peter Zijlstra
2021-02-09 20:58 ` Song Bao Hua (Barry Song)
2021-02-10 11:21 ` Peter Zijlstra
2021-02-10 12:27 ` Song Bao Hua (Barry Song)
2021-02-11 19:55 ` Valentin Schneider
2021-02-18 9:17 ` [Linuxarm] " Song Bao Hua (Barry Song)
2021-02-18 12:40 ` Valentin Schneider
2021-02-18 22:07 ` Song Bao Hua (Barry Song)
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=d3ec7706-6560-70dd-d968-26460ce0c666@linux.ee \
--to=mroos@linux.ee \
--cc=dietmar.eggemann@arm.com \
--cc=guodong.xu@linaro.org \
--cc=jonathan.cameron@huawei.com \
--cc=liguozhu@hisilicon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=prime.zeng@hisilicon.com \
--cc=song.bao.hua@hisilicon.com \
--cc=tiantao6@hisilicon.com \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=wanghuiqiang@huawei.com \
--cc=xuwei5@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;
as well as URLs for NNTP newsgroup(s).