All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guvenc Gulce <gulceg@domain.hid>
To: xenomai@xenomai.org
Subject: Re: [Xenomai-help] RT Task RPC over a POSIX/Native Queue
Date: Tue, 8 Sep 2009 15:41:56 -0700 (PDT)	[thread overview]
Message-ID: <982599.63991.qm@domain.hid> (raw)
In-Reply-To: <4AA6D85C.8040707@domain.hid>

Guvenc Gulce wrote:

>>> 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.
>> 
>> Exactly and that would disturb the real-timeliness of the rt task.
>> 
>>> 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.
>> 
>> Why should the first RT Task wait for the second RT Task when 
>> the second RT Task has lower priority than the first one ? If Xenomai 
>> scheduler works as expected then the first rt task should be 
>> able to continue to run after writing into Posix Queue (marshalled Linux 
>> call) and collect the results of the called linux function when 
>> the second rt task gets them and marshalls them back to a second 
>> feedback Queue which can be read by the first RT Task when 
>> it is appropriate for it. (Feedback Queue needs to be polled by the 
>> first RT Task as there is no async communication possibility in 
>> Userspace Realtime Environment) 

>> 
>> The main advantage here is that the original RT Task never loses his 
>> determinism as it might be doing some other jobs other than waiting 
>> for the answers from the called linux functions.  
>> 
>>> So, in short, you gain nothing.
>> I think the gain is that the original rt task stays deterministic and is still able 
>> to call the linux functions and can continue to do his job which needs 
>> determinism and may poll the feedback Queue some time later and 
>> get the results of the called linux function. 
>> Such a thing is impossible to do with the current Xenomai API, 

>Yes, you could do that, though, I do not see any real-world application
>where this would make sense. I mean, if you call a function you
>generally want to get the result immediately. What application do you
>have in mind?

Opps.. I didnt realize that I was replying to you and not to the list.. 

A typical application would be for example to offer a rt task the 
possibility of network communication without disturbing its determinism. 
If you send a data over the network, you dont necessarily expect 
the reply immediately or write to the file system again without 
disturbing the determinism. 

Regards,

Guvenc


      



  parent reply	other threads:[~2009-09-08 22:41 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 [this message]
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=982599.63991.qm@domain.hid \
    --to=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.