From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1L0h6o-0000DV-9Q
	for qemu-devel@nongnu.org; Thu, 13 Nov 2008 13:40:02 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1L0h6m-0000C3-7N
	for qemu-devel@nongnu.org; Thu, 13 Nov 2008 13:40:01 -0500
Received: from [199.232.76.173] (port=58412 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1L0h6l-0000Bt-RL
	for qemu-devel@nongnu.org; Thu, 13 Nov 2008 13:39:59 -0500
Received: from mail2.shareable.org ([80.68.89.115]:43331)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <jamie@shareable.org>) id 1L0h6l-0004xO-DV
	for qemu-devel@nongnu.org; Thu, 13 Nov 2008 13:39:59 -0500
Received: from jamie by mail2.shareable.org with local (Exim 4.63)
	(envelope-from <jamie@shareable.org>) id 1L0h6f-0007aB-MN
	for qemu-devel@nongnu.org; Thu, 13 Nov 2008 18:39:53 +0000
Date: Thu, 13 Nov 2008 18:39:53 +0000
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] [PATCH] add file: migration support (r2)
Message-ID: <20081113183953.GA29026@shareable.org>
References: <gfhq8c$pjm$1@ger.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <gfhq8c$pjm$1@ger.gmane.org>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.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