From: Dave Jones <davej@redhat.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] i386/x86_64 mpparse.c: kill maxcpus
Date: Sun, 20 Mar 2005 18:32:03 -0500 [thread overview]
Message-ID: <20050320233203.GC26230@redhat.com> (raw)
In-Reply-To: <20050320231232.GY4449@stusta.de>
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.
> The function maxcpus in init/main.c sets a static variable max_cpus -
> not the global variable maxcpus in the mpparse.c files.
Both variables are used differently. The arch specific var is only
used for HT descrimination. The init/main.c one is used for smp bringup.
> How should it be?
>
> Should max_cpus in init/main.c become global and replace the maxcpus
> from the mpparse.c files?
I'd just leave it as it is, as it seems to be working right now.
Dave
next prev parent reply other threads:[~2005-03-20 23:33 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 [this message]
2005-03-20 23:59 ` Adrian Bunk
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=20050320233203.GC26230@redhat.com \
--to=davej@redhat.com \
--cc=bunk@stusta.de \
--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