From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: linux-kernel@vger.kernel.org
Cc: Dan Christian <dac@proofpoint.com>
Subject: Re: broken maxcpus in 2.4.24
Date: Tue, 3 Feb 2004 09:53:30 +0100 [thread overview]
Message-ID: <200402030953.30429@WOLK> (raw)
In-Reply-To: <1075765034.17943.79.camel@reactor.us.proofpoint.com>
On Tuesday 03 February 2004 00:37, Dan Christian wrote:
Hi Dan,
> I compiled a vanilla 2.4.24 for a 2 processor Xeon.
> I set CONFIG_NR_CPUS to 4 (2 CPUs x 2 hyperthreads each).
> When I boot the kernel, /proc/cpuinfo only shows 2 cpus (0-1) and
> performance is bad.
> I reconfigure CONFIG_NR_CPUS back to 32. Now it shows 4 cpus (0-3) and
> performance is normal.
> Is this a bug or am misunderstanding how to set this configuration
> variable?
http://linux.bkbits.net:8080/linux-2.4/cset@1.1136.1.68?nav=index.html|
ChangeSet@-12w
ciao, Marc
next prev parent reply other threads:[~2004-02-03 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 23:37 broken maxcpus in 2.4.24 Dan Christian
2004-02-03 8:53 ` Marc-Christian Petersen [this message]
2004-02-03 23:45 ` James Schmidt
2004-02-03 23:49 ` Dave Jones
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=200402030953.30429@WOLK \
--to=m.c.p@wolk-project.de \
--cc=dac@proofpoint.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