From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Extensible heaps - needed for the future?
Date: Sun, 11 Dec 2005 19:15:21 +0100 [thread overview]
Message-ID: <439C6CB9.6050605@domain.hid> (raw)
In-Reply-To: <439C654F.9080805@domain.hid>
Jan Kiszka wrote:
> Hi,
>
> I noticed that xnhead_extend() is not used at the moment [1], thus the
> whole extent management is redundent for now. Are there plans to use it
> in the future? Should we keep this feature?
>
> I'm asking as I still have the idea in my head of breaking up the heap
> service and introducing a generic allocator interface to select
> different heap allocators at compile time. So, should extensions be an
> optional feature of an allocator?
Keep in mind that the native API is a plain client of the abstract RTOS
implemented by the nucleus, nothing more. What the native API does not
use in this area would probably be useful to other clients though. For
instance, the VRTX skin locally reimplements its own heap extension
system that could be replaced by the nucleus one -- and should.
>
> Jan
>
>
> [1]http://www.rts.uni-hannover.de/xenomai/lxr/ident?v=SVN-trunk;i=xnheap_extend
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core
--
Philippe.
next prev parent reply other threads:[~2005-12-11 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-11 17:43 [Xenomai-core] Extensible heaps - needed for the future? Jan Kiszka
2005-12-11 18:15 ` Philippe Gerum [this message]
2005-12-11 19:35 ` 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=439C6CB9.6050605@domain.hid \
--to=rpm@xenomai.org \
--cc=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.