Archives


- Beowulf
- Beowulf Announce
- Scyld-users
- Beowulf on Debian

[Beowulf] eth-mlx4-0/15

Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.

Search

Joachim Worringen worringen at googlemail.com
Sun Oct 25 03:12:40 PDT 2009


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 <robertkubrick at 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 at beowulf.org sponsored by Penguin Computing
> To change your subscription (digest mode or unsubscribe) visit
> http://www.beowulf.org/mailman/listinfo/beowulf
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.scyld.com/pipermail/beowulf/attachments/20091025/ddea7a8e/attachment.html


More information about the Beowulf mailing list