public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Paweł Krawczyk" <kravietz@aba.krakow.pl>
Cc: Jamie Lokier <lk@tantalophile.demon.co.uk>,
	zhengchuanbo <zhengcb@netpower.com.cn>,
	"linux-kernel @ vger. kernel. org" <linux-kernel@vger.kernel.org>
Subject: Re: about the tuning of eepro100
Date: Sat, 10 Aug 2002 14:18:54 -0400	[thread overview]
Message-ID: <3D55590E.4020902@mandrakesoft.com> (raw)
In-Reply-To: 20020810180256.GD25611@aba.krakow.pl

Paweł Krawczyk wrote:
> On Sat, Aug 10, 2002 at 06:55:58PM +0100, Jamie Lokier wrote:
> 
> 
>>I don't think you will get better than 90% performance, but if you do
>>please let me know!  I have written another e100 driver, in an attempt
>>to transmit and receive small packets at the maximum possible rate.
>>In tests, it would not even transmit at 100% small packets on our 82558.
>>(I didn't do that test on our 82559).
> 
> 
> Maybe we were looking for separate things - I had a firewall box with
> 100base-TX interfaces and when flooding it at full rate with small
> (40 bytes, i.e. empty IP headers) packets the system was unusable
> because of the interrupt rate. After I turned the bundling on, there
> was no signs of overload. Of course, I tested throughput of the
> card as well but on the IP level there was no difference I could
> worry about. But as I said, this was a firewall box and I was looking
> for a way to stop possible DOS, not for tiny packet delivery time
> slowdown, which may be important in other applications.


Sounds like you need the NAPI version of eepro100 or e100...  NAPI is 
designed to eliminate the overhead that you describe.

	Jeff





      reply	other threads:[~2002-08-10 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-10  9:38 about the tuning of eepro100 zhengchuanbo
2002-08-10  9:51 ` Paweł Krawczyk
2002-08-10 10:09   ` Adrian Bunk
2002-08-10 17:55   ` Jamie Lokier
2002-08-10 18:02     ` Paweł Krawczyk
2002-08-10 18:18       ` Jeff Garzik [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=3D55590E.4020902@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=kravietz@aba.krakow.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lk@tantalophile.demon.co.uk \
    --cc=zhengcb@netpower.com.cn \
    /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