LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Welte <laforge@gnumonks.org>
To: "Ruhland, Paul" <PRuhland@microwavedata.com>
Cc: "'linuxppc-dev@lists.linuxppc.org'" <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Ethernet, kernel bug/weakness
Date: Fri, 8 Mar 2002 09:03:41 +0100	[thread overview]
Message-ID: <20020308090341.V6936@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <A60FFE6CA339C742BE11C311EA8BFF5401637E@mdsms2.inside.mdsroc.com>; from PRuhland@microwavedata.com on Thu, Mar 07, 2002 at 03:50:04PM -0500


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/

      parent reply	other threads:[~2002-03-08  8:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-07 20:50 Ethernet, kernel bug/weakness Ruhland, Paul
2002-03-07 21:13 ` Dan Malek
2002-03-08  8:03 ` Harald Welte [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020308090341.V6936@sunbeam.de.gnumonks.org \
    --to=laforge@gnumonks.org \
    --cc=PRuhland@microwavedata.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox