netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: P@draigBrady.com
To: Chris Carpinello <chriscarpinello@hotmail.com>
Cc: netdev@oss.sgi.com
Subject: Re: e1000 w/ NAPI + SMP = 99% CPU utilization
Date: Tue, 08 Jun 2004 13:34:52 +0100	[thread overview]
Message-ID: <40C5B26C.7030305@draigBrady.com> (raw)
In-Reply-To: <BAY1-F101MkaFmV8ih90004a5a7@hotmail.com>

Chris Carpinello wrote:
> With a stock 2.6.5 kernel, I'm building the e1000 driver as a module
> w/ NAPI turned on for an SMP host (Dell PowerEdge 1650 with 4 1Gb
> Intel NICs).  ksoftirqd/0 is using 99% CPU utilization.  However, when
> I recompile the kernel with NAPI turned off, ksoftirqd/0 behaves
> normally.  Likewise, when I leave NAPI configured but turn off SMP
> support, ksoftirqd is fine.  The system in question has 2x Intel
> Corp. 82544EI (rev 02) and 2x Intel Corp. 82543GC (rev 02).
> 
> I'm willing to test patches.  Please CC me on responses, as I'm not
> subscribed.  Thanks.

At what packet rate does it go to 100%?
Anyway it's not much to worry about as
it's in polling mode.

One thing which should help is to share
the work across your CPUs. `cat /proc/interrupts`
will show the interrupts for your nics.
Then you can bind the interrupt to a particular CPU like:

echo 1 > /proc/irq/$num/smp_affinity
echo 2 > /proc/irq/$num/smp_affinity
echo 4 > /proc/irq/$num/smp_affinity
echo 8 > /proc/irq/$num/smp_affinity

Pádraig.

  reply	other threads:[~2004-06-08 12:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-07 19:08 e1000 w/ NAPI + SMP = 99% CPU utilization Chris Carpinello
2004-06-08 12:34 ` P [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-08 18:14 Chris Carpinello
2004-06-09  7:51 ` Robert Olsson
2004-06-09  9:01   ` P

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=40C5B26C.7030305@draigBrady.com \
    --to=p@draigbrady.com \
    --cc=chriscarpinello@hotmail.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).