![]() | |||||||||||||
Messages in this thread |
> Yes, I think that the driver definitely needs to be in control of how > many MSI-X interrupts it gets. The current mthca driver knows that it > has three different event queues -- one for firmware command events, > one for async events such as link up/down, and one for actual tx/rx > completions -- and uses a separate MSI-X message for each one. The idea was always to have MSI by default and if the driver wants MSI-X it turns off standard MSI and does its own thing completely. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-06-08 13:39 [from the cache] ©2003-2008 | |||||||||||||