![]() | |||||||||||||
Messages in this thread |
To come back to Randy's original question ... Cpusets are not - in my view - designed to display the NUMA architecture. /sys already does this very well (example of a 16 way machine) : $ ls /sys/devices/system/node/node* /sys/devices/system/node/node0: cpu0 cpu1 cpu2 cpu3 cpumap distance meminfo numastat /sys/devices/system/node/node1: cpu4 cpu5 cpu6 cpu7 cpumap distance meminfo numastat /sys/devices/system/node/node2: cpu10 cpu11 cpu8 cpu9 cpumap distance meminfo numastat /sys/devices/system/node/node3: cpu12 cpu13 cpu14 cpu15 cpumap distance meminfo numastat I think sysfs remains the best way to view your NUMA nodes. Sylvain On Wed, 2 Nov 2005, Daniel J Blueman wrote: > I'm not sure of the true answer; it is likely that CPUSETS was > designed in the 2.4 timeframe and compatibility was preferred over the > clean sysfs interface.> > I've CC'd the authors.> > Dan> > On 11/2/05, Randy.Dunlap <rdunlap@xenotime.net> wrote: > > On Wed, 2 Nov 2005, Daniel J Blueman wrote:> > >> > > Janos,> > >> > > You can see what valid memory nodes are available from the top-level > > > cpuset directory:> > >> > > # cat /dev/cpuset/mems> > > 0 1 2 3> > >> > > If you were to be running on a NUMA-capable system, you'd also want to > > > ensure page interleaving was disabled in the BIOS/pre-boot firmware > > > too.> >> > Just for info, why is this in /dev at all, instead of, say, > > /sys ??> >> > --> > ~Randy > ___ > Daniel J Blueman > - 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/ | ||||||||||||
| Last update: 2005-11-03 09:29 [from the cache] ©2003-2008 | |||||||||||||