All of lore.kernel.org
 help / color / mirror / Atom feed
From: NZG <ngustavson@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-help] writing from NRT to a rt_pipe-> easy wait for completion
Date: Thu, 7 Jun 2007 17:09:03 -0500	[thread overview]
Message-ID: <200706071709.03430.ngustavson@domain.hid> (raw)
In-Reply-To: <1181247263.4998.149.camel@domain.hid>

On Thursday 07 June 2007 3:14 pm, Philippe Gerum wrote:
> On Thu, 2007-06-07 at 14:46 -0500, NZG wrote:
> > > Yes, clearly.
> >
> > Ah, that in conjunction with the
> > "can't use message pipe - Cannot allocate memory"
> > thread resolves my issues then.
> >
> > My assumption was that data would exist in the pipe after the write until
> > the pipe was destroyed, irrespective of the "openness" of the NRT side.
>
> Nope, as a general rule, the read-side of an endpoint is flushed when
> the other end closes. Then, you have also to take into account the
> priority of the thread waiting on the endpoint wrt the priority of the
> one which closes the other side.
So, if I wanted to use standard NRT calls in user space to wait for data to 
actually be delivered through the rt pipe before closing the fd, what would 
be the best method? Select? Or is there a simple call for this I'm missing?

thx,
NZG




  parent reply	other threads:[~2007-06-07 22:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07 18:57 [Xenomai-help] writing from NRT to a rt_pipe NZG
2007-06-07 19:13 ` NZG
2007-06-07 19:34   ` Philippe Gerum
2007-06-07 19:46     ` NZG
2007-06-07 19:51       ` NZG
2007-06-07 20:14       ` Philippe Gerum
2007-06-07 20:41         ` NZG
2007-06-07 22:09         ` NZG [this message]
2007-06-07 22:44           ` [Xenomai-help] writing from NRT to a rt_pipe-> easy wait for completion Philippe Gerum
2007-06-07 22:57             ` NZG
2007-06-07 19:33 ` [Xenomai-help] writing from NRT to a rt_pipe Philippe Gerum

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=200706071709.03430.ngustavson@domain.hid \
    --to=ngustavson@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.