> -----Original Message----- > From: Andi Kleen [mailto:[EMAIL PROTECTED]
> Why are you saying it can't be used by the host? The stack > should be fully ready for it. Sorry, I should have said "it can't be used by the host to the full potential of the feature" :-). It does work for us now, as a "driver only" implementation, but setting IRQ affinity from the kernel (as well as couple other decisions that we would like host to make, rather than making them in the driver) should help quite a bit. > > The only small piece missing is a way to set the IRQ affinity > from the kernel, but that can be simulated from user space by > tweaking them in /proc. If you have a prototype patch adding > the kernel interfaces wouldn't be that hard neither. Agreed, at this point we should put a patch forward and tweak the kernel interface later on. > > Also how about per CPU TX completion interrupts? Yes, a channel can have separate Tx completion and RX MSI-X interrupts (and an exception MSI-X interrupt, if desired). It's up to 64 MSI-X interrupts total. > > -Andi > - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
