public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	hawkes@sgi.com, Tony Luck <tony.luck@gmail.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jack Steiner <steiner@sgi.com>, Dan Higgins <djh@sgi.com>,
	John Hesterberg <jh@sgi.com>, Greg Edwards <edwardsg@sgi.com>
Subject: Re: [PATCH] ia64: change defconfig to NR_CPUS==1024
Date: Fri, 6 Jan 2006 10:49:57 -0700	[thread overview]
Message-ID: <20060106174957.GF19769@parisc-linux.org> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F055A7B6B@scsmsx401.amr.corp.intel.com>

On Fri, Jan 06, 2006 at 09:45:20AM -0800, Luck, Tony wrote:
> I suppose that depends on your expectations from defconfig.  In my
> mind its the one that builds into a kernel that will boot and run
> on just about any box.  People who want to get a bit of extra performance
> will do the re-compilation to strip out the bits that they don't want
> and tune down limits that are set higher than they need.  I only

You can use that argument to set the CPU limit low too -- since a kernel
with a CPU limit lower than the number of CPUs in the box will just ignore
the additional ones, people who want to get the additional performance
will tune limits that are set lower than they need ;-)

> ever boot a defconfig kernel to check that it still works, my systems
> all run tiger_defconfig/zx1_defconfig based most of the time.  But
> perhaps I'm the weird one?
> 
> There are quite a few >16 socket boxes out there, which will give
> you >64 cpus with Montecito ... so I don't think that the >64 cpu
> system is going to remain in the noise for long.

I bet the number of 32-way+ boxes is lost in the noise compared to the
number of 1-, 2- and 4-way boxes sold.  Not that HP trust me with that
kind of sales data ;-)

  reply	other threads:[~2006-01-06 17:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06 17:45 [PATCH] ia64: change defconfig to NR_CPUS==1024 Luck, Tony
2006-01-06 17:49 ` Matthew Wilcox [this message]
2006-01-06 18:04   ` Christoph Lameter
2006-01-06 18:07     ` Matthew Wilcox
2006-01-06 18:19     ` Randy.Dunlap
2006-01-06 18:37       ` Christoph Lameter
2006-01-06 18:59         ` Arjan van de Ven
2006-01-06 20:17           ` Alan Cox
2006-01-06 20:18             ` Randy.Dunlap
2006-01-06 20:42           ` Rohit Seth
2006-01-06 21:00         ` Dave Jones
2006-01-06 18:25 ` Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2006-01-06 17:19 Luck, Tony
2006-01-06 17:24 ` Arjan van de Ven
2006-01-06 17:26 ` Matthew Wilcox
2006-01-05 21:39 hawkes
2006-01-05 22:33 ` Chen, Kenneth W
2006-01-06 17:06   ` John Hawkes
2006-01-06  8:38 ` Arjan van de Ven
2006-01-12  0:09 ` Paul Jackson
2006-01-12 19:04   ` Christoph Lameter

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=20060106174957.GF19769@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=djh@sgi.com \
    --cc=edwardsg@sgi.com \
    --cc=hawkes@sgi.com \
    --cc=jh@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steiner@sgi.com \
    --cc=tony.luck@gmail.com \
    --cc=tony.luck@intel.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