From: Robert Olsson <Robert.Olsson@data.slu.se>
To: Andi Kleen <ak@muc.de>
Cc: Greg Banks <gnb@sgi.com>, Arthur Kepner <akepner@sgi.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
netdev@oss.sgi.com, davem@redhat.com
Subject: Re: NAPI, e100, and system performance problem
Date: Fri, 22 Apr 2005 16:52:50 +0200 [thread overview]
Message-ID: <17001.4034.250460.397016@robur.slu.se> (raw)
In-Reply-To: <m1hdhzyrdz.fsf@muc.de>
Andi Kleen writes:
> We have seen similar behaviour. With NAPI some benchmarks run
> a lot slower than on a driver on the same hardware/NIC without NAPI.
> This can be even observed with simple tests like netperf single stream
> between two boxes.
>
> There seems to be also some problems with bidirectional traffic, although
> I have not fully tracked them down to NAPI yet.
>
> There is definitely some problem in NAPI land ...
Well NAPI enforces very little policy it leaves a lot of freedom for
driver writers. Driver design i.e do work in interrupt or softirq, use
of interrupt mitigation etc etc. It's minimal approach to solve some very
severe problem we had with networking stack at a time were linux OS was not
an option at all. Knowing also a bit about the background as we experimented
quite a bit about possible options. Alexey did the final kernel design
it got very well integrated into the kernel and softirq linux model.
Dave understood directly and included the framework directly.
So help us sort out the problems. And of course there are some differences
or "issues" as we know every design has it's trade-off is bit Jamal said you
can't optimize in both ends. Or help us replace it with something thats
solves the same problems even better.
Cheers.
--ro
BTW We talked with Intel folks about leaving irq disabled when reading
ISR and some status bit were. This can save some PCI-accesses I don't
if any experiments are done. MSI is also interesting in this aspect...
next prev parent reply other threads:[~2005-04-22 14:52 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 6:11 NAPI, e100, and system performance problem Brandeburg, Jesse
2005-04-18 12:14 ` jamal
2005-04-18 15:36 ` Robert Olsson
2005-04-18 16:55 ` Arthur Kepner
2005-04-18 19:34 ` Robert Olsson
2005-04-18 20:26 ` jamal
2005-04-19 5:55 ` Greg Banks
2005-04-19 18:36 ` David S. Miller
2005-04-19 20:38 ` NAPI and CPU utilization [was: NAPI, e100, and system performance problem] Arthur Kepner
2005-04-19 20:52 ` Rick Jones
2005-04-19 21:09 ` David S. Miller
[not found] ` <20050420145629.GH19415@sgi.com>
2005-04-20 15:15 ` NAPI, e100, and system performance problem jamal
2005-04-22 11:36 ` Andi Kleen
2005-04-22 12:33 ` jamal
2005-04-22 17:21 ` Andi Kleen
2005-04-22 18:18 ` jamal
2005-04-22 18:30 ` Andi Kleen
2005-04-22 18:37 ` Arthur Kepner
2005-04-22 18:52 ` David S. Miller
[not found] ` <Pine.LNX.4.61.0504241845070.2934@linux.site>
2005-04-25 11:25 ` jamal
2005-04-25 18:51 ` David S. Miller
2005-04-25 11:41 ` jamal
2005-04-25 12:16 ` Jamal Hadi Salim
2005-04-22 19:01 ` jamal
2005-04-22 19:07 ` David S. Miller
2005-04-22 19:21 ` jamal
2005-04-23 20:50 ` Robert Olsson
2005-04-23 16:56 ` Robert Olsson
2005-04-22 23:28 ` Greg Banks
2005-04-22 23:40 ` Stephen Hemminger
2005-04-22 23:43 ` David S. Miller
2005-04-23 2:51 ` Stephen Hemminger
2005-04-23 17:54 ` Robert Olsson
2005-04-23 3:04 ` jamal
2005-04-23 17:14 ` Robert Olsson
2005-04-22 14:52 ` Robert Olsson [this message]
2005-04-22 15:37 ` jamal
2005-04-22 17:22 ` Andi Kleen
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=17001.4034.250460.397016@robur.slu.se \
--to=robert.olsson@data.slu.se \
--cc=ak@muc.de \
--cc=akepner@sgi.com \
--cc=davem@redhat.com \
--cc=gnb@sgi.com \
--cc=jesse.brandeburg@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).