linux-kernel - Re: [REGRESSION] sched/fair: Reimplement NEXT

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <58a80940-a104-4932-a2f2-f0c6a1a205af@linux.ibm.com>
Date: Mon, 5 Jan 2026 20:08:17 +0530
From: Shrikanth Hegde <sshegde@...ux.ibm.com>
To: Ryan Roberts <ryan.roberts@....com>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org,
        Aishwarya TCV <Aishwarya.TCV@....com>,
        Dietmar Eggemann <dietmar.eggemann@....com>,
        Mel Gorman <mgorman@...hsingularity.net>,
        "Peter Zijlstra (Intel)" <peterz@...radead.org>
Subject: Re: [REGRESSION] sched/fair: Reimplement NEXT_BUDDY to align with
 EEVDF goals


Hi Ryan,

>> node distances:
>> node   0   1
>>    0:  10  20
>>    1:  20  10
>>
>> Whereas I assume the Graviton3 has 64 CPUs (cores) flat in a single MC
>> domain? I guess topology has influence in benchmark numbers here as well.
> 
> I can't easily enable scheduler debugging right now (which I think is needed to
> get this info directly?). But that's what I'd expect, yes. lscpu confirms there
> is a single NUMA node and topology for cpu0 gives this if it helps:

If you dump /proc/schedstat it should give you topology info as well.

(you will need to parse it depending on which CPU you are looking this from)