Hi, I am sorry to repeat the question, but so far I didn't get an answer on whether MSI (Message Signaled Interrupts) handling is supposed to respect with /proc/irq/*/smp_affinity mask bits. No matter what affinity bits I am setting on my system, all MSIs are processed by CPU#0. Please see the original message quoted below; an answer e.g. whether the affinity_mask and MSI features are expected to work together at all, or whether there's an improvement in latest kernel codebase would be of great help. If I should rather post to a different mailing list/forum, please suggest which one. The system in question run on 2.6.18 vanilla kernel. Used NICs are Broadcom Nextreme II (bnx2 module). To comment one of the suggestions made in response to the original post: the userspace IRQ balancer actually uses the /proc/*/affinity_mask interface, which is THE thing that does not work on my machine. So the suggestion is not applicable in this case. Thanks, -Svata Svata Dedic wrote: > Hello, > > I am having troubles to set up network interfaces on our machine to > properly use SMP Linux features. There are two Broadcom Nextreme II > ethernet NICs onboard a 2x dual-core CPU machine. > > My kernel has SMP and Message-Signaled Interrupts (MSI) enabled. When I > boot with MSI enabled, I can see in /proc/interrupts that each of the > NICs got a unique interrupt assigned. But all traffic generated to the > 1st NIC goes to the CPU#0, other CPUs show 0 processed interrupts in the > /proc/interrupts. > > I tried to assign the interrupt to a specific CPU (single bit in > smp_affinity, tried each of the 4 CPU cores), with the same results; > althought smp_affinity said e.g. 4, everything was processed by CPU#0 > > When the machine booted with "pci=nomsi" kernel parameter, the NICs were > assigned a shared IO-APIC interrupt, but the intr processing was > properly distributed among CPU cores as requested by the affinity_mask. > > What am I doing wrong ? > > Thanks for any advice, > -Svata > - > To unsubscribe from this list: send the line "unsubscribe linux-net" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
