All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rohit Seth <rohit.seth@intel.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Christoph Lameter <clameter@engr.sgi.com>,
	"Randy.Dunlap" <rdunlap@xenotime.net>,
	Matthew Wilcox <matthew@wil.cx>,
	"Luck, Tony" <tony.luck@intel.com>,
	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 20:42:25 +0000	[thread overview]
Message-ID: <1136580145.31992.9.camel@akash.sc.intel.com> (raw)
In-Reply-To: <1136573948.2940.65.camel@laptopd505.fenrus.org>

On Fri, 2006-01-06 at 10:59 -0800, Arjan van de Ven wrote:
> 
> > Vendors look for the upstream defaults and orient themselves on the
> > defconfig.
> 
> they do? That's news to me. I've worked at a vendor for almost 5
> years,
> 3 1/2 years of which I was the person who decided on the configs (with
> external input of course). In those 3 1/2 years I *never* looked at
> defconfig. *never*. And I don't expect other vendor kernel owners to
> do
> things differently; when a config option needs deciding you look at
> the
> description and pick a good value. That's it. Defconfig doesn't
> matter.
> 

IMO something like 128 is a good number as a default for most IA-64
machines.  As Arjan said above, OSVs almost always have their own
reasons and input to choose this number.  And lately there is a trend of
having at least two kernels, one for mostly used platforms and the other
one for bigger configurations.

-rohit


WARNING: multiple messages have this Message-ID (diff)
From: Rohit Seth <rohit.seth@intel.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Christoph Lameter <clameter@engr.sgi.com>,
	"Randy.Dunlap" <rdunlap@xenotime.net>,
	Matthew Wilcox <matthew@wil.cx>,
	"Luck, Tony" <tony.luck@intel.com>,
	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 12:42:25 -0800	[thread overview]
Message-ID: <1136580145.31992.9.camel@akash.sc.intel.com> (raw)
In-Reply-To: <1136573948.2940.65.camel@laptopd505.fenrus.org>

On Fri, 2006-01-06 at 10:59 -0800, Arjan van de Ven wrote:
> 
> > Vendors look for the upstream defaults and orient themselves on the
> > defconfig.
> 
> they do? That's news to me. I've worked at a vendor for almost 5
> years,
> 3 1/2 years of which I was the person who decided on the configs (with
> external input of course). In those 3 1/2 years I *never* looked at
> defconfig. *never*. And I don't expect other vendor kernel owners to
> do
> things differently; when a config option needs deciding you look at
> the
> description and pick a good value. That's it. Defconfig doesn't
> matter.
> 

IMO something like 128 is a good number as a default for most IA-64
machines.  As Arjan said above, OSVs almost always have their own
reasons and input to choose this number.  And lately there is a trend of
having at least two kernels, one for mostly used platforms and the other
one for bigger configurations.

-rohit


  parent reply	other threads:[~2006-01-06 20:42 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 [this message]
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
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=1136580145.31992.9.camel@akash.sc.intel.com \
    --to=rohit.seth@intel.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=clameter@engr.sgi.com \
    --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=rdunlap@xenotime.net \
    --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.