[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070410163714.GA104@tv-sign.ru>
Date: Tue, 10 Apr 2007 20:37:14 +0400
From: Oleg Nesterov <oleg@...sign.ru>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>, Robin Holt <holt@....com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Chris Snook <csnook@...hat.com>, linux-kernel@...r.kernel.org,
Jack Steiner <steiner@...ricas.sgi.com>,
Roland McGrath <roland@...hat.com>, acahalan@...il.com
Subject: Re: [PATCH] Only send pdeath_signal when getppid changes.
On 04/10, Eric W. Biederman wrote:
>
> So this patch fixes the pdeath_signal behaviour only sending a signal
> when the results of getppid would change.
Don't get me wrong, I personally like this patch very much. However,
A long ago, Albert Cahalan (cc-ed) wrote:
>
> I rely on thread-to-thread pdeath notification for my emulator.
> I also need notification on loss of a thread-group or mm, so I do
> my best to emulate those based on thread-to-thread notification.
>
> ...
>
> The way I use it pdeath_signal:
>
> The parent is one of many tasks within a task group.
> The child is not within that thread group, but shares VM.
> (the child is single threaded, existing only to get the signal)
> For each task in the thread group, there is a child task
> waiting for parent death notification. (there are two other
> tasks sharing VM but not in the task group: one to do
> async memory searching, and one to communicate with
> a user interface for debugging -- like an interactive valgrind)
Oleg.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists