diff options
| author | Eric Dumazet <[email protected]> | 2012-02-15 20:43:11 +0000 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2012-02-19 18:57:50 -0500 |
| commit | 11aad99af6ef629ff3b05d1c9f0936589b204316 (patch) | |
| tree | 36a35eb1de09c8c264937dc06f8f35b9c0e5805d /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | cd961c2ca98efbe7d738ca8720673fc03538b2b1 (diff) | |
atl1c: dont use highprio tx queue
This driver attempts to use two TX rings but lacks proper support :
1) IRQ handler only takes care of TX completion on first TX ring
2) the stop/start logic uses the legacy functions (for non multiqueue
drivers)
This means all packets witk skb mark set to 1 are sent through high
queue but are never cleaned and queue eventualy fills and block the
device, triggering the infamous "NETDEV WATCHDOG" message.
Lets use a single TX ring to fix the problem, this driver is not a real
multiqueue one yet.
Minimal fix for stable kernels.
Reported-by: Thomas Meyer <[email protected]>
Tested-by: Thomas Meyer <[email protected]>
Signed-off-by: Eric Dumazet <[email protected]>
Cc: Jay Cliburn <[email protected]>
Cc: Chris Snook <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions