From: Robert Olsson <Robert.Olsson@data.slu.se>
To: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: Robert Olsson <Robert.Olsson@data.slu.se>,
Jeff Garzik <jgarzik@pobox.com>,
linux-kernel@vger.kernel.org
Subject: Re: e1000 fixes (NAPI)
Date: Thu, 21 Nov 2002 11:43:11 +0100 [thread overview]
Message-ID: <15836.47295.808423.41648@robur.slu.se> (raw)
In-Reply-To: <20021120164319.A26918@vger.timpanogas.org>
Jeff V. Merkey writes:
>
> Need another fix. You need to reinstrument the tasklet schedule in the
> fill_rx_ring instread of doing the whole thing from interrupt. When the
> system is loaded at 100% saturation on gigbit with 300 byte packets or
> smaller, the driver does not allow any processes to run, and you cannot
> log in via ssh or any user space apps. This is severely busted.
>
> The later versions of the driver > 4.3.15 all exhibit this behavior and
> are extremely broken.
Where have you been? :-)
NAPI does RX processing in softirq. RX interrupts are just used to indicate
work. At high loads the consecutive RX polls gets run via ksoftirqd which
is under scheduler control also the RX softirq breakes for other work. This
makes the NAPI network stuff as very well behaved kernel citizen and also
gives network performance at any load.
More details is in the usenix paper;
http://www.cyberus.ca/~hadi/usenix-paper.tgz
Cheers.
--ro
next prev parent reply other threads:[~2002-11-21 10:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 19:01 Robert Olsson
2002-11-20 23:43 ` Jeff V. Merkey
2002-11-21 10:43 ` Robert Olsson [this message]
2002-11-21 18:05 ` Jeff V. Merkey
2002-11-21 18:10 ` Jeff V. Merkey
2002-11-21 17:13 ` Jeff Garzik
2002-11-21 18:30 ` Jeff V. Merkey
2002-11-21 17:31 ` Jeff Garzik
2002-11-21 22:03 ` Jeff V. Merkey
2002-11-21 1:18 Feldman, Scott
2002-11-22 10:21 Robert Olsson
2002-11-22 19:05 ` Jeff V. Merkey
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=15836.47295.808423.41648@robur.slu.se \
--to=robert.olsson@data.slu.se \
--cc=jgarzik@pobox.com \
--cc=jmerkey@vger.timpanogas.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®