From: Adrian Bunk <bunk@stusta.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
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, 06 Jan 2006 18:25:46 +0000 [thread overview]
Message-ID: <20060106182546.GX12131@stusta.de> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F055A7B6B@scsmsx401.amr.corp.intel.com>
On Fri, Jan 06, 2006 at 09:45:20AM -0800, Luck, Tony wrote:
> >Why can't we keep the default below 64? Surely the 0.1% of the market
> >which needs more than 64 cpus can recompile their kernel ...
>
> 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
> 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?
>...
defconfig's are usually not intended for running on all supported
machines, they are more a base for compile-tests and a starting point
for building an own configuration.
If you intend to use the ia64 defconfig in a different way I don't
see any strong point against it.
But if you seriously want a defconfig "that builds into a kernel that
will boot and run on just about any box", please change your defconfig
to ITANIUM=y,MCKINLEY=n. "People who want to get a bit of extra
performance" can still change their configuration to omit support for
the original Itanium.
> -Tony
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
WARNING: multiple messages have this Message-ID (diff)
From: Adrian Bunk <bunk@stusta.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
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 19:25:46 +0100 [thread overview]
Message-ID: <20060106182546.GX12131@stusta.de> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F055A7B6B@scsmsx401.amr.corp.intel.com>
On Fri, Jan 06, 2006 at 09:45:20AM -0800, Luck, Tony wrote:
> >Why can't we keep the default below 64? Surely the 0.1% of the market
> >which needs more than 64 cpus can recompile their kernel ...
>
> 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
> 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?
>...
defconfig's are usually not intended for running on all supported
machines, they are more a base for compile-tests and a starting point
for building an own configuration.
If you intend to use the ia64 defconfig in a different way I don't
see any strong point against it.
But if you seriously want a defconfig "that builds into a kernel that
will boot and run on just about any box", please change your defconfig
to ITANIUM=y,MCKINLEY=n. "People who want to get a bit of extra
performance" can still change their configuration to omit support for
the original Itanium.
> -Tony
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-01-06 18:25 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 21:39 [PATCH] ia64: change defconfig to NR_CPUS==1024 hawkes
2006-01-05 21:39 ` hawkes
2006-01-05 22:33 ` Chen, Kenneth W
2006-01-05 22:33 ` Chen, Kenneth W
2006-01-06 17:06 ` John Hawkes
2006-01-06 17:06 ` John Hawkes
2006-01-06 8:38 ` Arjan van de Ven
2006-01-06 8:38 ` Arjan van de Ven
2006-01-06 17:19 ` Luck, Tony
2006-01-06 17:19 ` Luck, Tony
2006-01-06 17:24 ` Arjan van de Ven
2006-01-06 17:24 ` Arjan van de Ven
2006-01-06 17:26 ` Matthew Wilcox
2006-01-06 17:26 ` Matthew Wilcox
2006-01-06 17:45 ` Luck, Tony
2006-01-06 17:45 ` Luck, Tony
2006-01-06 17:49 ` Matthew Wilcox
2006-01-06 17:49 ` Matthew Wilcox
2006-01-06 18:04 ` Christoph Lameter
2006-01-06 18:04 ` Christoph Lameter
2006-01-06 18:07 ` Matthew Wilcox
2006-01-06 18:07 ` Matthew Wilcox
2006-01-06 18:19 ` Randy.Dunlap
2006-01-06 18:19 ` Randy.Dunlap
2006-01-06 18:37 ` Christoph Lameter
2006-01-06 18:37 ` Christoph Lameter
2006-01-06 18:59 ` Arjan van de Ven
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:18 ` Randy.Dunlap
2006-01-06 20:42 ` Rohit Seth
2006-01-06 20:42 ` Rohit Seth
2006-01-06 21:00 ` Dave Jones
2006-01-06 21:00 ` Dave Jones
2006-01-06 18:25 ` Adrian Bunk [this message]
2006-01-06 18:25 ` Adrian Bunk
2006-01-12 0:09 ` Paul Jackson
2006-01-12 0:09 ` Paul Jackson
2006-01-12 19:04 ` Christoph Lameter
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=20060106182546.GX12131@stusta.de \
--to=bunk@stusta.de \
--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=matthew@wil.cx \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.