From: Martin Josefsson <gandalf@wlug.westbo.se>
To: "Vladimir B. Savkin" <savkin@shade.msu.ru>
Cc: fxzhang@ict.ac.cn, linux-kernel@vger.kernel.org
Subject: Re: eepro100+NAPI failure
Date: 18 Mar 2003 21:54:44 +0100 [thread overview]
Message-ID: <1048020884.1521.60.camel@tux.rsn.bth.se> (raw)
In-Reply-To: <20030318202728.GA15796@tentacle.sectorb.msk.ru>
On Tue, 2003-03-18 at 21:27, Vladimir B. Savkin wrote:
> Hi!
>
> I'm planning to deploy Intel-based fast ethernet NICs on a busy
> router so I decided to try NAPI.
> To test NAPI performance, I've blasted a stream of short packets
> from another host using pktgen. The bad thing is that receiving host
> stopped responding to packets immediately. The effect is 100%
> reproducable, eventually it comes back though, black-out can last
> from a second to several minutes. Here is what I was able to catch
> after 'ethtool -s eth0 msglvl 0xfff':
I saw the same problem when I tested it a while back, didn't have time
to investigate so my routers are running without NAPI right now :(
> Can anyone help me to make NAPI work? Does anyone even use NAPI
> with eepro100, I guess not many people since the patch is pretty old
> and I could not find it ported to 2.4.21-pre.
I havn't heard of anyone using it. I've understood that the recieve path
in the eepro100 chip can be quite fragile and has to be treated right or
it'll hang... maybe the NAPI patch changes things too much...
Anyway, please let me know if you manage to get it working
--
/Martin
Never argue with an idiot. They drag you down to their level, then beat you with experience.
next prev parent reply other threads:[~2003-03-18 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 20:27 Vladimir B. Savkin
2003-03-18 20:54 ` Martin Josefsson [this message]
2003-03-19 13:43 ` Vladimir B. Savkin
2003-03-19 18:21 ` Ion Badulescu
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=1048020884.1521.60.camel@tux.rsn.bth.se \
--to=gandalf@wlug.westbo.se \
--cc=fxzhang@ict.ac.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=savkin@shade.msu.ru \
/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
all inboxes | Powered by JetHome®