From: Anthony Liguori <anthony@codemonkey.ws>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Linux SIGIO handling changes
Date: Mon, 21 Apr 2008 13:48:39 -0500 [thread overview]
Message-ID: <480CE187.4080707@codemonkey.ws> (raw)
In-Reply-To: <200804211713.38338.paul@codesourcery.com>
Paul Brook wrote:
>> posix-aio is a pretty unfortunate interface as it doesn't provide a
>> mechanism to do asynchronous fdatasync()
>>
>
> Isn't that what aio_fsync(O_DSYNC) does?
>
Indeed. So it's really just the lack of vectored operations and the
fact that we limit it to a single thread.
Regards,
Anthony Liguori
> Paul
>
next prev parent reply other threads:[~2008-04-21 18:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 9:20 [Qemu-devel] Linux SIGIO handling changes Anders Melchiorsen
2008-04-20 9:20 ` [Qemu-devel] [PATCH] Use SIGALRM even for timers delivered over a fd Anders Melchiorsen
2008-04-20 9:20 ` [Qemu-devel] [PATCH] Use SIGIO in Linux host Anders Melchiorsen
2008-04-20 22:04 ` [Qemu-devel] Linux SIGIO handling changes Anthony Liguori
2008-04-21 13:37 ` Avi Kivity
2008-04-21 15:43 ` Anthony Liguori
2008-04-21 16:13 ` Paul Brook
2008-04-21 18:48 ` Anthony Liguori [this message]
2008-04-22 8:02 ` Avi Kivity
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=480CE187.4080707@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=paul@codesourcery.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 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).