From: Ingo Molnar <mingo@elte.hu>
To: Mark_H_Johnson@raytheon.com
Cc: Amit Shah <amit.shah@codito.com>,
Karsten Wiese <annabellesgarden@yahoo.de>,
Bill Huey <bhuey@lnxw.com>, Adam Heath <doogie@debian.org>,
emann@mrv.com, Gunther Persoons <gunther_persoons@spymac.com>,
"K.R. Foley" <kr@cybsft.com>,
linux-kernel@vger.kernel.org,
Florian Schmidt <mista.tapas@gmx.net>,
Fernando Pablo Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
Lee Revell <rlrevell@joe-job.com>,
Rui Nuno Capela <rncbc@rncbc.org>,
Shane Shrybman <shrybman@aei.ca>,
Esben Nielsen <simlo@phys.au.dk>,
Thomas Gleixner <tglx@linutronix.de>,
Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
Subject: Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm3-V0.7.32-15
Date: Mon, 13 Dec 2004 23:33:57 +0100 [thread overview]
Message-ID: <20041213223357.GA6944@elte.hu> (raw)
In-Reply-To: <OFA329B47C.3EDA9672-ON86256F69.005967F1@raytheon.com>
* Mark_H_Johnson@raytheon.com <Mark_H_Johnson@raytheon.com> wrote:
> A comparison of PREEMPT_RT (no tracing) to PREEMPT_DESKTOP
> (with tracing) to help answer previous requests.
>
> Comparison of .32-20RT and .32-18PK results
> 20RT has PREEMPT_RT (all tracing disabled)
> 18PK has PREEMPT_DESKTOP and no threaded IRQ's (tracing enabled)
> 2.4 has lowlat + preempt patches applied
>
> within 100 usec
> CPU loop (%) Elapsed Time (sec) 2.4
> Test RT PK RT PK | CPU Elapsed
> X 99.87 100.00& 65 * 64+ | 97.20 70
> top 99.35 100.00& 31 * 31+ | 97.48 29
> neto 96.94 100.00& 113 * 184+ | 96.23 36
> neti 97.05 100.00& 119 * 170+ | 95.86 41
interesting - the PK kernel with tracing enabled performs better than
the PK kernel with tracing disabled? Sounds counter-intuitive.
Ingo
next prev parent reply other threads:[~2004-12-13 22:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 17:05 [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm3-V0.7.32-15 Mark_H_Johnson
2004-12-13 22:33 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-13 23:14 Mark_H_Johnson
2004-12-13 20:02 Mark_H_Johnson
2004-12-13 22:39 ` Ingo Molnar
2004-12-10 22:06 Mark_H_Johnson
2004-12-10 22:24 ` Ingo Molnar
2004-12-10 21:58 Mark_H_Johnson
2004-12-10 21:54 Mark_H_Johnson
2004-12-10 22:14 ` Ingo Molnar
2004-12-10 21:31 Mark_H_Johnson
2004-12-10 21:54 ` Ingo Molnar
2004-12-10 21:06 Mark_H_Johnson
2004-12-10 21:40 ` Ingo Molnar
2004-12-10 20:03 Mark_H_Johnson
2004-12-10 17:49 Mark_H_Johnson
2004-12-10 21:09 ` Ingo Molnar
2004-12-10 21:12 ` Ingo Molnar
2004-12-10 21:24 ` Ingo Molnar
2004-12-13 0:16 ` Fernando Lopez-Lezcano
2004-12-13 6:47 ` Ingo Molnar
2004-12-14 0:46 ` Fernando Lopez-Lezcano
2004-12-14 4:42 ` K.R. Foley
2004-12-14 8:47 ` Rui Nuno Capela
2004-12-14 11:35 ` Ingo Molnar
2004-12-09 21:58 [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm3-V0.7.32-6 Mark_H_Johnson
2004-12-09 22:55 ` Ingo Molnar
2004-12-10 10:53 ` [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm3-V0.7.32-15 Ingo Molnar
2004-12-10 14:59 ` Gene Heskett
2004-12-10 15:59 ` Gene Heskett
2004-12-10 19:09 ` Lee Revell
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=20041213223357.GA6944@elte.hu \
--to=mingo@elte.hu \
--cc=Mark_H_Johnson@raytheon.com \
--cc=amit.shah@codito.com \
--cc=annabellesgarden@yahoo.de \
--cc=bhuey@lnxw.com \
--cc=doogie@debian.org \
--cc=emann@mrv.com \
--cc=gunther_persoons@spymac.com \
--cc=kr@cybsft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mista.tapas@gmx.net \
--cc=nando@ccrma.Stanford.EDU \
--cc=rlrevell@joe-job.com \
--cc=rncbc@rncbc.org \
--cc=shrybman@aei.ca \
--cc=simlo@phys.au.dk \
--cc=tglx@linutronix.de \
--cc=xschmi00@stud.feec.vutbr.cz \
/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.