linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carsten Emde <Carsten.Emde@osadl.org>
To: "M. Koehrer" <mathias_koehrer@arcor.de>
Cc: dvhltc@us.ibm.com, linux-rt-users@vger.kernel.org
Subject: Re: Replacement for Xenomai's Message queues?
Date: Thu, 28 Jan 2010 22:50:55 +0100	[thread overview]
Message-ID: <4B6206BF.9080708@osadl.org> (raw)
In-Reply-To: <5579824.1264709193179.JavaMail.ngmail@webmail08.arcor-online.net>

Mathias,

> [..] I have two real time applications (two processes), each running 
> a few real time threads. For inter process communication I want to 
> exchange data between the two applications. For this I want to use 
> two queues - one for direction A->B and one for B->A. Now I have the 
> situation that one thread in B that handles the A->B queue is
> waiting for data from A. Whenever A has the data available, it writes
> the data into the A->B queue. Immediately after receiving data from
> A, B unblocks and computes some answer data that is written into the
> B->A queue. The time between sending the data in A and getting the
> data back from B should be as low as possible (real time
> requirements: at max tens of microseconds...).
> 
> The functionality of mq_send, mq_receive looks suitable.
Alternatively, you may consider to use shared memory and to synchronize
and protect accesses to that memory with semaphores. The rt-tests suite
contains several examples of how to do it. Before using these test
programs as template for your own application, you may even run them as
they are to check whether the worst-case latency of such mechanisms fits
your requirements.

	Carsten.

  parent reply	other threads:[~2010-01-28 22:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28  8:09 Replacement for Xenomai's Message queues? M. Koehrer
2010-01-28 18:56 ` Darren Hart
2010-01-28 20:06 ` M. Koehrer
2010-01-28 21:12   ` Darren Hart
2010-01-28 21:50   ` Carsten Emde [this message]
2010-01-28 22:18   ` Tim Sander

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=4B6206BF.9080708@osadl.org \
    --to=carsten.emde@osadl.org \
    --cc=dvhltc@us.ibm.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).