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:   Fri, 31 Aug 2018 04:53:50 -0700
From:   Srikar Dronamraju <>
To:     Peter Zijlstra <>
Cc:     Ingo Molnar <>,
        LKML <>,
        Mel Gorman <>,
        Rik van Riel <>,
        Thomas Gleixner <>,
        Michael Ellerman <>,
        Heiko Carstens <>,
        Suravee Suthikulpanit <>,
        linuxppc-dev <>,
        Benjamin Herrenschmidt <>
Subject: Re: [PATCH 2/2] sched/topology: Expose numa_mask set/clear functions
 to arch

* Peter Zijlstra <> [2018-08-31 13:26:39]:

> On Fri, Aug 31, 2018 at 01:12:53PM +0200, Peter Zijlstra wrote:
> > NAK, not until you've fixed every cpu_to_node() user in the kernel to
> > deal with that mask changing.
> Also, what happens if userspace reads that information; uses libnuma and
> then you go and shift the world underneath their feet?
> > This is absolutely insane.

The topology events are suppose to be very rare.
>From whatever small experiments I have done till now, unless tasks are
bound to both cpu and memory, they seem to be coping well with topology
updates. I know things weren't optimal after a topology change but they
worked. Now after 051f3ca02e46 "Introduce NUMA identity node sched
domain", systems stall. I am only exploring at ways to keep them working
as much as they were before that commit.

Thanks and Regards
Srikar Dronamraju

Powered by blists - more mailing lists