All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Guvenc Gulce <gulceg@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] RT Task RPC over a POSIX/Native Queue
Date: Tue, 08 Sep 2009 19:17:44 +0200	[thread overview]
Message-ID: <4AA691B8.4090204@domain.hid> (raw)
In-Reply-To: <793108.19562.qm@domain.hid>

Guvenc Gulce wrote:
> Hi As far as I know an Xenomai RT Task can not call Linux API
> functions without leaving the Xenomai domain.
> 
> I was thinking about a generic library/framework which would allow an
> Xenomai RT Task call a Linux API function which would be then
> marshalled over a Posix/Native Queue to another Xenomai RT Task which
> then would do the dirty job of calling Linux functions. The responses
> and function return values from linux functions can be marshalled
> back to the original Xenomai RT-Task caller again over another
> Posix/Native Queue. In such a scenario the original caller RT Task
> would stay always in Xenomai domain.
> 
> I would like to hear whether such an approach sounds
> feasible/reasonable given the fact that currently Xenomai RT Tasks
> can not call Linux functions without leaving the Xenomai domain. Such
> a library/framework would be a solution to overcome that constraint.
> I would be glad to hear some opinions about this.

Leaving Xenomai domain is not bad per se. The reason why it is bad is
that when re-entering Linux domain, you may have to wait an unbounded
time for Linux to let your task run.

With your approach, the first RT task would not leave the Xenomai
domain, but it would wait for the second RT task to complete. And the
second RT task would risk to wait for the same unbounded time.

So, in short, you gain nothing.

-- 
                                          Gilles



  reply	other threads:[~2009-09-08 17:17 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 [this message]
     [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
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=4AA691B8.4090204@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=gulceg@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.