All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theo Veenker <Theo.Veenker@domain.hid>
To: rpm@xenomai.org
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] multiple tasks calling rt_pipe_write() on same pipe
Date: Mon, 10 Dec 2007 18:51:55 +0100	[thread overview]
Message-ID: <475D7CBB.90206@domain.hid> (raw)
In-Reply-To: <475D7B40.7080408@domain.hid>

Philippe Gerum wrote:
> Theo Veenker wrote:
>> Hi,
>>
>> I have multiple tasks all calling rt_pipe_write() to send some data
>> through the same pipe. Is my assumption that rt_pipe_write() won't be
>> interupted when a higher priority thread becomes ready correct?
>>
> 
> Messages are always atomically queued on the write side, so the contents
> of two distinct messages won't be mixed. Of course, the priority may
> still affect the queuing order of both messages, though. Does this
> answer your question?
> 

Perfectly! Thanks.

Theo



      reply	other threads:[~2007-12-10 17:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 17:27 [Xenomai-help] multiple tasks calling rt_pipe_write() on same pipe Theo Veenker
2007-12-10 17:45 ` Philippe Gerum
2007-12-10 17:51   ` Theo Veenker [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=475D7CBB.90206@domain.hid \
    --to=theo.veenker@domain.hid \
    --cc=rpm@xenomai.org \
    --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.