Re: [PATCH] mm: only define hashdist variable when needed

2015-05-06 Thread David Rientjes
On Mon, 4 May 2015, Rasmus Villemoes wrote: > For !CONFIG_NUMA, hashdist will always be 0, since it's setter is > otherwise compiled out. So we can save 4 bytes of data and some .text > (although mostly in __init functions) by only defining it for > CONFIG_NUMA. > > Signed-off-by: Rasmus Villemoe

Re: [PATCH] mm: only define hashdist variable when needed

2015-05-06 Thread Michal Hocko
On Mon 04-05-15 17:27:29, Rasmus Villemoes wrote: > For !CONFIG_NUMA, hashdist will always be 0, since it's setter is > otherwise compiled out. So we can save 4 bytes of data and some .text > (although mostly in __init functions) by only defining it for > CONFIG_NUMA. > > Signed-off-by: Rasmus Vil

[PATCH] mm: only define hashdist variable when needed

2015-05-04 Thread Rasmus Villemoes
For !CONFIG_NUMA, hashdist will always be 0, since it's setter is otherwise compiled out. So we can save 4 bytes of data and some .text (although mostly in __init functions) by only defining it for CONFIG_NUMA. Signed-off-by: Rasmus Villemoes --- include/linux/bootmem.h | 8 mm/page_all