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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Fri, 3 Apr 2009 23:53:51 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	David Rientjes <rientjes@...gle.com>
Cc:	Andi Kleen <andi@...stfloor.org>, Chris Worley <worleys@...il.com>,
	Yinghai Lu <yhlu.kernel@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Off topic: Numactl "distance" wrong

On Fri, Apr 03, 2009 at 02:43:32PM -0700, David Rientjes wrote:
> On Fri, 3 Apr 2009, Andi Kleen wrote:
> 
> > > Who would be the right person (or list) to talk about this?
> > 
> > Your BIOS vendor whose code reported the wrong values. Not that it matters
> > really on small systems.
> > 
> 
> The numactl --hardware values are coming directly from the sysfs per-node 
> distance interface, so this may not be a result of erroneous BIOS data but 
> rather the lack of a SLIT to describe the physical topology better.

That's the same really. Think about it. No SLIT on a NUMA system is a wrong
SLIT.

BTW there are more cases, like illegal slit which is also replaced
with 10/20.

-Andi
--
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/