From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] add file: migration support (r2)
Date: Thu, 13 Nov 2008 18:39:53 +0000 [thread overview]
Message-ID: <20081113183953.GA29026@shareable.org> (raw)
In-Reply-To: <gfhq8c$pjm$1@ger.gmane.org>
Charles Duffy wrote:
> documents the limitations of O_NONBLOCK on Linux with local
> filesystem access.
That's not a Linux limitation.
All OSes ignore O_NONBLOCK for filesystem accesses, including remote
filesystems. This is a POSIX thing.
The reason is that there's no way to select() on a file. (You'd need
to select() on readiness to read/write a specific byte range anyway,
so the interface doesn't work.)
The nearest equivalent to select() on file I/O is AIO, which is
probably what should be used if migration file I/O is blocking QEMU.
-- Jamie
next prev parent reply other threads:[~2008-11-13 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 18:04 [Qemu-devel] [PATCH] add file: migration support (r2) Charles Duffy
2008-11-13 18:39 ` Jamie Lokier [this message]
2008-11-13 18:44 ` Paul Brook
2008-11-13 18:49 ` Anthony Liguori
2008-11-14 3:33 ` Jamie Lokier
2008-11-14 3:49 ` Paul Brook
2008-11-18 3:04 ` Jamie Lokier
2008-11-18 12:57 ` Paul Brook
2008-11-18 14:26 ` 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=20081113183953.GA29026@shareable.org \
--to=jamie@shareable.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).