From: Michal Soltys <soltys@ziu.info>
To: netdev@vger.kernel.org
Subject: r8169 (+others ?) and note_interrupt performance hit on 2.6.30.x
Date: Sun, 26 Jul 2009 02:31:10 +0200 [thread overview]
Message-ID: <4A6BA3CE.9000607@ziu.info> (raw)
I've noticed, that on 2.6.30 kernels I took serious performance
hit compared to e.g. 2.6.28.10 (didn't check 2.6.29 ones).
Generally, with trivial nc -u other_host </dev/zero
- so ~ 1KB packets and 1gbit speed I went from:
01:30:25 AM CPU %usr %nice %sys %iowait %irq %soft %steal %guest %idle
01:30:26 AM all 0.91 0.00 8.68 0.00 2.28 7.31 0.00 0.00 80.82
01:30:26 AM 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 100.00
01:30:26 AM 1 1.68 0.00 15.13 0.00 5.04 13.45 0.00 0.00 64.71
running at full 1gbit speed with ease, to:
01:35:26 AM CPU %usr %nice %sys %iowait %irq %soft %steal %guest %idle
01:35:27 AM all 0.50 0.00 12.56 0.00 24.12 12.56 0.00 0.00 50.25
01:35:27 AM 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 100.00
01:35:27 AM 1 2.00 0.00 25.00 0.00 48.00 25.00 0.00 0.00 0.00
struggling at ~90MB/s (standard pfifo_fast)
Both netcat and interface interrupt were pinned at the same (2nd) core.
I did some quick oprofile, and noticed one new call -
note_interrupt - which wasn't present in the earlier kernel,
taking majority of the cpu time, relatively to the rest, e.g.:
samples cum. samples % cum. % symbol name
90984 90984 42.8695 42.8695 note_interrupt
The hardware is regular 32bit x86:
GA-MA74GM-S2H
AMD 4850e (2.5ghz)
onboard r8169
Both kernels with identical configuration, and tests done on idle machine.
next reply other threads:[~2009-07-26 0:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-26 0:31 Michal Soltys [this message]
2009-07-26 9:18 ` r8169 (+others ?) and note_interrupt performance hit on 2.6.30.x Francois Romieu
2009-07-26 10:50 ` Michal Soltys
2009-07-26 18:43 ` Michal Soltys
2009-07-27 21:52 ` Jarek Poplawski
2009-08-05 18:54 ` Michal Soltys
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=4A6BA3CE.9000607@ziu.info \
--to=soltys@ziu.info \
--cc=netdev@vger.kernel.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).