mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: MA QING A <Qing.a.Ma@alcatel-sbell.com.cn>
Cc: Kasper Sandberg <lkml@metanurb.dk>,
	LKML <linux-kernel@vger.kernel.org>,
	RT <linux-rt-users@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: RE: 2.6.25.4-rt2
Date: Tue, 20 May 2008 00:37:02 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0805200030120.9319@gandalf.stny.rr.com> (raw)
In-Reply-To: <630E9048ECEBBB4798CE33255209FE730648317D@CNSHGSMBS02.ad4.ad.alcatel.com>




On Tue, 20 May 2008, MA QING A wrote:

> Forgive me to ask a stupid question.
> Why using the 24 mainline kernel, the time is less than using the
> rt-patched kernel?
>

The test I used is a performance test, not a latency test. An RTOS
(Real-time Operating System) will sacrifice performance to achieve
determinism (low latencies). Several key features to an RT system usually
come with a performance cost.

A non RT system will perform 99% of the time faster than an RTOS. But all
it takes is that one time to miss a deadline to make an RT system crash.
An RTOS may be slightly slower, but it will not have those outliers that a
normal desktop system would have.

So getting back to your question.  Hackbench runs a bunch of stuff and
times how long it took to do so. It stresses the system quite a bit. The
lower the number the better. Given that hackbench is not checking for
latency, but only shear perforance, it is expected that hackbench will run
better on a non RT system.

Now, a test like cyclictest that measures latencies will show the benefits
of realtime.  The kernel with the RT patch can measure 65 microsecond
latencies for response times even while running hackbench. The vanilla
kernel would measure a few milliseconds response times running the same
test.

-- Steve


  reply	other threads:[~2008-05-20  4:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19 22:43 2.6.25.4-rt2 Steven Rostedt
2008-05-19 23:19 ` 2.6.25.4-rt2 Kasper Sandberg
2008-05-19 23:44   ` 2.6.25.4-rt2 Steven Rostedt
2008-05-19 23:43     ` 2.6.25.4-rt2 Kasper Sandberg
2008-05-20  0:44     ` 2.6.25.4-rt2 MA QING A
2008-05-20  4:37       ` Steven Rostedt [this message]
2008-05-20  4:59         ` 2.6.25.4-rt2 MA QING A
2008-05-20 13:54           ` 2.6.25.4-rt2 Steven Rostedt
2008-05-20  0:19 ` 2.6.25.4-rt2 Kasper Sandberg
2008-05-20  0:48   ` 2.6.25.4-rt2 Steven Rostedt
2008-05-20  0:49     ` 2.6.25.4-rt2 Kasper Sandberg
2008-05-20  1:21       ` 2.6.25.4-rt2 Steven Rostedt
2008-05-20  0:49   ` 2.6.25.4-rt2 Steven Rostedt

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=Pine.LNX.4.58.0805200030120.9319@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=Qing.a.Ma@alcatel-sbell.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=lkml@metanurb.dk \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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®