From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Brice Goglin" <Brice.Goglin@inria.fr>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Andi Kleen" <ak@suse.de>, "Ingo Molnar" <mingo@elte.hu>,
"Paul Mundt" <lethal@linux-sh.org>,
"Chris Snook" <csnook@redhat.com>,
linux-kernel@vger.kernel.org, "Greg KH" <gregkh@suse.de>
Subject: Re: Purpose of numa_node?
Date: Wed, 20 Feb 2008 13:55:38 -0800 [thread overview]
Message-ID: <86802c440802201355v260e8491k2e0832c5f12ebb39@mail.gmail.com> (raw)
In-Reply-To: <47B33C56.3070502@inria.fr>
On Wed, Feb 13, 2008 at 10:52 AM, Brice Goglin <Brice.Goglin@inria.fr> wrote:
> /sys/devices/pci0000:40/0000:40:0f.0/numa_node 1
> /sys/devices/pci0000:40/0000:40:10.0/numa_node 1
> /sys/devices/pci0000:40/0000:40:11.0/numa_node 1
> /sys/devices/pci0000:40/0000:40:12.0/numa_node 1
> /sys/devices/pci0000:40/0000:40:12.0/0000:51:00.0/numa_node 1
> /sys/devices/pci0000:40/0000:40:13.0/numa_node 1
>
> The 5 last lines above would report 0 instead of 1 with an older kernel.
> Everything looks correct now (0000:40 is the second PCIe bus and it is
> attached to socket #1).
>
> Thanks a lot, Yinghai! Are you planning to merge these patches in the
> near future? 2.6.26?
>
ingo put them in x86.git#testing
please check
http://people.redhat.com/mingo/x86.git/README
to get that.
YH
prev parent reply other threads:[~2008-02-20 21:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 0:48 Chris Snook
2008-01-31 7:40 ` Paul Mundt
2008-01-31 9:56 ` Andi Kleen
2008-01-31 13:42 ` Brice Goglin
2008-01-31 21:29 ` Yinghai Lu
2008-01-31 21:35 ` Brice Goglin
2008-01-31 21:42 ` Yinghai Lu
2008-01-31 23:35 ` Yinghai Lu
2008-02-13 18:52 ` Brice Goglin
2008-02-13 21:31 ` Yinghai Lu
2008-02-20 21:55 ` Yinghai Lu [this message]
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=86802c440802201355v260e8491k2e0832c5f12ebb39@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=Brice.Goglin@inria.fr \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=csnook@redhat.com \
--cc=gregkh@suse.de \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®