All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai@xenomai.org
Subject: [Xenomai-core] Re: [patch] static buffer for timer-bheap
Date: Fri, 2 Jun 2006 13:59:03 +0200	[thread overview]
Message-ID: <17536.10247.604874.412137@domain.hid> (raw)
In-Reply-To: <447F72A0.8000000@domain.hid>

Jan Kiszka wrote:
 > Hi,
 > 
 > this patch moves the heap for scalable timer queues into the xnpod_t
 > structure instead of allocating it dynamically. This simplifies the pod
 > initialisation and cleanup, which was not fully robust in this regard
 > anyway. If a pod is now considered too large (but we are discussion
 > kbytes here), allocating its buffer via xnarch_sysalloc would be an option.
 > 
 > In case this patch is acceptable, I would suggest merging it before 2.2
 > due to the contained (minor) fix.

Since this memory is specific to the data structure, its allocation
seems better by the data structure functions. It also make the binary
heap structure reusable for other purposes.

Could you explain why the current scheme is not robust ?

-- 


					    Gilles Chanteperdrix.


  reply	other threads:[~2006-06-02 11:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01 23:05 [Xenomai-core] [patch] static buffer for timer-bheap Jan Kiszka
2006-06-02 11:59 ` Gilles Chanteperdrix [this message]
2006-06-02 12:18   ` [Xenomai-core] " Jan Kiszka
2006-06-02 13:34     ` Gilles Chanteperdrix
2006-06-02 14:18 ` Gilles Chanteperdrix
2006-06-02 14:55   ` Jan Kiszka
2006-06-02 15:11     ` Gilles Chanteperdrix
2006-06-02 16:07       ` Jan Kiszka
2006-06-02 16:24         ` Gilles Chanteperdrix
2006-06-02 16:58           ` Jan Kiszka
2006-06-02 18:39             ` Jan Kiszka
2006-06-03 15:38               ` Gilles Chanteperdrix
2006-06-03 17:20                 ` 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=17536.10247.604874.412137@domain.hid \
    --to=gilles.chanteperdrix@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.