From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [RFC] Replace posix-aio with custom thread pool
Date: Thu, 11 Dec 2008 10:41:11 -0600 [thread overview]
Message-ID: <494142A7.2030908@codemonkey.ws> (raw)
In-Reply-To: <494130B5.2080800@redhat.com>
Gerd Hoffmann wrote:
> Andrea Arcangeli wrote:
>
>> My current feeling is that this user thread aio thing will never
>> satisfy enterprise usage and kernel aio is mandatory in my view.
>>
>
> Well, linux kernel aio has its share of problems too:
>
> * Anthony mentioned it may block on certain circumstances (forgot
> which ones), and you can't figure beforehand to turn off aio then.
>
> * It can't handle block allocation. Kernel handles that by doing
> such writes synchronously via VFS layer (instead of the separate
> aio code paths). Leads to horrible performance and bug reports
> such as "installs on sparse files are very slow".
>
> * support for vectored aio isn't that old. IIRC it was added
> somewhen around 2.6.20 (newer that current suse/redhat enterprise
> versions). Which IMHO means you can't expect it being present
> unconditionally.
>
>
>> And we should concentrate on kernel aio and get rid
>> of threads when host OS is linux.
>>
>
> Threads will be there anyway for kvm smp.
>
>
>> Has anybody a patch implementing kernel aio that I can plug into the
>> dma zerocopy api? I'm not so sure clone aio is worth maintaining
>> inside qemu instead of evolving glibc
>>
>
> Well, wait for glibc isn't going to fly. glibc waits for posix, and
> posix waits for a reference implementation (which will not be glibc).
>
>
>> and kernel with preadv/pwritev
>>
>
> With that in place you don't need kernel aio any more, then you can
> really do it in userspace with threads. But that probably would be
> linux-only ^W^W^W
>
linux-only is okay but we just need a relatively sane fall back. There
have been preadv/pwritev patches posted before, they just for some
reason never were merged.
http://lwn.net/Articles/163603/
> ahem: http://www.daemon-systems.org/man/preadv.2.html
>
Yeah, dunno if that's all BSDs or just NetBSD.
Regards,
Anthony Liguori
> cheers,
> Gerd
>
next prev parent reply other threads:[~2008-12-11 16:41 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 21:21 [Qemu-devel] [RFC] Replace posix-aio with custom thread pool Anthony Liguori
2008-12-06 9:03 ` Blue Swirl
2008-12-06 18:26 ` Jamie Lokier
2008-12-08 18:23 ` Anthony Liguori
2008-12-09 15:51 ` Gerd Hoffmann
2008-12-09 16:01 ` Anthony Liguori
2008-12-10 16:44 ` Andrea Arcangeli
2008-12-10 17:21 ` Anthony Liguori
2008-12-10 17:29 ` Gerd Hoffmann
2008-12-10 18:50 ` Anthony Liguori
2008-12-10 19:08 ` Andrea Arcangeli
2008-12-11 13:12 ` Andrea Arcangeli
2008-12-11 15:24 ` Gerd Hoffmann
2008-12-11 15:53 ` Andrea Arcangeli
2008-12-11 16:11 ` Gerd Hoffmann
2008-12-11 16:49 ` Andrea Arcangeli
2008-12-11 17:20 ` Gerd Hoffmann
2008-12-11 18:11 ` Andrea Arcangeli
2008-12-11 20:38 ` Gerd Hoffmann
2008-12-11 20:40 ` Anthony Liguori
2008-12-12 8:23 ` Jens Axboe
2008-12-12 11:51 ` Andrea Arcangeli
2008-12-12 11:54 ` Jens Axboe
2008-12-12 14:13 ` Andrea Arcangeli
2008-12-12 14:24 ` Anthony Liguori
2008-12-12 16:33 ` Chris Wright
2008-12-12 16:51 ` Anthony Liguori
2008-12-12 16:52 ` Chris Wright
2008-12-11 21:32 ` Christoph Hellwig
2008-12-12 0:27 ` Andrea Arcangeli
2008-12-11 21:30 ` Christoph Hellwig
2008-12-11 16:41 ` Anthony Liguori [this message]
2008-12-12 14:24 ` Andrea Arcangeli
2008-12-12 14:35 ` Anthony Liguori
2008-12-12 15:44 ` Andrea Arcangeli
2008-12-12 16:49 ` Anthony Liguori
2008-12-12 17:09 ` Andrea Arcangeli
2008-12-12 17:25 ` Anthony Liguori
2008-12-12 17:52 ` Andrea Arcangeli
2008-12-12 18:17 ` Anthony Liguori
2008-12-12 18:26 ` Andrea Arcangeli
2008-12-12 20:12 ` Gerd Hoffmann
2008-12-12 20:17 ` Anthony Liguori
2008-12-12 20:35 ` Gerd Hoffmann
2008-12-09 17:16 ` Avi Kivity
2008-12-17 14:44 ` Ian Jackson
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=494142A7.2030908@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aarcange@redhat.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).