Re: CONFIG_IRQBALANCE for 64-bit x86 ?

[Mark Lord <lkml@rtr.ca>]

Mark Lord wrote:
> Arjan van de Ven wrote:
>> ..
>> I listed a few;
>> 1) it's policy 2) the memory is only needed for a short time (20 
>> seconds or so) on
>> single-socket machines
>> 3) it makes decisions on "subjective" information such as interrupt
>> device classes that the kernel currently just doesn't have (it could
>> grow that obviously), and is clearly policy information.
> ..
> 
> It's much more than just "policy".
> Distributing IRQs across available cores is *essential* functionality,
> not an optional "extra" as this would have it be.
> 
> After reading some of the replies, I installed it on my malfunctioning 
> 64-bit
> system, but discovered it does not perform nearly as well as the kernel 
> solution
> in the 32-bit system does.
> 
> Responsiveness was jerky, and it took a long time to have any noticeable 
> effect.
> 
> And in the end, it still just assigned IRQs to two of the four available 
> cores.
> Which still results in the task scheduler fighting against IRQs more 
> than necessary.
> 
> Much of this could be due to a slow response curve in the userspace 
> balancer (?),
> but I have not yet examined it for such bugs.  Hopefully it also is 
> clever enough
> to mlock() itself, and to run at a low RT priority ?
> It really does need to respond *quickly* to changes in IRQ load,
> as otherwise I see dropouts on sound playback (let along video..) and 
> the like.
> 
> The vast majority of Linux machines are "single package", and this software
> appears to be designed more for multi package, and doesn't do a great 
> job here
> on the single package Intel cores I have (Core2duo, Core2quad).
..

All of which reminds me of perhaps *the* most important reason to keep
core functionality like "IRQ distribution" *inside* the kernel:

   It has to pass peer review on this mailing list.

External utilities have no such accountability, and can generally just
follow the whims of their maintainers at the expense of kernel performance.

Not that this may be the case (or not) here, but..

Cheers