To: Casey Dahlin <cdahlin@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v2] waitfd
From: Andi Kleen <andi@firstfloor.org>
References: <49639EB8.40204@redhat.com>
Date: Tue, 06 Jan 2009 19:48:37 +0100
In-Reply-To: <49639EB8.40204@redhat.com> (Casey Dahlin's message of "Tue, 06 Jan 2009 13:11:04 -0500")
Message-ID: <87fxjw46ey.fsf@basil.nowhere.org>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1125
Lines: 32

Casey Dahlin <cdahlin@redhat.com> writes:

> Linux now exposes signals, timers, and events via file descriptors
> through signalfd, timerfd, and eventfd. This means programmers can use
> a single select/[e]poll call to monitor all change in their
> program. This patch aims to expose child death via the same mechanism.
>
> waitfd provides a file descriptor out of which may be read a series of
> siginfo_t objects describing child death. A child process is reaped as
> soon as its information is read. This means child monitoring too can
> be performed with that same poll call.
>
> Patch is against v2.6.28

Can you please provide a manpage with the exact proposed semantics of
the interface.

Without that it's very hard to evaluate if the interface makes sense
or not.

In general a single paragraph is not enough to justify a new system 
call.

-Andi

-- 
ak@linux.intel.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/