From: Philippe Gerum <rpm@xenomai.org>
To: stefan.eletzhofer@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] rt_heap_bind in kernel module
Date: Thu, 20 Apr 2006 16:18:18 +0200 [thread overview]
Message-ID: <4447982A.9060409@domain.hid> (raw)
In-Reply-To: <200604201442.18803.stefan.eletzhofer@domain.hid>
Stefan Eletzhofer wrote:
> Hi,
> reading the API docs (2.1.0) of the xenomai native API I noticed that the
> rt_heap_bind() call is a userspace-only call and i'm wondering why that is
> the case? Or am I missing something here?
>
Binding op are not supported in kernel space, basically because one sees
a single address space there, and it's always possible to share the
original object descriptor directly between modules as a plain memory
area. The synchronization the binding ops provide between the creator
and the users of a given resource has been ignored for kernel space.
> I'm in the process of porting applications which use the RTAI shm module
> in both user space and kernel space; these applications basically allocate
> the shared memory chunks in user space and then have kernel modules dump
> data into these areas.
>
> To port things, I've coded a rt_heap_bind() for kernel space modelled after
> the code in skins/native/syscalls.c using the nucleus registry API, and that
> seems to work. So, is this missing call just laziness, then I'd post a patch.
>
> Thanks,
> Stefan E.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
--
Philippe.
prev parent reply other threads:[~2006-04-20 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 12:42 [Xenomai-help] rt_heap_bind in kernel module Stefan Eletzhofer
2006-04-20 14:18 ` Philippe Gerum [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=4447982A.9060409@domain.hid \
--to=rpm@xenomai.org \
--cc=stefan.eletzhofer@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.