Patch "sched/topology: Set correct NUMA topology type" has been added to the 4.18-stable tree
[email protected]
AppliedThis is a note to let you know that I've just added the patch titled
sched/topology: Set correct NUMA topology type
to the 4.18-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
sched-topology-set-correct-numa-topology-type.patch
and it can be found in the queue-4.18 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
From foo@baz Mon Oct 8 17:39:53 CEST 2018
From: Srikar Dronamraju <[email protected]>
Date: Fri, 10 Aug 2018 22:30:18 +0530
Subject: sched/topology: Set correct NUMA topology type
From: Srikar Dronamraju <[email protected]>
[ Upstream commit e5e96fafd9028b1478b165db78c52d981c14f471 ]
With the following commit:
051f3ca02e46 ("sched/topology: Introduce NUMA identity node sched domain")
the scheduler introduced a new NUMA level. However this leads to the NUMA topology on 2 node systems to not be marked as NUMA_DIRECT anymore.
After this commit, it gets reported as NUMA_BACKPLANE, because sched_domains_numa_level is now 2 on 2 node systems.
Fix this by allowing setting systems that have up to 2 NUMA levels as NUMA_DIRECT.
While here remove code that assumes that level can be 0.
--- kernel/sched/topology.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-)
kernel/sched/topology.c +1 -4
@@ -1295,7 +1295,7 @@ static void init_numa_topology_type(void n = sched_max_numa_distance; -if (sched_domains_numa_levels <=1 ) { +if (sched_domains_numa_levels <=2 ) { sched_numa_topology_type =NUMA_DIRECT ;return ; }
@@ -1380,9 +1380,6 @@ void sched_init_numa(void)break ; } -if (!level) -return ; -/* * 'level' contains the number of unique distances *
Patches currently in stable-queue which might be from [email protected] are
queue-4.18/sched-topology-set-correct-numa-topology-type.patch