From: Dave Jones <davej@redhat.com>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
Matthew Wilcox <matthew@wil.cx>,
"Luck, Tony" <tony.luck@intel.com>,
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 21:00:24 +0000 [thread overview]
Message-ID: <20060106210024.GK4595@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0601061035510.17875@schroedinger.engr.sgi.com>
On Fri, Jan 06, 2006 at 10:37:33AM -0800, Christoph Lameter wrote:
> On Fri, 6 Jan 2006, Randy.Dunlap wrote:
>
> > > The dicey thing in all of this is that the generic kernels will be used
> > > for the certification of applications. If the cpu limit is too low then
> > > applications will simply not be certified for these high processor counts.
> > > One may encounter problems if the app is then run with a higher processor
> > > count.
> >
> > Do you equate a 'defconfig' kernel with a generic kernel?
> >
> > I would expect certs to be done on vendor kernels, and as
> > Arjan has suggested, they will have their own configs,
> > not defconfig.
>
> Vendors look for the upstream defaults and orient themselves on the
> defconfig. It is best to have as much common code and configurations as
> possible.
As someone who builds vendor kernels, I can say this isn't true (from my
experience at least). When a new config option appears, I look at the
Kconfig, and make a decision. I *never* even look at the defconfig, as
a lot of the time, they are either out of date, or irrelevant.
Dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@redhat.com>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
Matthew Wilcox <matthew@wil.cx>,
"Luck, Tony" <tony.luck@intel.com>,
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 16:00:24 -0500 [thread overview]
Message-ID: <20060106210024.GK4595@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0601061035510.17875@schroedinger.engr.sgi.com>
On Fri, Jan 06, 2006 at 10:37:33AM -0800, Christoph Lameter wrote:
> On Fri, 6 Jan 2006, Randy.Dunlap wrote:
>
> > > The dicey thing in all of this is that the generic kernels will be used
> > > for the certification of applications. If the cpu limit is too low then
> > > applications will simply not be certified for these high processor counts.
> > > One may encounter problems if the app is then run with a higher processor
> > > count.
> >
> > Do you equate a 'defconfig' kernel with a generic kernel?
> >
> > I would expect certs to be done on vendor kernels, and as
> > Arjan has suggested, they will have their own configs,
> > not defconfig.
>
> Vendors look for the upstream defaults and orient themselves on the
> defconfig. It is best to have as much common code and configurations as
> possible.
As someone who builds vendor kernels, I can say this isn't true (from my
experience at least). When a new config option appears, I look at the
Kconfig, and make a decision. I *never* even look at the defconfig, as
a lot of the time, they are either out of date, or irrelevant.
Dave
next prev parent reply other threads:[~2006-01-06 21:00 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 [this message]
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=20060106210024.GK4595@redhat.com \
--to=davej@redhat.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.