Mike Tancsa wrote:
> At 05:19 PM 12/5/2007, Philipp Wuensche wrote:
>
>> After switching to net.isr.direct=0 and 346609775 good packets later, RX
>> overruns haven't increased by one! Thats nice. Still interrupt is using
>> up the CPU. I'm not quite sure if polling would help now!?
>
> Polling is
At 05:19 PM 12/5/2007, Philipp Wuensche wrote:
After switching to net.isr.direct=0 and 346609775 good packets later, RX
overruns haven't increased by one! Thats nice. Still interrupt is using
up the CPU. I'm not quite sure if polling would help now!?
Polling is helpful to prevent livelock. Not
Mike Tancsa wrote:
> At 12:23 PM 12/5/2007, Philipp Wuensche wrote:
>> Mike Tancsa wrote:
>> > At 07:14 PM 12/4/2007, Philipp Wuensche wrote:
>> >
>> >> The debug output of em0 looks like this:
>> >>
>> >> em0: CTRL = 0x40140248 RCTL = 0x8002
>> >> em0: Packet buffer = Tx=20k Rx=12k
>> >> em0: Flow
At 12:23 PM 12/5/2007, Philipp Wuensche wrote:
Mike Tancsa wrote:
> At 07:14 PM 12/4/2007, Philipp Wuensche wrote:
>
>> The debug output of em0 looks like this:
>>
>> em0: CTRL = 0x40140248 RCTL = 0x8002
>> em0: Packet buffer = Tx=20k Rx=12k
>> em0: Flow control watermarks high = 10240 low = 8740
Mike Tancsa wrote:
> At 07:14 PM 12/4/2007, Philipp Wuensche wrote:
>
>> The debug output of em0 looks like this:
>>
>> em0: CTRL = 0x40140248 RCTL = 0x8002
>> em0: Packet buffer = Tx=20k Rx=12k
>> em0: Flow control watermarks high = 10240 low = 8740
>> em0: tx_int_delay = 66, tx_abs_int_delay = 6
At 07:14 PM 12/4/2007, Philipp Wuensche wrote:
The debug output of em0 looks like this:
em0: CTRL = 0x40140248 RCTL = 0x8002
em0: Packet buffer = Tx=20k Rx=12k
em0: Flow control watermarks high = 10240 low = 8740
em0: tx_int_delay = 66, tx_abs_int_delay = 66
em0: rx_int_delay = 32, rx_abs_int_d
Adrian Chadd wrote:
> On 05/12/2007, Philipp Wuensche <[EMAIL PROTECTED]> wrote:
>
>> As I understand it, and correct me if I'm wrong, polling helps against
>> high interrupt rates but for that intel gigabit cards have interrupt
>> moderation. We don't have a problem with interrupts (20% CPU) at t
Robert Watson wrote:
>
> Could you show us the output from "top -S" left running for a few
> minutes in the steady state.
>
> Could you try setting the sysctl net.isr.direct to 0, and see how that
> affects performance, CPU time reports, and "top -S" output?
I first had too look up what net.isr.