From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Peter Soetens <peter@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Native API rt_pipe_monitor() call can not be called from an RT Task in linux userspace ?
Date: Wed, 17 Jun 2009 12:30:46 +0200 [thread overview]
Message-ID: <4A38C5D6.1050300@domain.hid> (raw)
In-Reply-To: <634c78ce0906170240w1ade29b0p904c3468af0866c@domain.hid>
Peter Soetens wrote:
> On Wed, Jun 17, 2009 at 10:09, Philippe Gerum<rpm@xenomai.org> wrote:
>> As you have probably understood already, building a full real-time to
>> real-time data path using pipes is not possible; this said, this is not
>> the purpose of this API anyway, which has been designed for real-time to
>> non-RT communication.
>
> I was hoping to use rt_pipe + select in real-time context to implement
> a data receiving server for real-time inter-process communication. Is
> this possible ?
> What would happen if the real-time clients open the pipes as rt_pipes
> and start sending
> data in ? What's the alternative to listen in real-time to many
> connections from
> a single thread ?
Note that posix message queues already work for inter-process
communications, with support for select. Depending on your needs, this
may be sufficient: you will need Xenomai threads on both sides, but the
non real-time one may use the SCHED_OTHER policy.
I was thinking, maybe we could map the xnpipe to a special flag in mq_open ?
--
Gilles
next prev parent reply other threads:[~2009-06-17 10:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 22:23 [Xenomai-help] Native API rt_pipe_monitor() call can not be called from an RT Task in linux userspace ? Guvenc Gulce
2009-06-17 8:09 ` Philippe Gerum
2009-06-17 8:16 ` Gilles Chanteperdrix
2009-06-17 9:40 ` Peter Soetens
2009-06-17 9:50 ` Gilles Chanteperdrix
2009-06-17 10:30 ` Gilles Chanteperdrix [this message]
2009-06-17 12:13 ` Peter Soetens
2009-06-17 12:25 ` Gilles Chanteperdrix
2009-06-17 13:16 ` Peter Soetens
2009-06-17 22:41 ` Philippe Gerum
2009-06-18 17:20 ` Guvenc Gulce
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=4A38C5D6.1050300@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=peter@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.