mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: "Song Bao Hua (Barry Song)" <song.bao.hua@hisilicon.com>,
	Valentin Schneider <valentin.schneider@arm.com>,
	Meelis Roos <mroos@linux.ee>, LKML <linux-kernel@vger.kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Mel Gorman <mgorman@suse.de>
Subject: Re: 5.11-rc4+git: Shortest NUMA path spans too many nodes
Date: Fri, 22 Jan 2021 11:05:08 +0100	[thread overview]
Message-ID: <99ecee86-8d96-c1e2-5b38-8f3dfcc38bd1@arm.com> (raw)
In-Reply-To: <353d255769b6463c862993e2329a9a8d@hisilicon.com>

On 21/01/2021 22:17, Song Bao Hua (Barry Song) wrote:
> 
> 
>> -----Original Message-----
>> From: Dietmar Eggemann [mailto:dietmar.eggemann@arm.com]
>> Sent: Friday, January 22, 2021 7:54 AM
>> To: Valentin Schneider <valentin.schneider@arm.com>; Meelis Roos
>> <mroos@linux.ee>; LKML <linux-kernel@vger.kernel.org>
>> Cc: Peter Zijlstra <peterz@infradead.org>; Vincent Guittot
>> <vincent.guittot@linaro.org>; Song Bao Hua (Barry Song)
>> <song.bao.hua@hisilicon.com>; Mel Gorman <mgorman@suse.de>
>> Subject: Re: 5.11-rc4+git: Shortest NUMA path spans too many nodes
>>
>> On 21/01/2021 19:21, Valentin Schneider wrote:
>>> On 21/01/21 19:39, Meelis Roos wrote:

[...]

>> # cat /sys/devices/system/node/node*/distance
>> 10 12 12 14 14 14 14 16
>> 12 10 14 12 14 14 12 14
>> 12 14 10 14 12 12 14 14
>> 14 12 14 10 12 12 14 14
>> 14 14 12 12 10 14 12 14
>> 14 14 12 12 14 10 14 12
>> 14 12 14 14 12 14 10 12
>> 16 14 14 14 14 12 12 10
>>
>> The '16' seems to be the culprit. How does such a topo look like?

Maybe like this:

      _________
      |       |
    .-6   0   4-.
    |  \ / \ /  |
    |   1   2   |
    |   \    \  |
    --7  3----5 |
      |  |____|_|
      |_______|

> 
> Once we get a topology like this:
> 
> 
>          +------+         +------+        +-------+       +------+
>          | node |         |node  |        | node  |       |node  |
>          |      +---------+      +--------+       +-------+      |
>          +------+         +------+        +-------+       +------+
> 
> We can reproduce this issue. 
> For example, every cpu with the below numa_distance can have 
> "groups don't span domain->span":
> node   0   1   2   3
>   0:  10  12  20  22
>   1:  12  10  22  24
>   2:  20  22  10  12
>   3:  22  24  12  10
                             2     20     2
So this should look like: 1 --- 0 ---- 2 --- 3

  reply	other threads:[~2021-01-22 10:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 13:41 Meelis Roos
2021-01-21 15:05 ` Valentin Schneider
2021-01-21 17:39   ` Meelis Roos
2021-01-21 18:21     ` Valentin Schneider
2021-01-21 18:53       ` Dietmar Eggemann
2021-01-21 21:17         ` Song Bao Hua (Barry Song)
2021-01-22 10:05           ` Dietmar Eggemann [this message]
2021-01-22 11:09             ` Song Bao Hua (Barry Song)
2021-01-22 11:16               ` Valentin Schneider

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=99ecee86-8d96-c1e2-5b38-8f3dfcc38bd1@arm.com \
    --to=dietmar.eggemann@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mroos@linux.ee \
    --cc=peterz@infradead.org \
    --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

all inboxes | Powered by JetHome®