Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 8 Feb 2001 11:36:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 8 Feb 2001 11:36:24 -0500 Received: from perninha.conectiva.com.br ([200.250.58.156]:18449 "EHLO perninha.conectiva.com.br") by vger.kernel.org with ESMTP id ; Thu, 8 Feb 2001 11:36:17 -0500 Date: Thu, 8 Feb 2001 12:44:22 -0200 (BRST) From: Marcelo Tosatti To: Mikulas Patocka 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 On Thu, 8 Feb 2001, Mikulas Patocka wrote: > > > The problem is that aio_read and aio_write are pretty useless for ftp or > > > http server. You need aio_open. > > > > Could you explain this? > > If the server is sending many small files, disk spends huge amount time > walking directory tree and seeking to inodes. Maybe opening the file is > even slower than reading it - read is usually sequential but open needs to > seek at few areas of disk. > > And if you have one-threaded server using open, close, aio_read and > aio_write, you actually block the whole server while it is opening a > single file. This is not how async io is supposed to work. Ok but this is not the point of the discussion. - 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/