Re: /proc/pid/numa_maps no longer shows "default" policy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jan 30, 2014 at 05:34:57PM +1100, Anton Blanchard wrote:
> 
> Hi Mel,
> 
> We recently noticed that /proc/pid/numa_maps used to show default
> policy mappings as such:
> 
> cat /proc/self/numa_maps 
> 00100000 default mapped=1 mapmax=339 active=0 N0=1
> 
> But now it shows them as prefer:X:
> 
> cat /proc/self/numa_maps
> 10000000 prefer:1 file=/usr/bin/cat mapped=1 N0=1
> 
> It looks like this was caused by 5606e387 (mm: numa: Migrate on
> reference policy). I'm not sure if this is expected, but we don't have
> CONFIG_NUMA_BALANCING enabled on ppc64 so I wasn't expecting processes
> to have a particular node affinity by default.
> 

https://lkml.org/lkml/2014/1/25/182

-- 
Mel Gorman
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]