From: Ingo Molnar <mingo@elte.hu>
To: Dave Sperry <dave_sperry@ieee.org>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Poor UDP performance using 2.6.21-rc5-rt5
Date: Mon, 2 Apr 2007 11:37:40 +0200 [thread overview]
Message-ID: <20070402093740.GA10091@elte.hu> (raw)
In-Reply-To: <4610BC15.5030800@ieee.org>
* Dave Sperry <dave_sperry@ieee.org> wrote:
> I checked the clock source and in both the vanilla and rt cases and
> they were both acpi_pm
ok, thanks for double-checking that.
> Here's the oprofile for my vanilla case:
i tried your workload and i think i managed to optimize it some more: i
have uploaded the -rt8 kernel with these improvements included - could
you try it? Is there any measurable improvement relative to -rt5?
one more thing to improve netperf performance is to do this before
running it:
chrt -f -p 50 $$
this will put netperf on the same priority level as the net hardirq and
the net softirq (which both default to SCHED_FIFO:50), and should result
in a (much) reduced context-switch rate.
Or, if networking is not latency-critical, then you could move the net
hardirq and softirq threads to SCHED_BATCH, and run netperf under
SCHED_BATCH as well, using:
chrt -b -p 0 $$
and figuring out the active softirq hardirq thread PIDs and "chrt -b"
-ing them too.
Ingo
next prev parent reply other threads:[~2007-04-02 9:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 19:15 Poor UDP performance using 2.6.21-rc5-rt5 Dave Sperry
2007-04-01 20:07 ` Nivedita Singhvi
2007-04-01 22:00 ` Dave Sperry
2007-04-02 5:55 ` Ingo Molnar
2007-04-02 6:30 ` Ingo Molnar
2007-04-02 7:21 ` Ingo Molnar
2007-04-02 8:17 ` Dave Sperry
2007-04-02 9:37 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-02 14:09 dave_sperry@ieee.org
2007-04-02 14:23 ` Ingo Molnar
2007-04-02 17:17 dave_sperry@ieee.org
2007-04-02 17:50 dave_sperry@ieee.org
2007-04-02 19:04 ` Ingo Molnar
2007-04-03 0:09 ` David Sperry
2007-04-03 6:43 ` Ingo Molnar
2007-04-03 8:51 ` Ingo Molnar
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=20070402093740.GA10091@elte.hu \
--to=mingo@elte.hu \
--cc=dave_sperry@ieee.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@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