Messages in this thread | | | Date | Tue, 21 Aug 2018 15:59:49 +0200 | From | Peter Zijlstra <> | Subject | Re: [PATCH 1/2] sched/topology: Set correct numa topology type |
| |
On Tue, Aug 21, 2018 at 04:02:58AM -0700, Srikar Dronamraju wrote: > * Srikar Dronamraju <srikar@linux.vnet.ibm.com> [2018-08-10 22:30:18]: > > > With commit 051f3ca02e46 ("sched/topology: Introduce NUMA identity node > > sched domain") scheduler introduces an new numa level. However this > > leads to numa topology on 2 node systems no more marked as NUMA_DIRECT. > > After this commit, it gets reported as NUMA_BACKPLANE. This is because > > sched_domains_numa_level is now 2 on 2 node systems. > > > > Fix this by allowing setting systems that have upto 2 numa levels as > > NUMA_DIRECT. > > > > While here remove a code that assumes level can be 0. > > > > Fixes: 051f3ca02e46 "Introduce NUMA identity node sched domain" > > Signed-off-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com> > > --- > > Hey Peter, > > Did you look at these two patches?
Nope, been on holidays and the inbox is an even bigger mess than normal. I'll get to it, eventually :/
| |