From: Nick Piggin <piggin@cyberone.com.au>
To: Eric <eric@cisu.net>
Cc: linux-kernel@vger.kernel.org, davej@redhat.com
Subject: Re: Correct CPUs printout on boot.
Date: Sat, 24 Jan 2004 13:25:51 +1100 [thread overview]
Message-ID: <4011D7AF.8030205@cyberone.com.au> (raw)
In-Reply-To: <200401231703.54127.eric@cisu.net>
Eric wrote:
>On Friday 23 January 2004 12:35 am, davej@redhat.com wrote:
>
>>This currently prints out the maximum number of CPUs the
>>kernel is configured to support, instead of the actual
>>number that the kernel brought up. Which results in odd
>>displays that look like you have more CPUs than you do.
>>
>
>Why do you have to declare a new variable? Can't you just do this? i is
>already counting how many cpu's we've brought up and its of the same type j.
>
CPU numbering is allowed to be sparse. Besides, i still
counts up to NR_CPUS even if CPU numbering isn't sparse.
prev parent reply other threads:[~2004-01-24 2:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 6:35 Correct CPUs printout on boot davej
2004-01-23 23:03 ` Eric
2004-01-24 2:25 ` Nick Piggin [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=4011D7AF.8030205@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=davej@redhat.com \
--cc=eric@cisu.net \
--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