From: "M. Koehrer" <mathias_koehrer@arcor.de>
To: pradysam@gmail.com, mathias_koehrer@arcor.de
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Re: Looking for a real time IPC to be used with select
Date: Mon, 19 Apr 2010 08:31:59 +0200 (CEST) [thread overview]
Message-ID: <29168504.1271658719738.JavaMail.ngmail@webmail18.arcor-online.net> (raw)
In-Reply-To: <r2r6d09081c1004170742ia4f0b1c5vfa51005c934617fd@mail.gmail.com>
Hi Pradyumna,
thanks for this approach!
> > My question is now: What kind of IPC is preferred here?
> > The only IPC I see is a local socket communication, however
> > this looks like a huge overhead for triggering...
>
> POSIX message queues in the kernel work fine for me. I had one problem
> with the accuracy of the timeouts in mq_timedreceieve and mq_timedsend
> which has been now fixed and is available as part of the latest -rt
> patch.
I read again the man page "mq_overview" and found that the message queue descriptor
could be used with select/poll! That's a point I have not realized so far.
Thus, this allows to use this as another promising approach!
BTW: When I use select() for the timeouts and mq_receive (instead of mq_timedreceive),
I hope to find no accuaracy issue...
I think select() is using high accuracy with the timeout in -rt.
Regards
Mathias
--
Mathias Koehrer
mathias_koehrer@arcor.de
Traumziele - von Beschreibung bis Buchung jetzt kompakt auf den Reise-Seiten von Arcor.de! http://www.arcor.de/rd/footer.reise
prev parent reply other threads:[~2010-04-19 6:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 14:12 Looking for a real time IPC to be used with select M. Koehrer
2010-04-16 20:30 ` Leyendecker, Robert
2010-04-17 7:55 ` Armin Steinhoff
2010-04-17 14:42 ` Pradyumna Sampath
2010-04-18 4:43 ` Sujit K M
2010-04-19 6:24 ` M. Koehrer
2010-04-19 6:31 ` M. Koehrer [this message]
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=29168504.1271658719738.JavaMail.ngmail@webmail18.arcor-online.net \
--to=mathias_koehrer@arcor.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=pradysam@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).