Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 6 Feb 2001 04:45:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 6 Feb 2001 04:45:27 -0500 Received: from baldur.fh-brandenburg.de ([195.37.0.5]:28089 "HELO baldur.fh-brandenburg.de") by vger.kernel.org with SMTP id ; Tue, 6 Feb 2001 04:45:15 -0500 Date: Tue, 6 Feb 2001 10:22:52 +0100 (MET) From: Roman Zippel To: Linus Torvalds cc: Alan Cox , "Stephen C. Tweedie" , Manfred Spraul , Christoph Hellwig , Steve Lord , linux-kernel@vger.kernel.org, kiobuf-io-devel@lists.sourceforge.net 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 Hi, On Mon, 5 Feb 2001, Linus Torvalds wrote: > > Does it has to be vectors? What about lists? > > I'd prefer to avoid lists unless there is some overriding concern, like a > real implementation issue. But I don't care much one way or the other - > what I care about is that the setup and usage time is as low as possible. > I suspect arrays are better for that. I was more thinking about the higher layers. Here it's simpler to setup a list of pages which can be send to a lower layer. In the page cache we already have per address space lists, so it would be very easy to use that. A lower layer can generate of course anything it wants out of this, e.g. it can generate sublists or vectors. bye, Roman - 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/