Skip to contentSkip to conversation

broken maxcpus in 2.4.24

DISCUSSION Dan Christian 4 participants 4 messages Feb 2, 2004 – Feb 3, 2004

lore
Share & tools
lore
#0 lore raw

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?

-Dan Christian

#1 lore raw

On Tuesday 03 February 2004 00:37, Dan Christian wrote:

Hi Dan,

Quoted 8 lines

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/[email protected]?nav=index.html|
ChangeSet@-12w

ciao, Marc

#2 lore raw
In reply to Dan Christian

Hope this hasn't been posted already.

Not sure if I am right or not on this but this seems to be related, at least on my box, to the APIC IDs of the CPUs. I am using an Intel SE7500CW, populated with 2x XEONs. The APIC ID's of the CPUs are 0 & 1 for the first physical CPU, and 6 & 7 for the second physical CPU (don't ask me why). If I don't use NR_CPUs = 8, I don't seem to see the second physical CPU. Someone correct me if I'm wrong.

-James

Quoted 15 lines · Dan Christian

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?

-Dan Christian

#3 lore raw
Quoted 1 line · James Schmidt

Hope this hasn't been posted already.

several times. The fix is in 2.4.25pre

Dave