Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030341AbXBZT1L (ORCPT ); Mon, 26 Feb 2007 14:27:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030406AbXBZT1L (ORCPT ); Mon, 26 Feb 2007 14:27:11 -0500 Received: from relay.2ka.mipt.ru ([194.85.82.65]:44266 "EHLO 2ka.mipt.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030341AbXBZT1J (ORCPT ); Mon, 26 Feb 2007 14:27:09 -0500 Date: Mon, 26 Feb 2007 22:20:02 +0300 From: Evgeniy Polyakov To: Chris Friesen Cc: Arjan van de Ven , Ingo Molnar , Linus Torvalds , Ulrich Drepper , linux-kernel@vger.kernel.org, Christoph Hellwig , Andrew Morton , Alan Cox , Zach Brown , "David S. Miller" , Suparna Bhattacharya , Davide Libenzi , Jens Axboe , Thomas Gleixner Subject: Re: [patch 00/13] Syslets, "Threadlets", generic AIO support, v3 Message-ID: <20070226192001.GA17892@2ka.mipt.ru> References: <20070221233111.GB5895@elte.hu> <45DCD9E5.2010106@redhat.com> <20070222074044.GA4158@elte.hu> <20070222113148.GA3781@2ka.mipt.ru> <20070226131133.GA11777@elte.hu> <20070226173701.GD22454@2ka.mipt.ru> <1172513950.3280.388.camel@laptopd505.fenrus.org> <20070226183856.GF22454@2ka.mipt.ru> <45E32D61.7060403@nortel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <45E32D61.7060403@nortel.com> User-Agent: Mutt/1.5.9i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (2ka.mipt.ru [0.0.0.0]); Mon, 26 Feb 2007 22:22:48 +0300 (MSK) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1135 Lines: 30 On Mon, Feb 26, 2007 at 12:56:33PM -0600, Chris Friesen (cfriesen@nortel.com) wrote: > Evgeniy Polyakov wrote: > > >I never ever tried to say _everything_ must be driven by events. > >IO must be driven, it is a must IMO. > > Do you disagree with Linus' post about the difficulty of treating > open(), fstat(), page faults, etc. as events? Or do you not consider > them to be IO? >From practical point of view - yes some of that processes are complex enough to not attract attention as async usage model. But I'm absolutely for the scenario, when several operations are performed asynchronously like open+stat+fadvice+sendfile. By IO I meant something which has end result, and that result must be enough to start async processing - data in the buffer for example. Async open I would combine with actual data processing - that one can be a one event. > Chris -- 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/