[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Hacking gnumach to track parental relationship of tasks

From: Neal H. Walfield
Subject: Re: Hacking gnumach to track parental relationship of tasks
Date: Fri, 06 Sep 2013 12:04:46 +0200
User-agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (Gojō) APEL/10.8 Emacs/23.2 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)

At Thu,  5 Sep 2013 16:57:41 +0200,
Justus Winter wrote:
> I made two rather small and (as I thought) straight forward changes to
> gnumach to keep track of a tasks father task and to make this
> information available.

What happens when the parent task is destroyed?  Are the children
destroyed with it automatically?  Does it stick around as a zombie?
Are the children reparented to their grandparent?  The last option has
the least overhead, but then you need to be careful about children
escaping from the task hierarchy.  (This is probably relevant to a
cgroup implementation.)

> Now I know handing out task ports right and
> left is not a wise thing to do, but I wanted to do it this way as a
> first step.

A child should not necessarily be able to send to its parent (the
parent may want to contain the child in some way).  However, it seems
reasonable to allow a parent to send to its child.

Note: the parent task should probably be the parent as provided to


reply via email to

[Prev in Thread] Current Thread [Next in Thread]