All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Daniel Adams <dadams81@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Problem using sem_open and rt_sem_create
Date: Thu, 29 Jan 2009 08:13:20 +0100	[thread overview]
Message-ID: <49815710.7070709@domain.hid> (raw)
In-Reply-To: <ba9b368a0901282246t4bece718g5b8512220e961719@domain.hid>

Daniel Adams wrote:
> Thanks Gillies,
> 
> Is it possible to use the rt_sem_bind from a linux process that hasn't been
> shadowed using rt_task_shadow?

No. If you read the documentation of rt_sem_bind, you will see:

Environments:

This service can be called from:

    * User-space task (switches to primary mode)

And to switch to primary mode, task needs to be shadowed with
rt_task_shadow.

> Is this the same for named pipes created using the native skin and accessing
> them from a posix interface?

The non real-time side of named pipes may be accessed using the Linux
posix interface, not Xenomai posix skin interface.

> 
> What is the recommended IPC to talk between posix threads and native rt
> threads?

It depends if you are talking about (non real-time) Linux posix threads,
or (real-time) Xenomai posix skin threads.

If you are talking about Linux posix threads, then what you are looking
for is rt_pipes.

If you are talking about Xenomai posix skin threads, then mostly any IPC
of both skins may be used. Only, you have to use the same interface with
both skins. So, for instance, if you choose Xenomai posix skin message
queues, you have to use mq_open, mq_send, mq_receive, mq_close,
mq_unlink with the threads of the two skins.

-- 
					    Gilles.


      reply	other threads:[~2009-01-29  7:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29  6:27 [Xenomai-help] Problem using sem_open and rt_sem_create Daniel Adams
2009-01-29  6:38 ` Gilles Chanteperdrix
2009-01-29  6:46   ` Daniel Adams
2009-01-29  7:13     ` Gilles Chanteperdrix [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=49815710.7070709@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=dadams81@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.