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: Wed, 9 Sep 2009 04:34:57 -0700 (PDT)	[thread overview]
Message-ID: <127667.68551.qm@domain.hid> (raw)
In-Reply-To: <4AA77F8D.3090709@domain.hid>

Gilles Thanks.. I will look into the nomac possibility in rtnet..

And Jan.. your comments here brings me back to my original 
post in this topic where I said:


>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.

and when we are at it why not to make a generic thing from 
this low prio proxy RT Task <-> RT Task communicate with each other with IPC 
and low prio RT Task does the dirty job of calling Linux API idea.. such a 
thing may be needed for other Linux APIs and not only for the network part..

I will try to develop this idea and prepare some test code maybe the 
community is also interested to have it in Xenomai tree.. more 
comments are also welcome..

Thanks & Regards

Guvenc 




----- Original Message ----
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Guvenc Gulce <gulceg@domain.hid>
Cc: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>; xenomai@xenomai.org
Sent: Wednesday, September 9, 2009 12:12:29 PM
Subject: Re: RT Task RPC over a POSIX/Native Queue

Guvenc Gulce wrote:
> rt_net is nice but then all network participants have to use rt_net otherwise 
> the realtime communication is not guaranteed on the wire.. in some cases 
> the real-timeliness on the wire may not be needed but the determinism 
> of the rt-task may still be an issue..
> 
> I think it is a great flexibility to give an rt task the chance to communicate 
> with non rt_net clients and servers in the network without worrying about 
> losing its determinism. 

To achieve this, you just need to set up a low-prio Xenomai server task
that accepts to-be-transmitted data from the RT task sends it out,
collects replies and dispatches them back to the sender. You may use
queues or shared memory as IPC mechanisms for the RT<->proxy
communication. They just have to be Xenomai provided. The effect will be
that the proxy is switching back and forth between primary (Xenomai) and
secondary (Linux) mode, but your RT task will stay in primary mode.

As you do not care about determinism of the network communication, you
also do not need RTnet. It would only introduce the risk that non-RT
network participant overload your box. And this load would show up in
the RT domain because RTnet would have to handle it.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux



      



  reply	other threads:[~2009-09-09 11:34 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 [this message]
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=127667.68551.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.