From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] migration: adding migration to/from a file (v2)
Date: Thu, 19 Feb 2009 19:33:24 +0000 [thread overview]
Message-ID: <20090219193324.GA22319@shareable.org> (raw)
In-Reply-To: <499D8564.1070007@redhat.com>
Uri Lublin wrote:
> Your concern in the previous patch was that write() to a regular file might
> block. That's why I'm calling select before calling write. Do you think
> select will mark the fd as writeable but write would still block ?
select() on a regular file _always_ marks the fd as writable. That's
one of the rules of select(). For non-blocking file access you can
only use threads or AIO, or a helper process.
-- Jamie
prev parent reply other threads:[~2009-02-19 19:33 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
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 [this message]
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=20090219193324.GA22319@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).