[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.
Brice Goglin brice.goglin at gmail.comFri Oct 23 14:37:14 PDT 2009
- Previous message: [Beowulf] eth-mlx4-0/15
- Next message: [Beowulf] eth-mlx4-0/15
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kubrick 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? These are multiple interrupt queues. The driver probably setups one per core (or one send and one recv queue per core) for each physical NIC. Brice
- Previous message: [Beowulf] eth-mlx4-0/15
- Next message: [Beowulf] eth-mlx4-0/15
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
