public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Zwane Mwaikambo <zwane@holomorphy.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH][2.5] smp_init 'CPUS done' looks strange
Date: Thu, 14 Nov 2002 12:59:07 +1100	[thread overview]
Message-ID: <20021114013718.0AE592C19D@lists.samba.org> (raw)
In-Reply-To: Your message of "Wed, 13 Nov 2002 08:22:28 CDT." <Pine.LNX.4.44.0211130820410.24523-100000@montezuma.mastecende.com>

In message <Pine.LNX.4.44.0211130820410.24523-100000@montezuma.mastecende.com> 
you write:
> On Wed, 13 Nov 2002, Rusty Russell wrote:
> 
> > In message <Pine.LNX.4.44.0211122246540.24523-100000@montezuma.mastecende.c
om> 
> > you write:
> > > Also, it would make sense in the future if smp_cpus_done actually gets a 
> > > value denoting how many cpus are online.
> > 
> > No.  Drop the prink by all means, but smp_cpus_done() can call
> > num_online_cpus() itself.  It can't know how many cpus the user
> > specified, however.
> 
> Doesn't that just encourage more (i = 0; i < NR_CPUS; i++) usage? If you 
> make max_cpus available to everyone, at least they'll have the correct cpu 
> count to check against. max_cpus is needed by more than bootup.

1) CPUs can be nonlinear.
2) They can bring CPUs up after boot.

AM has some cpu iterator patches for those who really care about
efficiently iterating over only online cpus, or only possible cpus.

Hope that helps,
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

      reply	other threads:[~2002-11-14  1:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13  3:50 [PATCH][2.5] smp_init 'CPUS done' looks strange Zwane Mwaikambo
2002-11-13  9:34 ` Rusty Russell
2002-11-13 13:22   ` Zwane Mwaikambo
2002-11-14  1:59     ` Rusty Russell [this message]

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=20021114013718.0AE592C19D@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=zwane@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox