Thread (1 message) 1 message, 1 author, 2002-03-08

Re: Ethernet, kernel bug/weakness

From: Harald Welte <laforge@gnumonks.org>
Date: 2002-03-08 08:03:41

On Thu, Mar 07, 2002 at 03:50:04PM -0500, Ruhland, Paul wrote:
Effect:
--
Once the ethernet traffic goes above the critical point described above, all
cpu cycles are spent servicing the ethernet traffic.
This is a common problem, also found with gigabit ethernet and large x86
boxes (or 100MBit and medium x86 boxes), as soon as you start shooting at them
with foll wire speed 20bytes IP packets.

It is well-known and about two years ago Jamal Hadi Selim and others were
solving the problem for a couple of example ethernet chips by using IRQ
mitigation.  This way the packets will get dropped on the network card
itself.

Seems like your driver isn't using this strategy for some strange reason.

Alternatively you can also try to detect high load within the driver and
switch to polling mode - this also has been implemented successfully in
some drivers, IIRC.
Paul Ruhland
--
Live long and prosper
- Harald Welte / laforge@gnumonks.org               http://www.gnumonks.org/
============================================================================
GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M+
V-- PS++ PE-- Y++ PGP++ t+ 5-- !X !R tv-- b+++ !DI !D G+ e* h--- r++ y+(*)

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help