From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Cc: Uri Lublin <uril@redhat.com>
Subject: Re: [Qemu-devel] migration: adding migration to/from a file (v2)
Date: Thu, 19 Feb 2009 20:28:49 +0000 [thread overview]
Message-ID: <20090219202849.GE22319@shareable.org> (raw)
In-Reply-To: <499DBB8E.6030705@codemonkey.ws>
Anthony Liguori wrote:
> >Sure looks like a bug.
> I wish! It's Unix suckiness.
Windows is the same.
It's a more of a conceptual problem than it looks, not merely an API bug.
It comes down to "what would 'readable' and 'writable' mean on a file?".
For a pipe or socket, readability depends on whether it's connected
and some data has been received from another process. That's
well-defined.
For a file, readability depends on the OS knowing in advance that you
_want_ to read the file so it can issue a request to the underlying
device - but it doesn't know you want to read the file until you call
read() at a specific offset and length, so readability is not
well-defined. Writability is similar but also depends on dynamic
memory availability.
That's why AIO is more fundemantally required for files than streams.
AIO is how you tell the OS "I'm going to want to read or write this bit".
-- Jamie
next prev parent reply other threads:[~2009-02-19 20:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 11:45 [Qemu-devel] migration: adding migration to/from a file (v2) Uri Lublin
2009-02-19 13:57 ` Anthony Liguori
2009-02-19 16:14 ` Uri Lublin
2009-02-19 16:51 ` Anthony Liguori
2009-02-19 19:06 ` Uri Lublin
2009-02-19 20:05 ` Anthony Liguori
2009-02-19 20:28 ` Jamie Lokier [this message]
2009-02-19 23:36 ` M. Warner Losh
2009-02-19 23:59 ` Anthony Liguori
2009-02-20 0:36 ` M. Warner Losh
2009-02-19 20:45 ` Uri Lublin
2009-02-19 19:37 ` Jamie Lokier
2009-02-19 20:06 ` Anthony Liguori
2009-02-19 19:33 ` Jamie Lokier
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=20090219202849.GE22319@shareable.org \
--to=jamie@shareable.org \
--cc=qemu-devel@nongnu.org \
--cc=uril@redhat.com \
/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).