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: Re: [Xenomai-core] [RFC][patch] per-process data.
Date: Mon, 8 May 2006 01:04:38 +0200	[thread overview]
Message-ID: <17502.32006.418774.459215@domain.hid> (raw)
In-Reply-To: <445E637A.5080706@domain.hid>

Jan Kiszka wrote:
 > Likely I did not yet get the full picture: What prevents using another
 > adeos per-task key for this? 

We would need a per-task key for every skin that needs a per-process
data, but more importantly, we would need to track the clone syscalls
(that would be another adeos event) in order to propagate the per-task
data to each thread of the process. Or maybe ptds are inherited upon
clone ?

And why is it required to establish a new
 > termination hook? Are there scenarios where the existing
 > task-termination hook is not suited for the planned cleanup work?

Because the existing hook is called once for every thread exit, whereas
the pexit event get triggered when the last thread of a process exits,
this is the only moment we are sure we can destroy per-process data.

Using the existing hook, we would need to decrement a reference counter
in the hook, but then we would (again) need to track the clone syscalls
in order to increment the reference counter.

Both implementations require to add an adeos event, the one I chose, if
it works, avoid reference counting.

-- 


					    Gilles Chanteperdrix.


  reply	other threads:[~2006-05-07 23:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-07 18:00 [Xenomai-core] [RFC][patch] per-process data Gilles Chanteperdrix
2006-05-07 21:15 ` Jan Kiszka
2006-05-07 23:04   ` Gilles Chanteperdrix [this message]
2006-05-08 10:18     ` Dmitry Adamushko
2006-05-08 12:47       ` Gilles Chanteperdrix
2006-05-08 13:05     ` Jan Kiszka
2006-05-08 12:51 ` Gilles Chanteperdrix
2006-05-08 13:14   ` Gilles Chanteperdrix
2006-05-08 13:51   ` Philippe Gerum
2006-05-09 17:49     ` Gilles Chanteperdrix
2006-05-09 22:09       ` Philippe Gerum
2006-05-10 13:03         ` Gilles Chanteperdrix
2006-05-11 12:53           ` Philippe Gerum
2006-05-11 14:03             ` Gilles Chanteperdrix
2006-05-11 14:12               ` Philippe Gerum

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=17502.32006.418774.459215@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.