Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763233AbXHATF1 (ORCPT ); Wed, 1 Aug 2007 15:05:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757406AbXHATFP (ORCPT ); Wed, 1 Aug 2007 15:05:15 -0400 Received: from atlrel9.hp.com ([156.153.255.214]:49853 "EHLO atlrel9.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756897AbXHATFN (ORCPT ); Wed, 1 Aug 2007 15:05:13 -0400 Subject: [PATCH] 2.6.23-rc1-mm1 - fix missing numa_zonelist_order sysctl From: Lee Schermerhorn To: Andrew Morton Cc: linux-kernel , linux-mm , Kamezawa Hiroyuki , Christoph Lameter Content-Type: text/plain Organization: HP/OSLO Date: Wed, 01 Aug 2007 15:02:51 -0400 Message-Id: <1185994972.5059.91.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1323 Lines: 45 Fix missing numa_zonelist_order sysctl config Against 2.6.23-rc1-mm1. Found this testing Mel Gorman's patch for the issue with "policy_zone" and ZONE_MOVABLE. Misplaced #endif is hiding the numa_zonelist_order sysctl when !SECURITY. [But, maybe reordering the zonelists is not such a good idea when ZONE_MOVABLE is populated?] Signed-off-by: Lee Schermerhorn kernel/sysctl.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index: Linux/kernel/sysctl.c =================================================================== --- Linux.orig/kernel/sysctl.c 2007-07-25 09:29:50.000000000 -0400 +++ Linux/kernel/sysctl.c 2007-08-01 13:29:18.000000000 -0400 @@ -1068,6 +1068,7 @@ static ctl_table vm_table[] = { .mode = 0644, .proc_handler = &proc_doulongvec_minmax, }, +#endif #ifdef CONFIG_NUMA { .ctl_name = CTL_UNNUMBERED, @@ -1079,7 +1080,6 @@ static ctl_table vm_table[] = { .strategy = &sysctl_string, }, #endif -#endif #if defined(CONFIG_X86_32) || \ (defined(CONFIG_SUPERH) && defined(CONFIG_VSYSCALL)) { - 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/