em driver, 82574L chip, and possibly ASPM

Jack Vogel jfvogel at gmail.com
Tue Feb 1 21:17:40 UTC 2011


But you aren't defining EM_MULTIQUEUE are you? (its not on by default)

Jack


On Tue, Feb 1, 2011 at 1:05 PM, Mike Tancsa <mike at sentex.net> wrote:

> On 2/1/2011 3:55 PM, Jack Vogel wrote:
> > Mike, just to remind me, are you running these 82574 adapters with MSIX ?
>
> Yes. Board is an Intel MB (S3420GPX). 8G RAM, AMD64. Kernel from a few
> days ago
>
>
> 0(backup3)# vmstat -i | grep em1
> irq257: em1:rx 0               113712958        159
> irq258: em1:tx 0                96623551        135
> irq259: em1:link                     488          0
> 0(backup3)# grep ^em1 /var/run/dmesg.boot
> em1: <Intel(R) PRO/1000 Network Connection 7.1.9> port 0x2000-0x201f mem
> 0xb4100000-0xb411ffff,0xb4120000-0xb4123fff irq 16 at device 0.0 on pci10
> em1: Using MSIX interrupts with 3 vectors
> em1: [ITHREAD]
> em1: [ITHREAD]
> em1: [ITHREAD]
> em1: Ethernet address: 00:15:17:ed:68:a4
> em1: link state changed to UP
> 0(backup3)#
> em1 at pci0:10:0:0:        class=0x020000 card=0x34ec8086 chip=0x10d38086
> rev=0x00 hdr=0x00
>    vendor     = 'Intel Corporation'
>    device     = 'Intel 82574L Gigabit Ethernet Controller (82574L)'
>    class      = network
>    subclass   = ethernet
>    cap 01[c8] = powerspec 2  supports D0 D3  current D0
>    cap 05[d0] = MSI supports 1 message, 64 bit
>    cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
>    cap 11[a0] = MSI-X supports 5 messages in map 0x1c enabled
> ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected
> ecap 0003[140] = Serial 1 001517ffffed68a4
>
>         ---Mike
>


More information about the freebsd-net mailing list