From: Karim Yaghmour <karim@opersys.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Restricted hard realtime
Date: Thu, 28 Oct 2004 07:59:20 -0400 [thread overview]
Message-ID: <4180DF18.5060808@opersys.com> (raw)
In-Reply-To: <20041027081044.GA14451@elte.hu>
Ingo Molnar wrote:
> with -RT-V0.3 i get lower than 20 usec _maximum_ latencies during
> './hackbench 20'. (the average latency is 1 usec) So while i'm not yet
> in the sub-femtosecond category, things are looking pretty good in
> PREEMPT_REALTIME land :)
Just curious: what's the setup here? (CPU speed, peripherals, distro,
applications being run to load the system, etc.) You may have described
this elsewhere on LKML and I may have missed it (sorry, I just can't
read everything that comes through).
I'm assuming that the timings are measured using the tracing
functionality currently in the patches.
Thanks,
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546
next prev parent reply other threads:[~2004-10-28 12:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 19:47 Paul E. McKenney
2004-10-23 20:17 ` Ingo Molnar
2004-10-23 20:29 ` Paul E. McKenney
2004-10-24 18:18 ` Paul E. McKenney
2004-10-25 12:26 ` Dimitri Sivanich
2004-10-23 20:22 ` Thomas Gleixner
2004-10-23 21:24 ` Paul E. McKenney
2004-10-23 22:06 ` Jon Masters
2004-10-24 15:32 ` Paul E. McKenney
2004-10-24 21:08 ` Jon Masters
2004-10-24 21:23 ` Ingo Molnar
2004-10-24 21:49 ` Jon Masters
2004-10-24 21:52 ` Paul E. McKenney
2004-10-27 3:16 ` Karim Yaghmour
2004-10-27 4:29 ` Andrew Morton
2004-10-27 8:10 ` Ingo Molnar
2004-10-28 11:59 ` Karim Yaghmour [this message]
2004-10-28 13:16 ` Ingo Molnar
2004-10-28 11:54 ` Karim Yaghmour
2004-10-28 13:04 ` john cooper
2004-10-27 22:35 ` Bill Huey
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=4180DF18.5060808@opersys.com \
--to=karim@opersys.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
Powered by JetHome