netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Olsson <Robert.Olsson@data.slu.se>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	gnb@sgi.com, hadi@cyberus.ca, ak@muc.de, akepner@sgi.com,
	jesse.brandeburg@intel.com, netdev@oss.sgi.com, davem@redhat.com
Subject: Re: NAPI, e100, and system performance problem
Date: Sat, 23 Apr 2005 19:54:13 +0200	[thread overview]
Message-ID: <17002.35781.813292.517029@robur.slu.se> (raw)
In-Reply-To: <20050423125153.65189ea0@localhost.localdomain>


Stephen Hemminger writes:

 > One of the problem with the dynamic schemes, is there is no generic infrastructure
 > to support it. There are some drivers that have tried dynamic schemes
 > but each seems to reinvent some adhoc scheme. Seems like a good area
 > for future research.

 Well how do decorrelate bursty network and more interesing at what 
 time level? I said this before... the only useful measure for mitigation
 setting was packets on RX ring.
 
 > Another related problem is some drivers use NAPI for both TX and RX and
 > this can cause asymmetric behavior and scheduling issues. The whole
 > dev->weight limit stuff assumes RX not TX usage of NAPI

 Well in the very beginning it was thought only RX yes, But it is possible 
 also to have TX buffer cleared etc in the ->poll routine to simplify 
 intr. acking. As implemented only RX packets updates the budget.
 From what I see in real life use this works well. Guess you noticed the 
 tests with e1000 and TCP just posted. 

 Anyway MSI will give us some new options in this area..

 Cheers.
					--ro

  reply	other threads:[~2005-04-23 17:54 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 [this message]
2005-04-23  3:04                     ` jamal
2005-04-23 17:14                     ` Robert Olsson
2005-04-22 14:52         ` Robert Olsson
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=17002.35781.813292.517029@robur.slu.se \
    --to=robert.olsson@data.slu.se \
    --cc=ak@muc.de \
    --cc=akepner@sgi.com \
    --cc=davem@davemloft.net \
    --cc=davem@redhat.com \
    --cc=gnb@sgi.com \
    --cc=hadi@cyberus.ca \
    --cc=jesse.brandeburg@intel.com \
    --cc=netdev@oss.sgi.com \
    --cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).