public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Mike Travis <travis@sgi.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] x86: cleanup early per cpu variables/accesses v4-folded
Date: Mon, 28 Apr 2008 15:04:46 +0200	[thread overview]
Message-ID: <20080428130445.GA7113@ucw.cz> (raw)
In-Reply-To: <20080422204219.994283000@polaris-admin.engr.sgi.com>

On Tue 2008-04-22 13:42:19, Mike Travis wrote:
> 
>   * Increase the limit of NR_CPUS to 4096 and introduce a boolean
>     called "MAXSMP" which when set (e.g. "allyesconfig"), will set
>     NR_CPUS = 4096 and NODES_SHIFT = 9 (512).  Changed max setting
>     for NODES_SHIFT from 15 to 9 to accurately reflect the real limit.

NAK. Having redundant option sounds like a bad idea. What is it good
for?

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      parent reply	other threads:[~2008-04-28 14:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22 20:42 [PATCH 0/5] x86: cleanup early per cpu variables/accesses v4-folded Mike Travis
2008-04-22 20:42 ` [PATCH 1/5] x86: Modify Kconfig to allow up to 4096 cpus Mike Travis
2008-04-22 20:42 ` [PATCH 2/5] x86: cleanup early per cpu variables/accesses v4 Mike Travis
2008-04-22 20:42 ` [PATCH 3/5] x86: restore pda nodenumber field Mike Travis
2008-04-22 20:42 ` [PATCH 4/5] x86: remove the 256k node_to_cpumask_map after init Mike Travis
2008-04-22 20:42 ` [PATCH 5/5] sched: replace MAX_NUMNODES with nr_node_ids in kernel/sched.c Mike Travis
2008-04-28 13:04 ` Pavel Machek [this message]

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=20080428130445.GA7113@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=travis@sgi.com \
    /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