All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai@xenomai.org, "Moser, Dan" <DMoser@domain.hid>,
	xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Re: [Xenomai-help] deleting a left over heap (shared memory segment)
Date: Tue, 11 Apr 2006 22:47:46 +0200	[thread overview]
Message-ID: <443C15F2.1060600@domain.hid> (raw)
In-Reply-To: <443C11CF.7030905@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]

Philippe Gerum wrote:
> Moser, Dan wrote:
>> Hi,
>>
>> I was wondering if there was a command line method for deleting left
>> over heaps (i.e., those that were not properly deleted with a call to
>> rt_heap_delete()) from /proc/xenomai/registry/native/heaps.
>>
>> Just a simple rm command (as root) yields the following:
>>
>> # rm -f myshmem
>> cannot remove `myshmem': Operation not permitted
>>
> 
> For the moment, there is way to remove lingering native API objects from
                         ^^^
                         no?!
> the /proc interface. On the other hand, the RTDM API allows this for
> some of its objects by writing a magic value to the proper /proc entry,
> and we might use the same technique to provide this feature to the
> native one.

Err, before adding to much stuff in this style (I'm allowed to diss it,
I introduced it ;) ), I would rather suggest to start thinking about a
scalable(!) cleanup hook for kernel objects.

We would need, e.g., per-process ownership of things like IPC objects or
RTDM devices instances. Then we could simply walk the chain on cleanup,
preferable in Linux context. This is a concept I already implemented in
an experimental skin. If this robustness should add too much overhead
(but I don't think so), we could make it optional. RTDM is already
prepared for it ("forced closure")!

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

      parent reply	other threads:[~2006-04-11 20:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-11 15:45 [Xenomai-help] deleting a left over heap (shared memory segment) Moser, Dan
2006-04-11 20:30 ` Philippe Gerum
2006-04-11 20:42   ` Philippe Gerum
2006-04-11 20:47   ` Jan Kiszka [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=443C15F2.1060600@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=DMoser@domain.hid \
    --cc=rpm@xenomai.org \
    --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.