> Good question. > > There are 19 free bits in my configuration but it's related to > CONFIG_NODES_SHIFT which is 9 for me (512 nodes) and very heavily affected > by options such as CONFIG_SPARSEMEM_VMEMMAP. Memory hot-remove does not work > with CONFIG_SPARSEMEM_VMEMMAP and enterprise distribution configs may be > taking the performance hit to enable memory hot-remove. If I disable this > option to enable memory hot-remove then there are 0 free bits in page->flags.
FWIW, when using current mmotm, memory hot memory remove does work w/ CONFIG_SPARSEMEM_VMEMMAP. Recently Fujitsu changed. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
