Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932329AbWHVSCk (ORCPT ); Tue, 22 Aug 2006 14:02:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932332AbWHVSCk (ORCPT ); Tue, 22 Aug 2006 14:02:40 -0400 Received: from relay.2ka.mipt.ru ([194.85.82.65]:27317 "EHLO 2ka.mipt.ru") by vger.kernel.org with ESMTP id S932329AbWHVSCj (ORCPT ); Tue, 22 Aug 2006 14:02:39 -0400 Date: Tue, 22 Aug 2006 22:01:35 +0400 From: Evgeniy Polyakov To: Jari Sundell Cc: Nicholas Miell , lkml , David Miller , Ulrich Drepper , Andrew Morton , netdev , Zach Brown , Christoph Hellwig Subject: Re: [take12 0/3] kevent: Generic event handling mechanism. Message-ID: <20060822180135.GA30142@2ka.mipt.ru> References: <11561555871530@2ka.mipt.ru> <1156230051.8055.27.camel@entropy> <20060822072448.GA5126@2ka.mipt.ru> <1156234672.8055.51.camel@entropy> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.7.5 (2ka.mipt.ru [0.0.0.0]); Tue, 22 Aug 2006 22:01:38 +0400 (MSD) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1542 Lines: 38 On Tue, Aug 22, 2006 at 06:57:05PM +0200, Jari Sundell (sundell.software@gmail.com) wrote: > On 8/22/06, Nicholas Miell wrote: > > > > > >OK, so with literally a dozen different interfaces to queue events to > >userspace, all of which are apparently inadequate and in need of > >replacement by kevent, don't you want to slow down a bit and make sure > >that the kevent API is correct before it becomes permanent and then just > >has to be replaced *again* ? > > > > Not to mention the name used causes (at least me) some confusion with BSD's > kqueue implementation. Skimming over the patches it actually looks somewhat > like kqueue with the more interesting features removed, like the ability to > pass the filter changes simultaneously with polling. I do not understand, what do you mean? It is obviously allowed to poll and change kevents at the same time. > Maybe this is a topic that will singe my fur, but what is wrong with the > kqueue API? Will I really have to implement support for yet another event > API in my program. Why did I not implemented it like Solaris did? Or FreeBSD did? It was designed with features mention on AIO homepage in mind, but not to be compatible with some other implementation. And why should it be? > Rakshasa -- Evgeniy Polyakov - 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/