Skip to contentSkip to conversation

Question on CONFIG_IRQBALANCE / 2.6.x

DISCUSSION Joerg Sommrey 3 participants 5 messages Feb 18, 2005 – Feb 20, 2005

lore
Share & tools
lore
#0 lore raw

Hi all,

there's something I don't understand: With IRQBALANCE *enabled* almost all interrupts are processed on CPU0. This changed in an unexpected way after disabling IRQBALANCE: now all interrupts are distributed uniformly to both CPUs. Maybe it's intentional, but it's not what I expect when a config option named IRQBALANCE is *disabled*.

Can anybody comment on this?

Thanks,
-jo

Signature · 1 line
-rw-r--r--  1 jo users 63 2005-02-18 21:21 /home/jo/.signature
#1 lore raw
Quoted 8 lines

there's something I don't understand: With IRQBALANCE *enabled* almost all interrupts are processed on CPU0. This changed in an unexpected way after disabling IRQBALANCE: now all interrupts are distributed uniformly to both CPUs. Maybe it's intentional, but it's not what I expect when a config option named IRQBALANCE is *disabled*.

Can anybody comment on this?

If you have a Pentium 3 based system, by default they'll round robin. If you turn on IRQbalance, they won't move until the traffic gets high enough load to matter. That's presumably what you're seeing.

m.

#2 lore raw
Quoted 7 lines · Martin J. Bligh
Quoted 7 lines

there's something I don't understand: With IRQBALANCE *enabled* almost all interrupts are processed on CPU0. This changed in an unexpected way after disabling IRQBALANCE: now all interrupts are distributed uniformly to both CPUs. Maybe it's intentional, but it's not what I expect when a config option named IRQBALANCE is *disabled*.

Quoted 5 lines
Quoted 1 line

Can anybody comment on this?

If you have a Pentium 3 based system, by default they'll round robin. If you turn on IRQbalance, they won't move until the traffic gets high enough load to matter. That's presumably what you're seeing.

It's an Athlon box that propably has the same behaviour. Just another question on this topic: with IRQBALANCE enabled, almost all interupts are routet to CPU0. Lately irq 0 runs on CPU1 and never returns to CPU0
- is there any obvious reason for that?

-jo

Signature · 1 line
-rw-r--r--  1 jo users 63 2005-02-18 23:29 /home/jo/.signature
#3 lore raw
Quoted 15 lines · Joerg Sommrey
Quoted 11 lines · Martin J. Bligh
Quoted 7 lines

there's something I don't understand: With IRQBALANCE *enabled* almost all interrupts are processed on CPU0. This changed in an unexpected way after disabling IRQBALANCE: now all interrupts are distributed uniformly to both CPUs. Maybe it's intentional, but it's not what I expect when a config option named IRQBALANCE is *disabled*.

Can anybody comment on this?

If you have a Pentium 3 based system, by default they'll round robin. If you turn on IRQbalance, they won't move until the traffic gets high enough load to matter. That's presumably what you're seeing.

Quoted 4 lines

It's an Athlon box that propably has the same behaviour. Just another question on this topic: with IRQBALANCE enabled, almost all interupts are routet to CPU0. Lately irq 0 runs on CPU1 and never returns to CPU0
- is there any obvious reason for that?

Note that it is a popular recommendation to -disable- CONFIG_IRQBALANCE, and then run the userspace 'irqbalanced'.

Jeff

#4 lore raw
In reply to Joerg Sommrey
Quoted 8 lines
Quoted 8 lines
Quoted 7 lines

there's something I don't understand: With IRQBALANCE *enabled* almost all interrupts are processed on CPU0. This changed in an unexpected way after disabling IRQBALANCE: now all interrupts are distributed uniformly to both CPUs. Maybe it's intentional, but it's not what I expect when a config option named IRQBALANCE is *disabled*.

Can anybody comment on this?

Quoted 8 lines
Quoted 3 lines

If you have a Pentium 3 based system, by default they'll round robin. If you turn on IRQbalance, they won't move until the traffic gets high enough load to matter. That's presumably what you're seeing.

It's an Athlon box that propably has the same behaviour. Just another question on this topic: with IRQBALANCE enabled, almost all interupts are routet to CPU0. Lately irq 0 runs on CPU1 and never returns to CPU0
- is there any obvious reason for that?

If it's not getting interrupts at 1010 per second or so, it won't rotate them, on the grounds it's not worthwhile.

M.