From: Peter Zijlstra <peterz@infradead.org>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: Valentin Schneider <valentin.schneider@arm.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Rik van Riel <riel@surriel.com>,
Barry Song <song.bao.hua@hisilicon.com>
Subject: Re: [PATCH] sched/topology: Warn when NUMA diameter > 2
Date: Wed, 11 Nov 2020 10:31:34 +0100 [thread overview]
Message-ID: <20201111093134.GR2594@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20201111084331.GJ3371@techsingularity.net>
On Wed, Nov 11, 2020 at 08:43:31AM +0000, Mel Gorman wrote:
> On Tue, Nov 10, 2020 at 06:43:00PM +0000, Valentin Schneider wrote:
> > NUMA topologies where the shortest path between some two nodes requires
> > three or more hops (i.e. diameter > 2) end up being misrepresented in the
> > scheduler topology structures.
> >
> > This is currently detected when booting a kernel with CONFIG_SCHED_DEBUG=y
> > + sched_debug on the cmdline, although this will only yield a warning about
> > sched_group spans not matching sched_domain spans:
> >
> > ERROR: groups don't span domain->span
> >
> > Add an explicit warning for that case, triggered regardless of
> > CONFIG_SCHED_DEBUG, and decorate it with an appropriate comment.
> >
> > The topology described in the comment can be booted up on QEMU by appending
> > the following to your usual QEMU incantation:
> >
> > -smp cores=4 \
> > -numa node,cpus=0,nodeid=0 -numa node,cpus=1,nodeid=1, \
> > -numa node,cpus=2,nodeid=2, -numa node,cpus=3,nodeid=3, \
> > -numa dist,src=0,dst=1,val=20, -numa dist,src=0,dst=2,val=30, \
> > -numa dist,src=0,dst=3,val=40, -numa dist,src=1,dst=2,val=20, \
> > -numa dist,src=1,dst=3,val=30, -numa dist,src=2,dst=3,val=20
> >
> > A somewhat more realistic topology (6-node mesh) with the same affliction
> > can be conjured with:
> >
> > -smp cores=6 \
> > -numa node,cpus=0,nodeid=0 -numa node,cpus=1,nodeid=1, \
> > -numa node,cpus=2,nodeid=2, -numa node,cpus=3,nodeid=3, \
> > -numa node,cpus=4,nodeid=4, -numa node,cpus=5,nodeid=5, \
> > -numa dist,src=0,dst=1,val=20, -numa dist,src=0,dst=2,val=30, \
> > -numa dist,src=0,dst=3,val=40, -numa dist,src=0,dst=4,val=30, \
> > -numa dist,src=0,dst=5,val=20, \
> > -numa dist,src=1,dst=2,val=20, -numa dist,src=1,dst=3,val=30, \
> > -numa dist,src=1,dst=4,val=20, -numa dist,src=1,dst=5,val=30, \
> > -numa dist,src=2,dst=3,val=20, -numa dist,src=2,dst=4,val=30, \
> > -numa dist,src=2,dst=5,val=40, \
> > -numa dist,src=3,dst=4,val=20, -numa dist,src=3,dst=5,val=30, \
> > -numa dist,src=4,dst=5,val=20
> >
> > Link: https://lore.kernel.org/lkml/jhjtux5edo2.mognet@arm.com
> > Signed-off-by: Valentin Schneider <valentin.schneider@arm.com>
>
> Acked-by: Mel Gorman <mgorman@techsingularity.net>
Thanks!
prev parent reply other threads:[~2020-11-11 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 18:43 [PATCH] sched/topology: Warn when NUMA diameter > 2 Valentin Schneider
2020-11-11 8:43 ` Mel Gorman
2020-11-11 9:31 ` Peter Zijlstra [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=20201111093134.GR2594@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=riel@surriel.com \
--cc=song.bao.hua@hisilicon.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