Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754274Ab0AGWFH (ORCPT ); Thu, 7 Jan 2010 17:05:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751651Ab0AGWFF (ORCPT ); Thu, 7 Jan 2010 17:05:05 -0500 Received: from nlpi129.sbcis.sbc.com ([207.115.36.143]:51277 "EHLO nlpi129.prodigy.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750783Ab0AGWFE (ORCPT ); Thu, 7 Jan 2010 17:05:04 -0500 Date: Thu, 7 Jan 2010 16:04:00 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@router.home To: David Rientjes cc: Mel Gorman , Andrea Arcangeli , Adam Litke , Avi Kivity , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH 1/7] Allow CONFIG_MIGRATION to be set without CONFIG_NUMA In-Reply-To: Message-ID: References: <1262795169-9095-1-git-send-email-mel@csn.ul.ie> <1262795169-9095-2-git-send-email-mel@csn.ul.ie> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 891 Lines: 20 On Thu, 7 Jan 2010, David Rientjes wrote: > CONFIG_MIGRATION is no longer strictly dependent on CONFIG_NUMA since > ARCH_ENABLE_MEMORY_HOTREMOVE has allowed it to be configured for UMA > machines. All strictly NUMA features in the migration core should be > isolated under its #ifdef CONFIG_NUMA (sys_move_pages()) in mm/migrate.c > or by simply not compiling mm/mempolicy.c (sys_migrate_pages()), so this > patch looks fine as is (although the "help" text for CONFIG_MIGRATION > could be updated to reflect that it's useful for both memory hot-remove > and now compaction). Correct. Reviewed-by: Christoph Lameter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/