linux-kernel - Re: Off topic: Numactl "distance" wrong

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 3 Apr 2009 14:52:21 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Yinghai Lu <yhlu.kernel@...il.com>
cc:	Andi Kleen <andi@...stfloor.org>, Chris Worley <worleys@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Off topic: Numactl "distance" wrong

On Fri, 3 Apr 2009, Yinghai Lu wrote:

> acpi_numa_slit_init() in srat_64.c will have one copy (called
> acpi_slit) of SLIT, if there is SLIT from ACPI.
> 
> so if numa is enabled, could expose that acpi_slit via sysfs for the
> user to update it.
> 

Yeah, but in what format do you expect the user to update it?  There is no 
ACPI requirement that all nodes that have a remote distance of 20 to node 
0, for instance, are local to themselves.

So you'll have to report the entire physical topology in one write to a 
sysfs interface.  We don't currently have such a format unless we are to 
allow updating of the pxms.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/