All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Chris Stone <chris.stone@optelian.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] a question about ADEOS
Date: Wed, 30 May 2012 23:40:36 +0200	[thread overview]
Message-ID: <4FC693D4.1090108@xenomai.org> (raw)
In-Reply-To: <623784B6C75D274389918D358E89E8BB0B7FE2DD@OPTELIAN5.optelian.local>

On 05/30/2012 07:32 PM, Chris Stone wrote:
> Rest assured there are many users of Adeos/Xenomai that believe it is
> a much more elegant/reliable/efficient/simple choice for real time in
> Linux. The linux scheduler is a mammoth beast that takes far too long
> to run. One of the finest advantages of Adeos/Xenomai is that you get
> to preempt the mammoth beast with a simple and fast real time
> scheduler. PREEMPT-RT is an interesting solution, but is not a
> particularly well thought out one. PREEMPT-RT is unstable and slow,
> which is why it STILL isn't fully accepted into the native kernel
> yet, after at least 8 years of trying to get it in. In another five
> years, PREEMPT_RT will make Xenomai better by reducing worst case
> latency when an application switches to secondary mode, but it will
> never replace Adeos/Xenomai.

Do not get me wrong, I have no issue with preempt_rt being the solution
chosen by the kernel community as the solution for real-time. I would
even tend to be a bit less extreme than you, calling room for
improvement the "mammoth beast" and the slow kernel.

As for the stability, the OSADL published some results:
https://www.osadl.org/Single-View.111+M59e3481cdfe.0.html

which show that the preempt_rt patched kernels are able to run for
sustained period of times under load without crashes, at least on the
tested platforms. This is not so different of the way we validate the
I-pipe patch.

I was merely trying to answer the question "why is not adeos integrated
to the linux kernel?".
-- 
                                                                Gilles.


  parent reply	other threads:[~2012-05-30 21:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30 14:35 [Xenomai] a question about ADEOS ali hagigat
2012-05-30 14:57 ` Chris Stone
2012-05-30 15:08 ` Philippe Gerum
2012-05-30 15:27   ` Gilles Chanteperdrix
2012-05-30 15:57     ` Lennart Sorensen
2012-05-30 16:53       ` Gilles Chanteperdrix
2012-05-30 17:57         ` Lennart Sorensen
2012-05-30 18:40           ` Gilles Chanteperdrix
2012-05-30 17:32       ` Chris Stone
2012-05-30 17:59         ` Lennart Sorensen
2012-05-30 21:40         ` Gilles Chanteperdrix [this message]
2012-05-31 15:10           ` Chris Stone
2012-06-05  6:26   ` ali hagigat
2012-06-05  7:10     ` Philippe Gerum
2012-06-05  8:06       ` [Xenomai] ftrace dietmar.schindler
2012-06-05  8:17         ` Philippe Gerum
2012-06-13  9:32           ` dietmar.schindler
2012-06-13  9:49             ` Wolfgang Grandegger
2012-06-13 10:00             ` Wolfgang Grandegger
2012-06-05  7:20     ` [Xenomai] a question about ADEOS 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=4FC693D4.1090108@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=chris.stone@optelian.com \
    --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.