From: "Nish Aravamudan" <nish.aravamudan@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Gautam H Thaker" <gthaker@atl.lmco.com>, linux-kernel@vger.kernel.org
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 13:06:52 -0800 [thread overview]
Message-ID: <29495f1d0602231306o55d759d5v9600b070a4b485e3@mail.gmail.com> (raw)
In-Reply-To: <20060223205851.GA24321@elte.hu>
On 2/23/06, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Gautam H Thaker <gthaker@atl.lmco.com> wrote:
>
> > ::::::::::::::
> > top: 2.6.15-rt15-smp.out # REAL_TIME KERNEL
> > ::::::::::::::
>
> > 2906 root -66 0 18624 2244 1480 S 41.4 0.1 27:11.21 nalive.p
> > 6 root -91 0 0 0 0 S 32.3 0.0 21:04.53 softirq-net-rx/
> > 1379 root -40 -5 0 0 0 S 14.5 0.0 9:54.76 IRQ 23
>
> One effect of the -rt kernel is that it shows IRQ load explicitly -
> while the stock kernel can 'hide' it because there interrupts run
> 'atomically', making it hard to measure the true system overhead. The
> -rt kernel will likely show more overhead, but i'd not expect this
> amount of overhead.
>
> To figure out the true overhead of both kernels, could you try the
> attached loop_print_thread.c code, and run it on: an idle non-rt kernel,
> and idle -rt kernel, a busy non-rt kernel and a busy -rt kernel, and
> send me the typical/average loops/sec value you are getting?
>
> Furthermore, there have been some tasklet related fixes in 2.6.15-rt17,
> which maybe could improve this workload. Maybe ...
Would it make more sense to compare 2.6.15 and 2.6.15-rt17, as opposed
to 2.6.12-1.1390_FC4 and 2.6.15-rt17? Seems like the closer the two
kernels are, the easier it will be to isolate the differences.
Thanks,
Nish
next prev parent reply other threads:[~2006-02-23 21:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 19:55 Gautam H Thaker
2006-02-23 20:15 ` Benjamin LaHaise
2006-02-23 20:58 ` Ingo Molnar
2006-02-23 21:06 ` Nish Aravamudan [this message]
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
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=29495f1d0602231306o55d759d5v9600b070a4b485e3@mail.gmail.com \
--to=nish.aravamudan@gmail.com \
--cc=gthaker@atl.lmco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®