Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751309AbWJQQg3 (ORCPT ); Tue, 17 Oct 2006 12:36:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751302AbWJQQg3 (ORCPT ); Tue, 17 Oct 2006 12:36:29 -0400 Received: from relay.2ka.mipt.ru ([194.85.82.65]:42204 "EHLO 2ka.mipt.ru") by vger.kernel.org with ESMTP id S1751293AbWJQQg2 (ORCPT ); Tue, 17 Oct 2006 12:36:28 -0400 Date: Tue, 17 Oct 2006 20:35:36 +0400 From: Evgeniy Polyakov To: Eric Dumazet Cc: Johann Borck , Ulrich Drepper , Ulrich Drepper , lkml , David Miller , Andrew Morton , netdev , Zach Brown , Christoph Hellwig , Chase Venters Subject: Re: [take19 1/4] kevent: Core files. Message-ID: <20061017163536.GA17692@2ka.mipt.ru> References: <11587449471424@2ka.mipt.ru> <200610171732.28640.dada1@cosmosbay.com> <20061017160155.GA18522@2ka.mipt.ru> <200610171826.05028.dada1@cosmosbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <200610171826.05028.dada1@cosmosbay.com> 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, 17 Oct 2006 20:35:37 +0400 (MSD) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1825 Lines: 40 On Tue, Oct 17, 2006 at 06:26:04PM +0200, Eric Dumazet (dada1@cosmosbay.com) wrote: > On Tuesday 17 October 2006 18:01, Evgeniy Polyakov wrote: > > > Ok, there is one apologist for mmap buffer implementation, who forced me > > to create first implementation, which was dropped due to absense of > > remote mental reading abilities. > > Ulrich, does above approach sound good for you? > > I actually do not want to reimplement something, that will be > > pointed to with words 'no matter what you say, it is broken and I do not > > want it' again :). > > In my humble opinion, you should first write a 'real application', to show how > the mmap buffer and kevent syscalls would be used (fast path and > slow/recovery paths). I am sure it would be easier for everybody to agree on > the API *before* you start coding a *lot* of hard (kernel) stuff : It would > certainly save your mental CPU cycles (and ours too :) ) > > This 'real application' could be the event loop of a simple HTTP server, or a > basic 'echo all' server. Adding the bits about timers events and signals > should be done too. I wrote one with previous ring buffer implementation - it used timers and echoed when they fired, it was even described in details in one of the lwn.net articles. I'm not going to waste others and my time implementing feature requests without at least _some_ feedback from those who asked them. In case when person, originally requested some feature, does not answer and there are other opinions, only they will be get into account of course. > Eric -- 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/