All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Native skin: user space handles sharable between processes?
Date: Mon, 25 Aug 2008 13:36:42 +0200	[thread overview]
Message-ID: <48B2994A.1050708@domain.hid> (raw)

Hi,

what is the policy for the user space handles the native skin generates:
Can the user share them between processes via putting them into shared
memory (like it is allowed for some POSIX objects)?

I'm wondering if I have to use the POSIX pattern to resolve the address
of a fast mutex: If shared, look to global heap, otherwise use
process-local heap. If native handle structures were only valid within a
single context, I could use absolute pointers instead, saving some code
and data.

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux


             reply	other threads:[~2008-08-25 11:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-25 11:36 Jan Kiszka [this message]
2008-08-25 12:08 ` [Xenomai-core] Native skin: user space handles sharable between processes? Gilles Chanteperdrix
2008-08-25 12:16   ` Jan Kiszka
2008-08-25 12:21     ` Gilles Chanteperdrix
2008-08-25 12:23       ` Jan Kiszka

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=48B2994A.1050708@domain.hid \
    --to=jan.kiszka@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.