From: Benjamin LaHaise <bcrl@kvack.org>
To: Gautam H Thaker <gthaker@atl.lmco.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>
Subject: Re: ~5x greater CPU load for a networked application when using 2.6.15-rt15-smp vs. 2.6.12-1.1390_FC4
Date: Thu, 23 Feb 2006 15:15:10 -0500 [thread overview]
Message-ID: <20060223201510.GA30329@kvack.org> (raw)
In-Reply-To: <43FE134C.6070600@atl.lmco.com>
On Thu, Feb 23, 2006 at 02:55:56PM -0500, Gautam H Thaker wrote:
> It has been documented before (and accepted) that this patch turns Linux into
> a RT kernel but considerably slows down the code paths, esp. thru the I/O
> subsystem. I want to provide some additional measurements and seek opinions
> of if it might ever be possible to improve on this situation.
32 bit kernel or 64 bit kernel? What about profiling the system with
oprofile?
-ben
--
"Ladies and gentlemen, I'm sorry to interrupt, but the police are here
and they've asked us to stop the party." Don't Email: <dont@kvack.org>.
next prev parent reply other threads:[~2006-02-23 20:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 19:55 ~5x greater CPU load for a networked application when using 2.6.15-rt15-smp vs. 2.6.12-1.1390_FC4 Gautam H Thaker
2006-02-23 20:15 ` Benjamin LaHaise [this message]
2006-02-23 20:58 ` Ingo Molnar
2006-02-23 21:06 ` Nish Aravamudan
2006-02-23 21:08 ` Ingo Molnar
2006-02-23 21:14 ` Nish Aravamudan
2006-02-23 22:07 ` Esben Nielsen
2006-02-24 8:03 ` Jan Engelhardt
2006-02-24 12:11 ` Andrew Morton
2006-02-24 20:06 ` Gautam H Thaker
2006-02-24 20:31 ` Andrew Morton
2006-02-24 20:44 ` Gautam H Thaker
2006-02-24 16:52 ` Theodore Ts'o
2006-02-24 19:25 ` Gautam H Thaker
2006-02-28 19:27 ` Matt Mackall
2006-02-28 22:19 ` Gautam H Thaker
-- strict thread matches above, loose matches on Subject: below --
2006-07-11 18:08 Jonathan Walsh
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=20060223201510.GA30329@kvack.org \
--to=bcrl@kvack.org \
--cc=gthaker@atl.lmco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.