From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264377AbUHaQxN (ORCPT ); Tue, 31 Aug 2004 12:53:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264530AbUHaQxN (ORCPT ); Tue, 31 Aug 2004 12:53:13 -0400 Received: from peabody.ximian.com ([130.57.169.10]:4539 "EHLO peabody.ximian.com") by vger.kernel.org with ESMTP id S264377AbUHaQxJ (ORCPT ); Tue, 31 Aug 2004 12:53:09 -0400 Subject: Re: [ANNOUNCE] Kernel Generalized Event Management From: Robert Love To: Bob Bennett Cc: Chris Wright , akpm@osdl.org, linux-kernel@vger.kernel.org, kgem-devel@lists.sourceforge.net In-Reply-To: <1093966183.22744.125.camel@benro02lx.ca.com> References: <20040830153942.C1973@build.pdx.osdl.net> <1093966183.22744.125.camel@benro02lx.ca.com> Content-Type: text/plain Date: Tue, 31 Aug 2004 12:52:36 -0400 Message-Id: <1093971158.4815.2.camel@betsy.boston.ximian.com> Mime-Version: 1.0 X-Mailer: Evolution 1.5.94 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2004-08-31 at 11:29 -0400, Bob Bennett wrote: > It appears that Robert Love's Kernel Events Layer project is attempting > to address a lot of these event management issues. An alternative is to > build upon this project to support synchronous event handling as well as > the event broadcasting that it performs now. With the Kernel Events Layer, we are not looking to provide synchronous notification or a method for user-space to affect kernel behavior. The Kernel Events Layer in its current incarnation (which I need to rediff and post) is a general sysfs change notifier. And it is just a layer netlink, at the end of the day. Robert Love