From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: Andrea Arcangeli <aarcange@redhat.com>
Subject: Re: [Qemu-devel] [RFC 1/2] pci-dma-api-v1
Date: Sun, 30 Nov 2008 16:31:05 -0600 [thread overview]
Message-ID: <49331429.1090300@codemonkey.ws> (raw)
In-Reply-To: <20081128191819.GA18031@shareable.org>
Jamie Lokier wrote:
> 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.
>
No. lio_listio is a batch submission mechanism, not an operation.
Each request maintains the same behavior as if they were submitted
independently. This means if you're doing a write operation and you
submit a vectored request via lio_listio, each portion of the vector has
to complete before the other one.
But most importantly, pthreads doesn't use readv/writev to implement
lio_listio as has been mentioned elsewhere.
Regards,
Anthony Liguori
> Doesn't explain why they didn't _start_ with aio_readv before
> inventing lio_listio, but there you go. Unix history.
>
> -- Jamie
>
>
>
next prev parent reply other threads:[~2008-11-30 22:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 12:35 [Qemu-devel] [RFC 1/2] pci-dma-api-v1 Andrea Arcangeli
2008-11-27 12:43 ` [Qemu-devel] [RFC 2/2] bdrv_aio_readv/writev_em Andrea Arcangeli
2008-11-28 11:09 ` Jamie Lokier
2008-11-27 19:14 ` [Qemu-devel] [RFC 1/2] pci-dma-api-v1 Blue Swirl
2008-11-28 1:56 ` Andrea Arcangeli
2008-11-28 17:59 ` Blue Swirl
2008-11-28 18:50 ` Andrea Arcangeli
2008-11-28 19:03 ` Blue Swirl
2008-11-28 19:18 ` Jamie Lokier
2008-11-29 19:49 ` Avi Kivity
2008-11-30 17:20 ` Andrea Arcangeli
2008-11-30 22:31 ` Anthony Liguori [this message]
2008-11-30 18:04 ` Andrea Arcangeli
2008-11-30 17:41 ` [Qemu-devel] [RFC 1/1] pci-dma-api-v2 Andrea Arcangeli
2008-11-30 18:36 ` [Qemu-devel] " Blue Swirl
2008-11-30 19:04 ` Andrea Arcangeli
2008-11-30 19:11 ` Blue Swirl
2008-11-30 19:20 ` Andrea Arcangeli
2008-11-30 21:36 ` Blue Swirl
2008-11-30 22:54 ` Anthony Liguori
2008-11-30 22:50 ` [Qemu-devel] " Anthony Liguori
2008-12-01 9:41 ` Avi Kivity
2008-12-01 16:37 ` Anthony Liguori
2008-12-02 9:45 ` Avi Kivity
2008-11-30 22:38 ` [Qemu-devel] [RFC 1/2] pci-dma-api-v1 Anthony Liguori
2008-11-30 22:51 ` Jamie Lokier
2008-11-30 22:34 ` Anthony Liguori
2008-11-29 19:48 ` Avi Kivity
2008-11-30 17:29 ` Andrea Arcangeli
2008-11-30 20:27 ` Avi Kivity
2008-11-30 22:33 ` Andrea Arcangeli
2008-11-30 22:33 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49331429.1090300@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aarcange@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.