| 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
| ||
|
Message-ID: <86802c440802201355v260e8491k2e0832c5f12ebb39@mail.gmail.com> Date: Wed, 20 Feb 2008 13:55:38 -0800 From: "Yinghai Lu" <yhlu.kernel@...il.com> To: "Brice Goglin" <Brice.Goglin@...ia.fr> Cc: "Andrew Morton" <akpm@...ux-foundation.org>, "Andi Kleen" <ak@...e.de>, "Ingo Molnar" <mingo@...e.hu>, "Paul Mundt" <lethal@...ux-sh.org>, "Chris Snook" <csnook@...hat.com>, linux-kernel@...r.kernel.org, "Greg KH" <gregkh@...e.de> Subject: Re: Purpose of numa_node? On Wed, Feb 13, 2008 at 10:52 AM, Brice Goglin <Brice.Goglin@...ia.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 -- 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/
Powered by blists - more mailing lists