lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 21 Aug 2018 04:02:58 -0700
From:   Srikar Dronamraju <>
To:     Peter Zijlstra <>,
        Ingo Molnar <>
Cc:     LKML <>,
        Mel Gorman <>,
        Rik van Riel <>,
        Thomas Gleixner <>,
        Michael Ellerman <>,
        Heiko Carstens <>,
        Suravee Suthikulpanit <>,
        Andre Wild <>,
        linuxppc-dev <>
Subject: Re: [PATCH 1/2] sched/topology: Set correct numa topology type

* Srikar Dronamraju <> [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
> While here remove a code that assumes level can be 0.
> Fixes: 051f3ca02e46 "Introduce NUMA identity node sched domain"
> Signed-off-by: Srikar Dronamraju <>
> ---

Hey Peter,

Did you look at these two patches?

Thanks and Regards
Srikar Dronamraju

Powered by blists - more mailing lists