82557/8/9 Ethernet Pro 100 interrupt mitigation support
Subsystems (2)
Hello everyone,
I have several systems with three integrated Intel 82559 (I *think*).
Does someone know if these boards support hardware interrupt mitigation? I.e. is it possible to configure them to raise an IRQ only if their hardware buffer is full OR if some given time (say 1 ms) has passed and packets are available in their hardware buffer.
I've been using the eepro100 driver up to now, but I'm about to try the e100 driver. Would I have to use NAPI? Or is this an orthogonal feature?
Regards.
00:08.0 Ethernet controller: Intel Corporation 82557/8/9 Ethernet Pro 100 (rev 08)
Subsystem: Intel Corporation EtherExpress PRO/100B (TX)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (2000ns min, 14000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 10
Region 0: Memory at e6400000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at d800 [size=64]
Region 2: Memory at e6100000 (32-bit, non-prefetchable) [size=1M]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
00:09.0 Ethernet controller: Intel Corporation 82557/8/9 Ethernet Pro 100 (rev 08)
Subsystem: Intel Corporation EtherExpress PRO/100B (TX)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (2000ns min, 14000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 11
Region 0: Memory at e6403000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at dc00 [size=64]
Region 2: Memory at e6200000 (32-bit, non-prefetchable) [size=1M]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
00:0a.0 Ethernet controller: Intel Corporation 82557/8/9 Ethernet Pro 100 (rev 08)
Subsystem: Intel Corporation EtherExpress PRO/100B (TX)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (2000ns min, 14000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 12
Region 0: Memory at e6402000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at e000 [size=64]
Region 2: Memory at e6000000 (32-bit, non-prefetchable) [size=1M]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
Quoted 7 lines · Marc Sigler
Hello everyone,
I have several systems with three integrated Intel 82559 (I *think*).
Does someone know if these boards support hardware interrupt mitigation? I.e. is it possible to configure them to raise an IRQ only if their hardware buffer is full OR if some given time (say 1 ms) has passed and packets are available in their hardware buffer.
I've been using the eepro100 driver up to now, but I'm about to try the e100 driver. Would I have to use NAPI? Or is this an orthogonal feature?
the software developers manual for this part is available on our e1000.sf.net page here:
http://downloads.sourceforge.net/e1000/OpenSDM_55x_10c.pdf?modtime=1040083200&big_mirror=0
e100 hardware (as far as I can see from the specs) doesn't support any irq mitigation, so you'll need to run in NAPI mode if you want to throttle irq's. the in-kernel e100 already runs in NAPI mode, so that's already covered.
beware that the eepro100 driver is scheduled for removal (2.6.25 or so).
Cheers,
Auke
Quoted 10 lines · Auke
Quoted 9 lines · Marc Sigler
Hello everyone,
I have several systems with three integrated Intel 82559 (I *think*).
Does someone know if these boards support hardware interrupt mitigation? I.e. is it possible to configure them to raise an IRQ only if their hardware buffer is full OR if some given time (say 1 ms) has passed and packets are available in their hardware buffer.
Quoted 8 lines
Quoted 3 lines
I've been using the eepro100 driver up to now, but I'm about to try the e100 driver. Would I have to use NAPI? Or is this an orthogonal feature?
the software developers manual for this part is available on our e1000.sf.net page here:
http://downloads.sourceforge.net/e1000/OpenSDM_55x_10c.pdf?modtime=10400
83200&big_mirror=0
Quoted 8 lines
e100 hardware (as far as I can see from the specs) doesn't support any irq mitigation, so you'll need to run in NAPI mode if you want to throttle irq's. the in-kernel e100 already runs in NAPI mode, so that's already covered.
beware that the eepro100 driver is scheduled for removal (2.6.25 or so).
We support mitigation of interrupts in a downloadable microcode on only a few pieces of hardware (revision id specific) in e100.c (see e100_setup_ucode)
If you really really wanted mitigation you could probably backport the microcode from the e100 driver in the 2.4.35 kernel for your specific hardware. This driver is versioned 2.X.
Beyond that I can't really offer much help in this case, but would certainly accept patches!
Jesse
Quoted 20 lines · Jesse Brandeburg
Quoted 18 lines · Auke Kok
Quoted 10 lines · Marc Sigler
I have several systems with three integrated Intel 82559 (I *think*).
Does someone know if these boards support hardware interrupt mitigation? I.e. is it possible to configure them to raise an IRQ only if their hardware buffer is full OR if some given time (say 1 ms) has passed and packets are available in their hardware buffer.
I've been using the eepro100 driver up to now, but I'm about to try the e100 driver. Would I have to use NAPI? Or is this an orthogonal feature?
e100 hardware (as far as I can see from the specs) doesn't support any irq mitigation, so you'll need to run in NAPI mode if you want to throttle irq's. the in-kernel e100 already runs in NAPI mode, so that's already covered.
Quoted 5 lines
Quoted 1 line
beware that the eepro100 driver is scheduled for removal (2.6.25 or so).
We support mitigation of interrupts in a downloadable microcode on only a few pieces of hardware (revision id specific) in
e100.c(seee100_setup_ucode)
http://lxr.linux.no/source/drivers/net/e100.c#L1176
OK.
How do I tell which revision id I have?
00:08.0 0200: 8086:1229 (rev 08)
00:09.0 0200: 8086:1229 (rev 08)
00:0a.0 0200: 8086:1229 (rev 08)
How much memory is available on the board to bundle packets? 3000 bytes?
Quoted 3 lines
If you really really wanted mitigation you could probably backport the microcode from the e100 driver in the 2.4.35 kernel for your specific hardware. This driver is versioned 2.X.
I forgot to mention I'm running 2.6.22.1-rt9.
I'm not sure why you mention 2.4.35?
The problem with e100 is that it fails to properly set up all three interfaces, which is why I'm stuck with eepro100.
Regards.
Quoted 32 lines · John Sigler
Quoted 21 lines · Jesse Brandeburg
Quoted 19 lines · Auke Kok
Quoted 11 lines · Marc Sigler
I have several systems with three integrated Intel 82559 (I *think*).
Does someone know if these boards support hardware interrupt mitigation? I.e. is it possible to configure them to raise an IRQ only if their hardware buffer is full OR if some given time (say 1 ms) has passed and packets are available in their hardware buffer.
I've been using the eepro100 driver up to now, but I'm about to try the e100 driver. Would I have to use NAPI? Or is this an orthogonal feature?
e100 hardware (as far as I can see from the specs) doesn't support any irq mitigation, so you'll need to run in NAPI mode if you want to throttle irq's. the in-kernel e100 already runs in NAPI mode, so that's already covered.
Quoted 6 lines
Quoted 2 lines
beware that the eepro100 driver is scheduled for removal (2.6.25 or so).
We support mitigation of interrupts in a downloadable microcode on only a few pieces of hardware (revision id specific) in
e100.c(seee100_setup_ucode)
Quoted 7 lines
OK.
How do I tell which revision id I have?
00:08.0 0200: 8086:1229 (rev 08)
00:09.0 0200: 8086:1229 (rev 08)
00:0a.0 0200: 8086:1229 (rev 08)
^^^^^^
rev 8
Quoted 2 lines
How much memory is available on the board to bundle packets? 3000 bytes?
yes, well, 3kB. I don't remember if the chip actually bundles interrupts after the dma complets or pends the dma while delaying the interrupt (I would guess it is the former)
Quoted 6 lines
Quoted 3 lines
If you really really wanted mitigation you could probably backport the microcode from the e100 driver in the 2.4.35 kernel for your specific hardware. This driver is versioned 2.X.
I forgot to mention I'm running 2.6.22.1-rt9.
I'm not sure why you mention 2.4.35?
because 2.4.35 has the "old" e100 driver from Intel, which has all sorts of support (and all sorts of complexity) for offloading and interrupt bundling, etc.
Quoted 2 lines
The problem with e100 is that it fails to properly set up all three interfaces, which is why I'm stuck with eepro100.
I remember working with you on this, but we left the issue with no solution because it appears your hardware has some specific issue with strange eeprom timings that we cannot reproduce.
you can try loading the ucode (that matches your revision id) using eepro100.
Jesse