public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kristian Benoit <kbenoit@opersys.com>
To: Sven-Thorsten Dietrich <sdietrich@mvista.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	linux-kernel@vger.kernel.org, paulmck@us.ibm.com, bhuey@lnxw.com,
	andrea@suse.de, tglx@linutronix.de,
	Karim Yaghmour <karim@opersys.com>,
	mingo@elte.hu, pmarques@grupopie.com, bruce@andrew.cmu.edu,
	ak@muc.de, dwalker@mvista.com, hch@infradead.org, akpm@osdl.org,
	rpm@xenomai.org
Subject: Re: PREEMPT_RT vs ADEOS: the numbers, part 1
Date: Sat, 11 Jun 2005 10:15:55 -0400	[thread overview]
Message-ID: <1118499356.5786.16.camel@localhost> (raw)
In-Reply-To: <1118481315.9519.39.camel@sdietrich-xp.vilm.net>

On Sat, 2005-06-11 at 02:15 -0700, Sven-Thorsten Dietrich wrote:
> Its a good start, and its excellent that its being looked at. Thank
> you
> guys very much for taking the time to compare these 2 very different
> systems. 

Youre welcome !

> I think the comparison should absolutely compare identical community
> kernels. The comparison between two different release candidates is
> questionable. rc2 to rc4 doesn't seem like much, after all, how much
> code could go into a release candidate. (diff | wc -l) 

I agree with that, but as the results show, there does'nt seems to be
much difference impact the numbers in the tested field.

> Also, I question testing -rc code in the first place, except for
> regression purposes. 

I tested the -rc code in orther to be able to compare the patched
kernels against theird own source.

> How does that effort compare for porting ADEOS code? If several weeks
> of
> work are invested in a comparison of rc2 to rc4, how much additional
> work is needed to bring Adeos up to the base for the current RT
> kernel?

Philippe, I think that question is youre !

Kristian


  reply	other threads:[~2005-06-11 14:18 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 [this message]
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
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=1118499356.5786.16.camel@localhost \
    --to=kbenoit@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=karim@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