All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cliff Wickman <cpw@sgi.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Brice Goglin <Brice.Goglin@inria.fr>,
	Chris Worley <worleys@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Off topic: Numactl "distance" wrong
Date: Fri, 3 Apr 2009 16:01:17 -0500	[thread overview]
Message-ID: <20090403210117.GA14582@sgi.com> (raw)
In-Reply-To: <86802c440904031349v31f84f8anf082db7505e60387@mail.gmail.com>

On Fri, Apr 03, 2009 at 01:49:27PM -0700, Yinghai Lu wrote:
> On Fri, Apr 3, 2009 at 1:16 PM, Brice Goglin <Brice.Goglin@inria.fr> wrote:
> > 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?

numactl and libnuma are discussed on
linux-numa@vger.kernel.org

> >>
> >
> > 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.
> 
> for x86 64 bit, we are copying SLIT table and save another copy.
> 
> could provide one /sys interface to make user could modify it...
> 
> YH
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Cliff Wickman
Silicon Graphics, Inc.
cpw@sgi.com
(651) 683-3824

  reply	other threads:[~2009-04-03 21:01 UTC|newest]

Thread overview: 26+ 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
2009-04-03 20:49   ` Yinghai Lu
2009-04-03 21:01     ` Cliff Wickman [this message]
2009-04-03 21:43       ` Yinghai Lu
2009-04-03 21:05     ` Cliff Wickman
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=20090403210117.GA14582@sgi.com \
    --to=cpw@sgi.com \
    --cc=Brice.Goglin@inria.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=worleys@gmail.com \
    --cc=yhlu.kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.