All of lore.kernel.org
 help / color / mirror / Atom feed
From: P@draigBrady.com
To: netdev@oss.sgi.com
Subject: e100 NAPI performance
Date: Fri, 29 Aug 2003 11:16:46 +0100	[thread overview]
Message-ID: <3F4F280E.1020507@draigBrady.com> (raw)

Hi,
I didn't get any feedback on the following mail.

Also in case this patch wasn't noticed,
I think it's a no brainer to apply?
http://tardis.linux.ie/1637/sourceforge.net

cheers,
Pádraig.

-------- Original Message --------
Subject: e100 NAPI performance
Date: Mon, 25 Aug 2003 14:12:05 +0100
From: P@draigBrady.com
To: e1000-devel@lists.sourceforge.net

Hi,

I'm testing the latest e100 driver (3.0.0_dev13)
in a device here that is purely used to
capture traffic, and I'm testing with 64 byte packets.

I've turned on NAPI and can recv up to 120K packets/s
fine. (btw the driver without NAPI is
fine up to 101K packets/s). Above this though
the packet capture rate actually decreases

At 130K packets/s only 110K/s are received,
and 16K/s are rx fifo overruns.
I thought NAPI was supposed to keep a bound
on the worst case?

any advice on improving performance
like ethtool params or something?

CPU is 1.2GHz PIII
linux kernel is 2.4.20

                 reply	other threads:[~2003-08-29 10:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3F4F280E.1020507@draigBrady.com \
    --to=p@draigbrady.com \
    --cc=netdev@oss.sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.