From: Adrian Bunk <bunk@stusta.de>
To: Dave Jones <davej@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] i386/x86_64 mpparse.c: kill maxcpus
Date: Mon, 21 Mar 2005 00:59:46 +0100 [thread overview]
Message-ID: <20050320235946.GA4449@stusta.de> (raw)
In-Reply-To: <20050320233203.GC26230@redhat.com>
On Sun, Mar 20, 2005 at 06:32:03PM -0500, Dave Jones wrote:
> On Mon, Mar 21, 2005 at 12:12:32AM +0100, Adrian Bunk wrote:
> > On Sun, Mar 20, 2005 at 05:42:34PM -0500, Dave Jones wrote:
> > > On Sun, Mar 20, 2005 at 08:25:49PM +0100, Adrian Bunk wrote:
> > > > Do we really need a global variable that does only hold the value of
> > > > NR_CPUS?
> > >
> > > Yes.
> > >
> > > NR_CPUS = compile time
> > > maxcpus = boot command line at runtime.
> >
> > If this is how is was expected to work - it isn't exactly what is
> > currently implemented.
>
> It's ugly, as its setting the same thing in two different places, but
> I don't see any obvious reason why it won't work.
>...
I might be too dumb, but where are the mpparse.c maxcpus variables ever
set to any value different from NR_CPUS?
> Dave
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:[~2005-03-21 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-20 19:25 [2.6 patch] i386/x86_64 mpparse.c: kill maxcpus Adrian Bunk
2005-03-20 22:42 ` Dave Jones
2005-03-20 23:12 ` Adrian Bunk
2005-03-20 23:32 ` Dave Jones
2005-03-20 23:59 ` Adrian Bunk [this message]
2005-03-21 0:01 ` Dave Jones
2005-03-21 0:45 ` Adrian Bunk
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=20050320235946.GA4449@stusta.de \
--to=bunk@stusta.de \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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