Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965285AbXBQPAh (ORCPT ); Sat, 17 Feb 2007 10:00:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965287AbXBQPAh (ORCPT ); Sat, 17 Feb 2007 10:00:37 -0500 Received: from [212.12.190.178] ([212.12.190.178]:32938 "EHLO raad.intranet" rhost-flags-FAIL-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S965285AbXBQPAg (ORCPT ); Sat, 17 Feb 2007 10:00:36 -0500 From: Al Boldi To: linux-kernel@vger.kernel.org Subject: Re: [patch 05/11] syslets: core code Date: Sat, 17 Feb 2007 17:57:56 +0300 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200702171757.56364.a1426z@gawab.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1059 Lines: 30 Evgeniy Polyakov wrote: > Ray Lee (ray-lk@madrabbit.org) wrote: > > The truth of this lies somewhere in the middle. It isn't kernel driven, > > or userspace interface driven, but a tradeoff between the two. > > > > So: > > > Userspace_API_is_the_ever_possible_last_thing_to_ever_think_about. > > > Period > > > > Please listen to those of us who are saying that this might not be the > > case. Maybe we're idiots, but then again maybe we're not, okay? > > Sometimes the API really *DOES* change the underlying implementation. > > It is exactly the time to say what interface sould be good. > System is almost ready - it is time to make it looks cool for users. IMHO, what is needed is an event registration switch-board that handles notifications from the kernel and the user side respectively. Thanks! -- Al - 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/