From: Karim Yaghmour <karim@opersys.com>
To: "Bill Huey (hui)" <bhuey@lnxw.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Kristian Benoit <kbenoit@opersys.com>,
linux-kernel@vger.kernel.org, paulmck@us.ibm.com, andrea@suse.de,
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 I-PIPE: the numbers, part 2
Date: Wed, 22 Jun 2005 21:09:30 -0400 [thread overview]
Message-ID: <42BA0BCA.6020903@opersys.com> (raw)
In-Reply-To: <20050623005538.GA3348@nietzsche.lynx.com>
Bill Huey (hui) wrote:
> He's probably confusing you from the real FUDers. I don't see you
> as a FUDer.
Thanks, I appreciate the vote of confidence.
> He's just resentful fighting with you over attention from the same
> batch of strippers at last years OLS. :)
But I don't want to "fight" Ingo. There would just be no point
whatsoever with "fighting" with one the best developers Linux
has. I started my involvement in these recent threads with a
very clear statement that I was open to being shown wrong in
having exclusively championed the nanokernel approach in the
past. I set out to show myself wrong with these tests and
beside some vague expectations, I truely didn't know what I
was going to find. I certainly wouldn't have bet a hot-dog on
preempt_rt coming neck-to-neck with the ipipe on interrupt
latency ... So yes, in doing so some results I've found aren't
that nice. But, hell, I didn't invent those results. They are
there for anyone to repdroduce or contradict. I have no
monopoly over LMbench, PC hardware, the Linux kernel, or
anything else used to get those numbers.
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:[~2005-06-23 0:58 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 17:13 PREEMPT_RT vs I-PIPE: the numbers, part 2 Kristian Benoit
2005-06-20 18:31 ` Bill Huey
2005-06-22 16:00 ` Karim Yaghmour
2005-06-22 19:29 ` Bill Huey
2005-06-22 20:05 ` Ingo Molnar
2005-06-22 20:39 ` Karim Yaghmour
2005-06-22 22:04 ` Ingo Molnar
2005-06-22 23:03 ` Lee Revell
2005-06-22 23:52 ` Karim Yaghmour
2005-06-22 23:38 ` Karim Yaghmour
2005-06-22 23:57 ` Andrea Arcangeli
2005-06-23 0:05 ` Daniel Walker
2005-06-23 0:48 ` Karim Yaghmour
2005-06-23 0:06 ` Ingo Molnar
2005-06-23 0:47 ` Karim Yaghmour
2005-06-23 0:55 ` Bill Huey
2005-06-23 1:09 ` Karim Yaghmour [this message]
2005-06-23 1:15 ` Bill Huey
2005-06-23 1:47 ` Karim Yaghmour
2005-06-23 0:59 ` David Lang
2005-06-23 1:22 ` Karim Yaghmour
2005-06-23 1:42 ` David Lang
2005-06-23 2:09 ` Karim Yaghmour
2005-06-23 2:15 ` David Lang
2005-06-23 1:34 ` Ingo Molnar
2005-06-23 2:02 ` Karim Yaghmour
2005-06-23 3:57 ` Lee Revell
2005-06-23 4:13 ` Karim Yaghmour
2005-06-22 20:10 ` Karim Yaghmour
2005-06-22 20:15 ` Bill Huey
2005-06-21 1:55 ` Paul E. McKenney
2005-06-21 2:29 ` Karim Yaghmour
2005-06-22 1:19 ` Paul E. McKenney
2005-06-22 15:31 ` Karim Yaghmour
2005-06-22 15:27 ` Kristian Benoit
2005-06-22 16:27 ` Paul E. McKenney
2005-06-22 17:20 ` Kristian Benoit
2005-06-22 17:34 ` Ingo Molnar
2005-06-22 17:40 ` Ingo Molnar
2005-06-22 18:12 ` Karim Yaghmour
2005-06-22 18:14 ` Ingo Molnar
2005-06-22 19:04 ` Karim Yaghmour
2005-06-22 18:50 ` Paul E. McKenney
2005-06-22 19:04 ` Ingo Molnar
2005-06-22 20:17 ` Karim Yaghmour
2005-06-22 20:22 ` Ingo Molnar
2005-06-22 21:03 ` Karim Yaghmour
2005-06-22 21:10 ` Ingo Molnar
2005-06-22 21:32 ` Karim Yaghmour
2005-06-22 22:41 ` Ingo Molnar
2005-06-22 23:02 ` Karim Yaghmour
2005-06-22 21:20 ` Paul E. McKenney
2005-06-22 19:08 ` Karim Yaghmour
2005-06-23 14:48 ` Paulo Marques
2005-06-22 17:58 ` Karim Yaghmour
2005-06-22 18:47 ` Paul E. McKenney
2005-06-22 19:16 ` Karim Yaghmour
2005-06-22 21:23 ` Paul E. McKenney
2005-06-22 17:17 ` Lee Revell
2005-06-22 17:32 ` Karim Yaghmour
2005-06-29 7:43 ` PREEMPT_RT & threading IRQ 0 Ingo Molnar
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=42BA0BCA.6020903@opersys.com \
--to=karim@opersys.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=bhuey@lnxw.com \
--cc=bruce@andrew.cmu.edu \
--cc=dwalker@mvista.com \
--cc=hch@infradead.org \
--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 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.