Re: [PATCH 6/6] hugetlb: update hugetlb documentation for mempolicy based management.

[David Rientjes <rientjes@xxxxxxxxxx>]

On Mon, 14 Sep 2009, David Rientjes wrote:

> > On PPC64, the parameters behave differently. I couldn't convince it to
> > create more than one NUMA node. On x86-64, the NUMA nodes appeared to
> > exist and would be visible on /proc/buddyinfo for example but the sysfs
> > directories for the fake nodes were not created so nr_hugepages couldn't
> > be examined on a per-node basis for example.
> > 
> 
> I don't know anything about the ppc64 fake NUMA, but the sysfs node 
> directories should certainly be created on x86_64.  I'll look into it 
> because that's certainly a bug.  Thanks.
> 

This works on my machine just fine.

For example, with numa=fake=8:

	$ ls /sys/devices/system/node
	has_cpu  has_normal_memory  node0  node1  node2  node3  node4  
node5  node6  node7  online  possible

	$ ls /sys/devices/system/node/node3
	cpu4  cpu5  cpu6  cpu7  cpulist  cpumap  distance  meminfo  
numastat  scan_unevictable_pages

I don't see how this could differ if bootmem is setting up the nodes 
correctly, which dmesg | grep "^Bootmem setup node" would reveal.

The defconfig disables CONFIG_NUMA_EMU now, though, so perhaps it got 
turned off by accident in your kernel?

Let me know if there's any abnormalities with your particular setup.
--
To unsubscribe from this list: send the line "unsubscribe linux-numa" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html