All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Alphan Ulusoy <alphan@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] RT Task RPC over a POSIX/Native Queue
Date: Tue, 08 Sep 2009 21:24:48 +0200	[thread overview]
Message-ID: <4AA6AF80.5090902@domain.hid> (raw)
In-Reply-To: <89DE9B44-67FD-4DFE-BFE6-7445851AABCD@su.sabanciuniv.edu>

Alphan Ulusoy wrote:
> You can always use the Xenomai's _wonderful_ pipe functionality (and  
> other task communication services as well) to communicate data back  
> and forth between RT (Xenomai user -or- kernel space tasks) and non-RT  
> (dedicated linux executables) tasks. This also ensures that your RT  
> and non-RT domains are clearly separated by design, which is a good  
> thing IMHO.

Waiting for the non real-time task to post an answer through rt-pipes is
as dangerous for the real-time task determinism as with message queues
of any kind.

Besides, a task with low priority which oscillates between first and
secondary modes does not threaten a primary mode only task determinism
any more than a non real-time tasks. However, it can communicates with
the primary mode only task with a lot more IPCs and synchronization
mechanisms.

And there is no difference in design between an application separated
between real-time and non real-time tasks on the one hand, and an
application separated between real-time and oscillating tasks on the
other hand. The real gain in design happens when you can split driver
code from application code.

-- 
					    Gilles.


  reply	other threads:[~2009-09-08 19:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-08 17:10 [Xenomai-help] RT Task RPC over a POSIX/Native Queue Guvenc Gulce
2009-09-08 17:17 ` Gilles Chanteperdrix
     [not found]   ` <394564.56258.qm@domain.hid>
     [not found]     ` <4AA6D85C.8040707@domain.hid>
2009-09-08 22:41       ` Guvenc Gulce
2009-09-08 22:44         ` Gilles Chanteperdrix
2009-09-08 22:53           ` Guvenc Gulce
2009-09-08 23:02             ` Stuart O Anderson
2009-09-09  8:36               ` Philippe Gerum
2009-09-09  8:24             ` Gilles Chanteperdrix
2009-09-09  9:26               ` Guvenc Gulce
2009-09-09  9:39                 ` Gilles Chanteperdrix
2009-09-09 10:12             ` Jan Kiszka
2009-09-09 11:34               ` Guvenc Gulce
2009-09-09 12:03               ` Gilles Chanteperdrix
2009-09-09 12:07                 ` Jan Kiszka
2009-09-09 12:13                   ` Gilles Chanteperdrix
2009-09-08 17:23 ` Alphan Ulusoy
2009-09-08 19:24   ` Gilles Chanteperdrix [this message]
2009-09-08 19:42     ` Alphan Ulusoy

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=4AA6AF80.5090902@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=alphan@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.