From: Ingo Molnar <mingo@elte.hu>
To: David Rientjes <rientjes@google.com>, Greg KH <gregkh@suse.de>
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] x86: increase CONFIG_NODES_SHIFT max to 10
Date: Thu, 11 Mar 2010 14:23:54 +0100 [thread overview]
Message-ID: <20100311132354.GA26600@elte.hu> (raw)
In-Reply-To: <alpine.DEB.2.00.1003101537330.30724@chino.kir.corp.google.com>
* David Rientjes <rientjes@google.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
next prev parent reply other threads:[~2010-03-11 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 23:42 [patch] x86: increase CONFIG_NODES_SHIFT max to 10 David Rientjes
2010-03-11 13:23 ` Ingo Molnar [this message]
2010-03-11 14:06 ` Greg KH
2010-03-11 14:15 ` Ingo Molnar
2010-03-11 17:58 ` Greg KH
2010-03-11 18:18 ` Ingo Molnar
2010-03-25 22:39 ` [patch v2] " David Rientjes
2010-04-02 19:06 ` [tip:x86/urgent] x86: Increase " tip-bot for David Rientjes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100311132354.GA26600@elte.hu \
--to=mingo@elte.hu \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox