Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932267AbWHWBvj (ORCPT ); Tue, 22 Aug 2006 21:51:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932256AbWHWBvj (ORCPT ); Tue, 22 Aug 2006 21:51:39 -0400 Received: from alnrmhc14.comcast.net ([206.18.177.54]:10978 "EHLO alnrmhc11.comcast.net") by vger.kernel.org with ESMTP id S932190AbWHWBvi (ORCPT ); Tue, 22 Aug 2006 21:51:38 -0400 Subject: Re: [take12 0/3] kevent: Generic event handling mechanism. From: Nicholas Miell To: Ulrich Drepper Cc: David Miller , jmorris@namei.org, johnpol@2ka.mipt.ru, linux-kernel@vger.kernel.org, akpm@osdl.org, netdev@vger.kernel.org, zach.brown@oracle.com, hch@infradead.org In-Reply-To: <44EB974B.3030200@redhat.com> References: <1156276823.2476.22.camel@entropy> <20060822.133606.48392664.davem@davemloft.net> <1156281220.2476.65.camel@entropy> <20060822.142500.11271092.davem@davemloft.net> <1156287511.2476.137.camel@entropy> <44EB974B.3030200@redhat.com> Content-Type: text/plain Date: Tue, 22 Aug 2006 18:51:06 -0700 Message-Id: <1156297866.2476.208.camel@entropy> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 (2.6.3-1.fc5.5.0.njm.1) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1745 Lines: 36 On Tue, 2006-08-22 at 16:46 -0700, Ulrich Drepper wrote: > I so far also haven't taken the time to look exactly at the interface. > I plan to do it asap since this is IMO our big chance to get it right. > I want to have a unifying interface which can handle all the different > events we need and which come up today and tomorrow. We have to be able > to handle not only file descriptors and AIO but also timers, signals, > message queues (OK, they are file descriptors but let's make it > official), futexes. I'm probably missing the one or the other thing now. Are you sure about signals? I thought about that, but they generally fall into two categories: signals that have to be signals (i.e. SIGILL, SIGABRT, SIGFPE, SIGSEGV, etc.) and signals that should be replaced a queued event notification (SIGALRM, SIGRTMIN-SIGRTMAX). Of course, that leaves things like SIGTERM, SIGINT, SIGQUIT, etc. so, uh, nevermind then. Signal redirection to event queues is definitely needed. > DaveM says there are example programs for the current interfaces. I > must admit I haven't seen those either. So if possible, point the world > to them again. If you do that now I'll review everything and write up > my recommendations re the interface before Monday. There's a handful of little test apps at http://tservice.net.ru/~s0mbre/archive/kevent/ , but they don't work with the current iteration of the interface. I don't know if there are others somewhere else. -- Nicholas Miell - 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/