[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100311132354.GA26600@elte.hu>
Date: Thu, 11 Mar 2010 14:23:54 +0100
From: Ingo Molnar <mingo@...e.hu>
To: David Rientjes <rientjes@...gle.com>, Greg KH <gregkh@...e.de>
Cc: Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [patch] x86: increase CONFIG_NODES_SHIFT max to 10
* David Rientjes <rientjes@...gle.com> wrote:
> Some larger systems require more than 512 nodes, so increase the maximum
> CONFIG_NODES_SHIFT to 10 for a new max of 1024 nodes.
>
> This was tested with numa=fake=64M on systems with more than 64GB of RAM. A
> total of 1022 nodes were initialized.
>
> Successfully builds with no additional warnings on x86_64 allyesconfig.
Not so here:
drivers/base/node.c:169: error: negative width in bit-field ?<anonymous>?
> Greg KH has queued up numa-fix-BUILD_BUG_ON-for-node_read_distance.patch
> for 2.6.35 to fix the build error when CONFIG_NODES_SHIFT is set to 10.
> See http://lkml.org/lkml/2010/3/10/390
erm. Alas I cannot merge it in the x86 tree without that fix being upstream.
Why for v2.6.35 - shouldnt that be v2.6.34?
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists