From: Andrea Arcangeli <andrea@suse.de>
To: Karim Yaghmour <karim@opersys.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Kristian Benoit <kbenoit@opersys.com>,
linux-kernel@vger.kernel.org, paulmck@us.ibm.com, bhuey@lnxw.com,
tglx@linutronix.de, pmarques@grupopie.com, bruce@andrew.cmu.edu,
nickpiggin@yahoo.com.au, ak@muc.de, sdietrich@mvista.com,
dwalker@mvista.com, hch@infradead.org, akpm@osdl.org,
rpm@xenomai.org
Subject: Re: PREEMPT_RT vs ADEOS: the numbers, part 1
Date: Mon, 13 Jun 2005 00:20:11 +0200 [thread overview]
Message-ID: <20050612222011.GG5796@g5.random> (raw)
In-Reply-To: <42AB662B.4010104@opersys.com>
On Sat, Jun 11, 2005 at 06:31:07PM -0400, Karim Yaghmour wrote:
> The logger used two TSC values. One prior to shooting the interrupt to the
> target, and one when receiving the response. Responding to an interrupt
Real life RT apps would run the second rdtsc in user space and not
kernel space, right?
And thanks for your benchmarking efforts!
next prev parent reply other threads:[~2005-06-12 22:20 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 4:36 PREEMPT_RT vs ADEOS: the numbers, part 1 Kristian Benoit
2005-06-11 6:14 ` Nick Piggin
2005-06-11 9:15 ` Sven-Thorsten Dietrich
2005-06-11 14:15 ` Kristian Benoit
2005-06-12 15:48 ` Philippe Gerum
2005-06-11 14:39 ` Karim Yaghmour
2005-06-11 22:14 ` Philippe Gerum
2005-06-11 13:57 ` Kristian Benoit
2005-06-11 14:28 ` Zwane Mwaikambo
2005-06-11 7:08 ` Ingo Molnar
2005-06-11 7:44 ` Nick Piggin
2005-06-11 9:27 ` Sven-Thorsten Dietrich
2005-06-12 15:31 ` Philippe Gerum
2005-06-11 14:28 ` Kristian Benoit
2005-06-11 10:37 ` Ingo Molnar
2005-06-11 14:23 ` Kristian Benoit
2005-06-11 14:56 ` Ingo Molnar
2005-06-11 14:31 ` Karim Yaghmour
2005-06-11 14:52 ` Ingo Molnar
2005-06-11 14:52 ` Karim Yaghmour
2005-06-11 17:40 ` Karim Yaghmour
2005-06-11 18:15 ` Ingo Molnar
2005-06-11 18:34 ` Ingo Molnar
2005-06-11 22:27 ` Karim Yaghmour
2005-06-12 10:47 ` James R Bruce
2005-06-12 14:54 ` Ingo Molnar
2005-06-13 2:39 ` Kristian Benoit
2005-06-11 19:14 ` Ingo Molnar
2005-06-11 22:31 ` Karim Yaghmour
2005-06-12 6:11 ` Ingo Molnar
2005-06-12 15:26 ` Daniel Walker
2005-06-12 19:29 ` Karim Yaghmour
2005-06-12 20:59 ` Ingo Molnar
2005-06-13 0:45 ` Andrea Arcangeli
2005-06-13 1:20 ` Karim Yaghmour
2005-06-13 5:47 ` Ingo Molnar
2005-06-12 22:20 ` Andrea Arcangeli [this message]
2005-06-12 23:03 ` Sven-Thorsten Dietrich
2005-06-13 0:53 ` randy_dunlap
2005-06-13 1:12 ` Karim Yaghmour
2005-06-13 6:51 ` Sven-Thorsten Dietrich
2005-06-13 15:00 ` Ingo Molnar
2005-06-13 15:12 ` Kristian Benoit
2005-06-11 19:27 ` Ingo Molnar
2005-06-12 4:21 ` Karim Yaghmour
2005-06-11 20:14 ` Paul E. McKenney
2005-06-11 22:33 ` Karim Yaghmour
2005-06-12 20:36 ` Paul E. McKenney
2005-06-12 11:11 ` James R Bruce
2005-06-12 19:49 ` Karim Yaghmour
2005-06-13 2:32 ` Kristian Benoit
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=20050612222011.GG5796@g5.random \
--to=andrea@suse.de \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=bhuey@lnxw.com \
--cc=bruce@andrew.cmu.edu \
--cc=dwalker@mvista.com \
--cc=hch@infradead.org \
--cc=karim@opersys.com \
--cc=kbenoit@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=paulmck@us.ibm.com \
--cc=pmarques@grupopie.com \
--cc=rpm@xenomai.org \
--cc=sdietrich@mvista.com \
--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