On 02/05/2014 06:28 AM, Michal Hocko wrote: > On Thu 02-01-14 12:20:17, Dave Hansen wrote: >> This continues in a series of patches to clean up the >> configuration menus. I believe they've become really hard to >> navigate and there are some simple things we can do to make >> things easier to find. >> >> This creates a "Memory Options" menu and moves some things like >> swap and slab configuration under them. It also moves SLUB_DEBUG >> to the debugging menu. >> >> After this patch, the menu has the following options: >> >> [ ] Memory placement aware NUMA scheduler >> [*] Enable VM event counters for /proc/vmstat >> [ ] Disable heap randomization >> [*] Support for paging of anonymous memory (swap) >> Choose SLAB allocator (SLUB (Unqueued Allocator)) >> [*] SLUB per cpu partial cache >> [*] SLUB: attempt to use double-cmpxchg operations > > Is there any reason to keep them in init/Kconfig rather than > mm/Kconfig? It would sound like a logical place to have them all, no? These options are the memory-related ones that fall under the "General setup" menu and the mm/Kconfig ones fall in to "Processor type and features". I've been hesitant to move these over to mm/Kconfig just because I don't want to put more stuff in the arch-specific menus. You raise a good point, though, that there isn't a great logical separation about what should go where. Things like zram and KSM end up in "Processor type and features" when they're really pretty architecture-neutral. -- 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>