netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Olsson <Robert.Olsson@data.slu.se>
To: Greg Banks <gnb@melbourne.sgi.com>
Cc: "David S. Miller" <davem@redhat.com>,
	Jeff Garzik <jgarzik@pobox.com>,
	Linux Network Development list <netdev@oss.sgi.com>
Subject: [PATCH] make tg3 NAPI support configurable
Date: Fri, 19 Dec 2003 14:20:02 +0100	[thread overview]
Message-ID: <16354.64258.364153.488309@robur.slu.se> (raw)
In-Reply-To: <3FE2F3A7.2A109F28@melbourne.sgi.com>


Greg Banks writes:

 > I've been having some issues with irq rates and cpu usage in the
 > tg3 driver.  In short, on Altix machines they're far too high.
 > It turned out that reverting the driver to its pre-NAPI interrupt
 > coalescing scheme made the situation a lot better.
 > 
 > How much better?  Running 8192 byte UDP packets across gige
 > with NAPI takes 99.5% of a CPU to service 29,100 irqs per second.
 > With the pre-NAPI code the figures are 36.0% CPU and 4880 irq/sec.
 > Similar improvements are seen for non-fragmented UDP and for TCP.

 Hello!

 You can use coalescing with NAPI as well, e1000 and other drivers
 are doing this. This will give you same interrupt rates as non-
 NAPI at low load and "polling" without any interrupts at high load.

 Furthermore NAPI can be extended to schedule dev->poll even for TX-
 interrupts. There is pacth for e1000 doing this. We see about 5-8% 
 overall system packet improvement with this.

 Cheers.
					--ro

  reply	other threads:[~2003-12-19 13:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-19 12:48 [PATCH] make tg3 NAPI support configurable Greg Banks
2003-12-19 13:20 ` Robert Olsson [this message]
2004-01-11  1:49   ` Jeff Garzik
2004-01-12  0:12     ` Greg Banks
2004-01-13 19:09     ` Robert Olsson
  -- strict thread matches above, loose matches on Subject: below --
2004-01-14  0:23 Feldman, Scott
2004-01-15  8:01 jc

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=16354.64258.364153.488309@robur.slu.se \
    --to=robert.olsson@data.slu.se \
    --cc=davem@redhat.com \
    --cc=gnb@melbourne.sgi.com \
    --cc=jgarzik@pobox.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).