From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1L68rC-0006hm-1M
	for qemu-devel@nongnu.org; Fri, 28 Nov 2008 14:18:26 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1L68rA-0006gw-2v
	for qemu-devel@nongnu.org; Fri, 28 Nov 2008 14:18:25 -0500
Received: from [199.232.76.173] (port=45503 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1L68r9-0006gp-Rq
	for qemu-devel@nongnu.org; Fri, 28 Nov 2008 14:18:23 -0500
Received: from mail2.shareable.org ([80.68.89.115]:43121)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <jamie@shareable.org>) id 1L68r9-0003lC-HS
	for qemu-devel@nongnu.org; Fri, 28 Nov 2008 14:18:23 -0500
Date: Fri, 28 Nov 2008 19:18:19 +0000
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] [RFC 1/2] pci-dma-api-v1
Message-ID: <20081128191819.GA18031@shareable.org>
References: <20081127123538.GC10348@random.random>
	<f43fc5580811271114u7ecc3277kc7518fb7dbf9b4c0@mail.gmail.com>
	<20081128015602.GA31011@random.random>
	<f43fc5580811280959k3410e62eq7a2a46417b438b64@mail.gmail.com>
	<20081128185001.GD31011@random.random>
	<f43fc5580811281103t5c396e3ay9c98b6c1658dd8dd@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f43fc5580811281103t5c396e3ay9c98b6c1658dd8dd@mail.gmail.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Andrea Arcangeli <aarcange@redhat.com>

Blue Swirl wrote:
> >  I wonder how can possibly aio_readv/writev be missing in posix aio?
> >  Unbelievable. It'd be totally trivial to add those to glibc, much
> >  easier infact than to pthread_create by hand, but how can we add a
> >  dependency on a certain glibc version? Ironically it'll be more
> >  user-friendly to add dependency on linux kernel-aio implementation
> >  that is already available for ages and it's guaranteed to run faster
> >  (or at least not slower).
> 
> There's also lio_listio that provides for vectored AIO.

I think lio_listio is the missing aio_readv/writev.

It's more versatile, and that'll by why POSIX never bothered with
aio_readv/writev.

Doesn't explain why they didn't _start_ with aio_readv before
inventing lio_listio, but there you go.  Unix history.

-- Jamie