netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Olsson <Robert.Olsson@data.slu.se>
To: Andi Kleen <ak@muc.de>
Cc: jamal <hadi@cyberus.ca>, 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: Sat, 23 Apr 2005 18:56:49 +0200	[thread overview]
Message-ID: <17002.32337.149675.535048@robur.slu.se> (raw)
In-Reply-To: <20050422183004.GC10598@muc.de>


Andi Kleen writes:

 > Well, did you ever test a non routing workload?

 Well Linux. 2.6.11.7 SMP kernel using one CPU driver e1000 NAPI - 
 no-NAPI. Opteron 1.6 GHz e1000 w 82546GB. 

Driver                   sec       NAPI    no-NAPI
-------------------------------------------------
131072 131072      4    60.00      24.80    25.11   Mbits/sec
131072 131072    512    60.00     941.57   941.53   
131072 131072   1024    60.00     941.60   941.61   
131072 131072   2048    60.00     941.60   941.61   
131072 131072   4096    60.00     941.60   941.57   
131072 131072   8192    60.00     941.60   941.61   
131072 131072  16384    60.00     941.28   941.60   
131072 131072  32768    60.00     941.61   941.27   

About the same TCP performance I would say.

Now another TCP test... about to deliver TCP even under severe network
conditions. Say a big TCP server with many NIC's and one NIC gets DOS'ed.  

In this case a DoS attack at 820 kpps at a different NIC not the one 
with the netperf test. (Actually it's doing forwarding at 330 kpps) and 
at the same time serving TCP, netserver in our case.

Driver                            NAPI    no-NAPI
-------------------------------------------------
131072 131072      4    60.00      25.59     N/A
131072 131072    512    60.00     836.79     N/A
131072 131072   1024    60.00     709.65     0.02
131072 131072   2048    60.00     734.34     N/A
131072 131072   4096    60.00     753.99     N/A
131072 131072   8192    60.00     695.57     N/A
131072 131072  16384    60.00     815.50     N/A
131072 131072  32768    60.00     690.33     N/A

So even when we are under hard attack we can serve TCP at very decent 
rates with the NAPI driver. 

Without NAPI are not able to deliver any TCP service at all.

Cheers.
					--ro

  parent reply	other threads:[~2005-04-23 16:56 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 [this message]
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
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.32337.149675.535048@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=hadi@cyberus.ca \
    --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).