From: Brice Goglin <Brice.Goglin@inria.fr>
To: Chris Worley <worleys@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Off topic: Numactl "distance" wrong
Date: Fri, 03 Apr 2009 22:16:03 +0200 [thread overview]
Message-ID: <49D66E83.5070606@inria.fr> (raw)
In-Reply-To: <f3177b9e0904031302p8aef826u1874a8b9d9af0840@mail.gmail.com>
Chris Worley wrote:
> Sorry for an off topic, but I'm hoping somebody can point me in the
> right direction of where to direct this question...
>
> I have an Opteron system where I've seen the HW diagrams, and each of
> 4 sockets is directly connected (HT) to two other sockets, and two HT
> hops away from a third (i.e. a simple square topology, no X in the
> middle).
>
> Yet, "numactl --hardware" shows but one hop to each socket:
>
> # numactl --hardware
> ...
> node 0 1 2 3
> 0: 10 20 20 20
> 1: 20 10 20 20
> 2: 20 20 10 20
> 3: 20 20 20 10
>
> I know this is wrong.
>
> Who would be the right person (or list) to talk about this?
>
IIRC, the motherboard/BIOS is supposed to report numa distances through
the PXM ACPI method. But I have never seen any opteron box do it
properly. So you just get 10 for "local" and 20 for "remote". Some
Itanium machines however report actual distances.
Brice
next prev parent reply other threads:[~2009-04-03 20:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 20:02 Off topic: Numactl "distance" wrong Chris Worley
2009-04-03 20:16 ` Brice Goglin [this message]
2009-04-03 20:49 ` Yinghai Lu
2009-04-03 21:01 ` Cliff Wickman
2009-04-03 21:43 ` Yinghai Lu
2009-04-03 21:24 ` Andi Kleen
2009-04-03 21:43 ` David Rientjes
2009-04-03 21:48 ` Yinghai Lu
2009-04-03 21:52 ` David Rientjes
2009-04-03 21:55 ` Andi Kleen
2009-04-03 22:15 ` Yinghai Lu
2009-04-07 2:52 ` KOSAKI Motohiro
2009-04-07 6:17 ` Brice Goglin
2009-04-07 7:05 ` Andi Kleen
2009-04-07 7:40 ` Brice Goglin
2009-04-07 7:56 ` Andi Kleen
2009-04-07 7:44 ` David Rientjes
2009-04-07 7:59 ` Andi Kleen
2009-04-07 8:08 ` David Rientjes
2009-04-07 8:23 ` Andi Kleen
2009-04-07 8:30 ` David Rientjes
2009-04-07 9:13 ` Andi Kleen
2009-04-03 21:53 ` Andi Kleen
2009-04-03 21:54 ` David Rientjes
2009-04-03 22:18 ` Yinghai Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49D66E83.5070606@inria.fr \
--to=brice.goglin@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=worleys@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox