Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 8 Feb 2001 10:47:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 8 Feb 2001 10:47:03 -0500 Received: from artax.karlin.mff.cuni.cz ([195.113.31.125]:1554 "EHLO artax.karlin.mff.cuni.cz") by vger.kernel.org with ESMTP id ; Thu, 8 Feb 2001 10:46:55 -0500 Date: Thu, 8 Feb 2001 16:46:12 +0100 (CET) From: Mikulas Patocka To: Marcelo Tosatti cc: "Stephen C. Tweedie" , Pavel Machek , Linus Torvalds , Jens Axboe , Manfred Spraul , Ben LaHaise , Ingo Molnar , Alan Cox , Steve Lord , Linux Kernel List , kiobuf-io-devel@lists.sourceforge.net, Ingo Molnar Subject: Re: [Kiobuf-io-devel] RFC: Kernel mechanism: Compound event wait In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > > > How do you write high-performance ftp server without threads if select > > > on regular file always returns "ready"? > > > > Select can work if the access is sequential, but async IO is a more > > general solution. > > Even async IO (ie aio_read/aio_write) should block on the request queue if > its full in Linus mind. This is not problem (you can create queue big enough to handle the load). The problem is that aio_read and aio_write are pretty useless for ftp or http server. You need aio_open. Mikulas - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/