All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Hannes Mayer <h.mayer@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] ... the rt-preempt patch once been in fusion
Date: Mon, 06 Feb 2006 00:11:26 +0100	[thread overview]
Message-ID: <43E6861E.3000400@domain.hid> (raw)
In-Reply-To: <43E668EF.4090306@domain.hid>

Hannes Mayer wrote:
> Hi all!
> 
> Well, subject says almost all.
> I remember there has been an effort to make a fusion/rt-preempt
> patch conglomerate back then.
> I'm just curious (as I've just been toying with the Molnar
> patch) - has that thing been dropped in xeno completely ?
> 

Clearly not, it is still on the project's agenda, but PREEMPT_RT has been too much 
of a moving target recently, not to speak of the vanilla 2.6 kernel itself. Even 
if Xeno's core has not changed in the same proportions, a large refactoring has 
taken place for 2.1 though.

Additionally, PREEMPT_RT's infrastructure has evolved a lot since Xeno was first 
ported over such kernel, and the way to interface both sub-systems likely needs to 
be re-thought. This combo cannot be done overnight, but I think that we are 
getting close to point where it would be possible to rework on this issue.

This work is likely going to start by a test campaign evaluating PREEMPT_RT's and 
Xeno's nucleus performances in a series of simple and relevant test cases over 
different ranges of platforms, so that we could measure up to which point (and 
under which condition) the real-time spectrum would be widened by using a 
combination of both.

-- 

Philippe.


  reply	other threads:[~2006-02-05 23:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-05 21:06 [Xenomai-core] ... the rt-preempt patch once been in fusion Hannes Mayer
2006-02-05 23:11 ` Philippe Gerum [this message]
2006-02-05 23:42   ` Hannes Mayer
2006-02-06  8:25     ` Philippe Gerum

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=43E6861E.3000400@domain.hid \
    --to=rpm@xenomai.org \
    --cc=h.mayer@domain.hid \
    --cc=xenomai@xenomai.org \
    /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.