From: Karsten Desler <kdesler@soohrt.org>
To: Karsten Desler <kdesler@soohrt.org>
Cc: jamal <hadi@cyberus.ca>,
Bernd Eckenfels <ecki-news2004-05@lina.inka.de>,
"David S. Miller" <davem@davemloft.net>,
netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: _High_ CPU usage while routing (mostly) small UDP packets
Date: Tue, 7 Dec 2004 11:21:32 +0100 [thread overview]
Message-ID: <20041207102132.GA28588@quickstop.soohrt.org> (raw)
In-Reply-To: <20041207040235.GA10501@soohrt.org>
Karsten Desler <kdesler@soohrt.org> wrote:
> * jamal wrote:
> > Beats me. Make sure it boots NAPI. Also if you can turn off ITR; intel
> > loves to turn on that silly feature.
>
> ITR was in fact activated. I think i've disabled it now
> (e1000.InterruptThrottleRate=0 in the kernel cmdline).
> And as I'm reading the e1000 code, there is no way to enable/disable
> NAPI without a recompile. So the fact that ethtool spat out -NAPI in
> the version string means that NAPI is actually used.
But looking and the int/s number, I'm not so sure anymore. Is there any
other way to find out?
# ethtool -i eth0|grep ^vers
version: 5.5.4-k2-NAPI
# ethtool -i eth1|grep ^vers
version: 5.5.4-k2-NAPI
CPU0 CPU1
169: 5 115554253 IO-APIC-level eth0
177: 78998347 5568 IO-APIC-level eth1
# sar -I 169 5 5
11:20:05 INTR intr/s
11:20:10 169 10401.40
11:20:15 169 10579.80
11:20:20 169 10965.20
11:20:25 169 10768.20
11:20:30 169 10460.60
Average: 169 10635.04
# sar -I 177 5 5
11:18:50 INTR intr/s
11:18:55 177 4769.74
11:19:00 177 4780.80
11:19:05 177 4669.74
11:19:10 177 4724.55
11:19:15 177 4748.50
Average: 177 4738.67
Cheers,
Karsten
next prev parent reply other threads:[~2004-12-07 10:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 20:53 _High_ CPU usage while routing (mostly) small UDP packets Karsten Desler
2004-12-06 21:48 ` David S. Miller
2004-12-06 22:41 ` Karsten Desler
2004-12-06 23:56 ` Con Kolivas
2004-12-07 0:18 ` Karsten Desler
[not found] ` <E1CbSf8-00047p-00@calista.eckenfels.6bone.ka-ip.net>
2004-12-07 0:20 ` Karsten Desler
2004-12-07 2:46 ` jamal
2004-12-07 2:54 ` Karsten Desler
2004-12-07 3:18 ` jamal
2004-12-07 3:24 ` Karsten Desler
2004-12-07 3:30 ` jamal
2004-12-07 4:02 ` Karsten Desler
2004-12-07 10:21 ` Karsten Desler [this message]
2004-12-07 12:34 ` jamal
2004-12-07 13:14 ` Karsten Desler
2004-12-07 10:47 ` P
2004-12-07 11:21 ` Karsten Desler
2004-12-07 12:38 ` Robert Olsson
2004-12-07 12:50 ` Karsten Desler
2004-12-07 13:04 ` jamal
2004-12-07 13:11 ` Karsten Desler
2004-12-07 13:39 ` P
2004-12-07 18:38 ` Karsten Desler
2004-12-08 5:39 ` Willy Tarreau
2004-12-08 13:08 ` Karsten Desler
2004-12-08 13:27 ` jamal
2004-12-07 21:10 ` Karsten Desler
2004-12-07 22:40 ` Robert Olsson
2004-12-08 22:06 ` Karsten Desler
2004-12-08 4:31 ` jamal
2004-12-08 13:26 ` Karsten Desler
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=20041207102132.GA28588@quickstop.soohrt.org \
--to=kdesler@soohrt.org \
--cc=davem@davemloft.net \
--cc=ecki-news2004-05@lina.inka.de \
--cc=hadi@cyberus.ca \
--cc=linux-kernel@vger.kernel.org \
--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).