linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pradyumna Sampath <pradysam@gmail.com>
To: "M. Koehrer" <mathias_koehrer@arcor.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Looking for a real time IPC to be used with select
Date: Sat, 17 Apr 2010 16:42:59 +0200	[thread overview]
Message-ID: <r2r6d09081c1004170742ia4f0b1c5vfa51005c934617fd@mail.gmail.com> (raw)
In-Reply-To: <3215024.1271427173625.JavaMail.ngmail@webmail08.arcor-online.net>

On Fri, Apr 16, 2010 at 4:12 PM, M. Koehrer <mathias_koehrer@arcor.de> wrote:

> Now I have the need that another real time thread B should also be able
> to trigger the "select()" in the thread_func_A() above.
> This means, I should add a suitable inter-process-communication
> between thread A and B that can be used with select() as well.
> Having this, the thread A can be triggered by the socket or
> by the IPC from thread B by adding two file desciptors to the readfds
> of select().
>
> 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.

regards
/prady

-- 
http://www.prady.in

  parent reply	other threads:[~2010-04-17 14:43 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 [this message]
2010-04-18  4:43 ` Sujit K M
2010-04-19  6:24 ` M. Koehrer
2010-04-19  6:31 ` M. Koehrer

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=r2r6d09081c1004170742ia4f0b1c5vfa51005c934617fd@mail.gmail.com \
    --to=pradysam@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mathias_koehrer@arcor.de \
    /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).