[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130108225833.GA4193@electric-eye.fr.zoreil.com>
Date: Tue, 8 Jan 2013 23:58:33 +0100
From: Francois Romieu <romieu@...zoreil.com>
To: Timo Teras <timo.teras@....fi>
Cc: netdev@...r.kernel.org
Subject: Re: r8169 rx_missed increasing in bursts (regression)
Timo Teras <timo.teras@....fi> :
[...]
> My current hypothesis is that due to high softirq and recent(ish)
> commit da78dbf "r8169: remove work from irq handler" moving more work
> to softirq makes the receive path now suffer from latency from getting
> irq to reading packets from the NIC on these boxes. And that at times
> the rx fifo can get full causing a missed packet or so.
This hypothesis won't explain the regression in 3.3.8 since 3.3.x does
not include commit da78dbf.
Do you notice any netdev watchdog message in dmesg ?
'perf top' may exhibit something unusual too.
> This might be further escalated by the bug fixed in commit 7dbb491
> "r8169: avoid NAPI scheduling delay" (which is not present in -stable
> trees).
Right, it would had been worth adding to -stable.
However it only 1) is a problem for 3.4.x (fixed in 3.5) and 2) triggers
when returning from the slow work thread - which should not be used much.
[...]
> So would it be sensible to do something like:
> -#define NUM_RX_DESC 256 /* Number of Rx descriptor registers */
> +#define NUM_RX_DESC 512 /* Number of Rx descriptor registers */
You can try it but it may actually increase the amount of heavy work done
in softirq.
> And cherry-picking the commit 7dbb491? Perhaps this could be pushed to
> the -stable queues too.
3.4.x at most.
--
Ueimor
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists