linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valentin Schneider <valentin.schneider@arm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, peterz@infradead.org,
	vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
	morten.rasmussen@arm.com, mgorman@suse.de,
	song.bao.hua@hisilicon.com
Subject: [PATCH 0/1] sched/topology: NUMA distance deduplication
Date: Fri, 22 Jan 2021 12:39:42 +0000	[thread overview]
Message-ID: <20210122123943.1217-1-valentin.schneider@arm.com> (raw)

Hi folks,

As pointed out by Barry in [1], there are topologies out there that struggle to
go through the NUMA distance deduplicating sort. Included patch is something
I wrote back when I started untangling this distance > 2 mess.

It's only been lightly tested on some array of QEMU-powered topologies I keep
around for this sort of things. I *think* this works out fine with the NODE
topology level, but I wouldn't be surprised if I (re)introduced an off-by-one
error in there. 

@Barry feel free to test / edit this as you see fit.

[1]: http://lore.kernel.org/r/9d6c6d3ba6ac4272bf844034da4653fe@hisilicon.com

HTH.


Valentin Schneider (1):
  sched/topology: Make sched_init_numa() use a set for the deduplicating
    sort

 include/linux/topology.h |  1 +
 kernel/sched/topology.c  | 99 +++++++++++++++++++---------------------
 2 files changed, 49 insertions(+), 51 deletions(-)

--
2.27.0


             reply	other threads:[~2021-01-22 12:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 12:39 Valentin Schneider [this message]
2021-01-22 12:39 ` [PATCH 1/1] sched/topology: Make sched_init_numa() use a set for the deduplicating sort Valentin Schneider
2021-01-25  2:23   ` Song Bao Hua (Barry Song)
2021-01-25  9:26     ` Valentin Schneider
2021-01-25 16:45       ` Valentin Schneider
2021-01-25 21:35         ` Song Bao Hua (Barry Song)
2021-01-28 14:47           ` Valentin Schneider
2021-01-29  2:02             ` Song Bao Hua (Barry Song)
2021-02-01 12:03               ` Valentin Schneider
2021-02-01  9:53   ` Dietmar Eggemann
2021-02-01 10:19     ` Vincent Guittot
2021-02-01 10:35     ` Song Bao Hua (Barry Song)
2021-02-01 11:55     ` Valentin Schneider
2021-02-02 10:03     ` [tip: sched/core] sched/topology: Fix sched_domain_topology_level alloc in sched_init_numa() tip-bot2 for Dietmar Eggemann
2021-02-17 13:17     ` tip-bot2 for Dietmar Eggemann
2021-03-17 19:04 [PATCH 0/1] sched/topology: NUMA distance deduplication John Paul Adrian Glaubitz
2021-03-17 19:36 ` Valentin Schneider
2021-03-17 19:47   ` John Paul Adrian Glaubitz
2021-03-17 20:04     ` Valentin Schneider
2021-03-17 20:56       ` Valentin Schneider
2021-03-17 23:26         ` John Paul Adrian Glaubitz
2021-03-18 10:28           ` John Paul Adrian Glaubitz
2021-03-18 10:48             ` Valentin Schneider
2021-03-17 21:14       ` Sergei Trofimovich
2021-03-17 21:58         ` Anatoly Pugachev
2021-03-17 23:29         ` John Paul Adrian Glaubitz

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=20210122123943.1217-1-valentin.schneider@arm.com \
    --to=valentin.schneider@arm.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@kernel.org \
    --cc=morten.rasmussen@arm.com \
    --cc=peterz@infradead.org \
    --cc=song.bao.hua@hisilicon.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).