I assume these are MSI-X interrupts of the one Mellanox driver instance. This feature allows to spread interrupts more or less evenly across CPUs, in conjunction with multiple send/recv queues.
Each PCI device has a single driver (unless we talk about virtualized I/O, which does not apply here). But a single driver can serve any number of interrupts. Joachim On Fri, Oct 23, 2009 at 2:25 AM, Robert Kubrick <robertkubr...@gmail.com>wrote: > I noticed my machine has 16 drivers in the /proc/interrupts table marked as > eth-mlx4-0 to 15, in addition to the usual mlx-async and mlx-core drivers. > The server runs Linux Suse RT, has an infiniband interface, OFED 1.1 > drivers, and 16 Xeon MP cores , so I'm assuming all these eth-mlx4 drivers > are supposed to do "something" with each core. I've never seen these irq > managers before. When I run infiniband apps the interrupts go to both > mlx-async and eth-mlx4-0 (just 0, all the other drivers don't get any > interrupts). Also the eth name part looks suspicious. > > I can't find any reference online, any idea what these drivers are about? > _______________________________________________ > Beowulf mailing list, Beowulf@beowulf.org sponsored by Penguin Computing > To change your subscription (digest mode or unsubscribe) visit > http://www.beowulf.org/mailman/listinfo/beowulf >
_______________________________________________ Beowulf mailing list, Beowulf@beowulf.org sponsored by Penguin Computing To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
