Andrew Morton writes:
Does this actually clean things up, or does it randomly move things around
while carefully retaining existing obscurity?  Not sure..

Heh, the bulk of it is basically splitting the current __cache_alloc into separate UMA and NUMA paths via __do_cache_alloc so we don't have to play with NUMA_BUILD tricks. I also moved __cache_alloc_node in the same CONFIG_NUMA block as __cache_alloc while I was at it. Pekka -
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to