Prev: net: reserve ports for applications using fixed port
Next: driver/misc: Add new driver for Avago ADJD-S371-QR999
From: Rik van Riel on 16 Feb 2010 12:50 On 02/12/2010 07:00 AM, Mel Gorman wrote: > CONFIG_MIGRATION currently depends on CONFIG_NUMA or on the architecture > being able to hot-remove memory. The main users of page migration such as > sys_move_pages(), sys_migrate_pages() and cpuset process migration are > only beneficial on NUMA so it makes sense. > > As memory compaction will operate within a zone and is useful on both NUMA > and non-NUMA systems, this patch allows CONFIG_MIGRATION to be set if the > user selects CONFIG_COMPACTION as an option. > > Signed-off-by: Mel Gorman<mel(a)csn.ul.ie> > Reviewed-by: Christoph Lameter<cl(a)linux-foundation.org> Reviewed-by: Rik van Riel <riel(a)redhat.com> -- All rights reversed. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Christoph Lameter on 17 Mar 2010 12:40
On Wed, 17 Mar 2010, Mel Gorman wrote: > > If select MIGRATION works, we can remove "depends on NUMA || ARCH_ENABLE_MEMORY_HOTREMOVE" > > line from config MIGRATION. > > > > I'm not quite getting why this would be an advantage. COMPACTION > requires MIGRATION but conceivable both NUMA and HOTREMOVE can work > without it. Avoids having to add additional CONFIG_XXX on the page migration "depends" line in the future. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |