From: Stephen Hemminger <shemminger@vyatta.com>
To: linux-rt-users@vger.kernel.org
Cc: netdev@vger.kernel.org
Subject: Network performance forwarding tests on RT
Date: Wed, 5 Nov 2008 11:52:05 -0800 [thread overview]
Message-ID: <20081105115205.14c5282f@s6510> (raw)
As an experiment, I rebuilt a version of Vyatta using 2.6.26-rt11 kernel.
This required some fixes to unionfs and aufs which I'll send to anyone who wants.
The performance of the RT PREEMPT kernel is worse than non-PREEMPT kernel.
Running RFC2544, frame loss test we the loss rate is worse on RT than non RT.
Ideally, there would be no loss, but on this platform, the best we have
seen is 70% loss at 64 bytes.
Size 2.6.26 2.6.26-rt11
64 80.5% 99%
128 67 99
256 43 92
512 0 54
1024 0 3
1280 0 0
1518 0 0
More importantly, with RT PREEMPT, the driver gets stuck and times out
under heavy load (see 99% loss above). It appears the change to network
scheduling related to NAPI doesn't work well under load.
I wouldn't recommend RT PREEMPT for heavy network loads.
Hardware: Celeron 430 @ 1.80GHz Intel dual-port 82546GB NIC
Config:
CONFIG_NR_CPUS=8
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT_DESKTOP is not set
CONFIG_PREEMPT_RT=y
CONFIG_PREEMPT=y
CONFIG_PREEMPT_SOFTIRQS=y
CONFIG_PREEMPT_HARDIRQS=y
CONFIG_PREEMPT_RCU=y
CONFIG_PREEMPT_RCU_BOOST=y
next reply other threads:[~2008-11-05 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 19:52 Stephen Hemminger [this message]
2008-11-07 0:50 ` Network performance forwarding tests on RT Clark Williams
[not found] ` <ccb913ac0811062303r7f94f8a8lfe48336d6dafb9f6@mail.gmail.com>
2008-11-07 16:52 ` Stephen Hemminger
2008-11-07 21:22 ` Sven-Thorsten Dietrich
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=20081105115205.14c5282f@s6510 \
--to=shemminger@vyatta.com \
--cc=linux-rt-users@vger.kernel.org \
--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).