Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
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
Message-Id: <20210122123943.1217-1-valentin.schneider@arm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Precedence: bulk

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