em0: <Intel(R) PRO/1000 Network Connection, Version - 2.1.7> port 0xd000-0xd03f mem 0xd0000000-0xd001ffff irq 24 at device 4.0 on pci3 em0: Ethernet address: 00:04:23:ba:7b:e4 em0: Speed:N/A Duplex:N/A em1: <Intel(R) PRO/1000 Network Connection, Version - 2.1.7> port 0xd100-0xd13f mem 0xd0020000-0xd003ffff irq 25 at device 4.1 on pci3 em1: Ethernet address: 00:04:23:ba:7b:e5 em1: Speed:N/A Duplex:N/A em2: <Intel(R) PRO/1000 Network Connection, Version - 2.1.7> port 0xd200-0xd23f mem 0xd0040000-0xd005ffff irq 26 at device 6.0 on pci3 em2: Ethernet address: 00:04:23:ba:7b:e6 em2: Speed:N/A Duplex:N/A em3: <Intel(R) PRO/1000 Network Connection, Version - 2.1.7> port 0xd300-0xd33f mem 0xd0060000-0xd007ffff irq 27 at device 6.1 on pci3 em3: Ethernet address: 00:04:23:ba:7b:e7 em3: Speed:N/A Duplex:N/A
maybe? On Fri, 2005-08-12 at 16:32 -0500, Matthew Lenz wrote: > On Fri, 2005-08-12 at 16:10 -0500, Bill Marquette wrote: > > I usually use: > > client: iperf -P 2 -w 128k -c server > > server: iperf -w 128k -s > > > > And I'd recommend using: > > http://dast.nlanr.net/Projects/Iperf/iperfdocs_1.7.0.html > > > > Also, I'm not sure FreeBSD uses polling mode for the em driver by > > default. Are all your NICs on the same IRQ, if not can you set them > > to the same IRQ? At least in OpenBSD same IRQ improves performance > > somewhat due to how interrupt handling works (if you're in the > > interrupt handler for IRQ x, loop through all devices on IRQ x and > > process anything they need done). > > > > --Bill > > I'm one of those linux guys. How does one determine a device's IRQ > under freebsd?
