From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:37461) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SBT7w-0005WS-K0 for qemu-devel@nongnu.org; Sat, 24 Mar 2012 11:43:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SBT7u-0000qR-VL for qemu-devel@nongnu.org; Sat, 24 Mar 2012 11:43:36 -0400 Received: from verein.lst.de ([213.95.11.211]:52387 helo=newverein.lst.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SBT7u-0000qH-P8 for qemu-devel@nongnu.org; Sat, 24 Mar 2012 11:43:34 -0400 Date: Sat, 24 Mar 2012 16:43:33 +0100 From: Christoph Hellwig Message-ID: <20120324154333.GH13014@lst.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH 1/5] block: Virtual Bridges VERDE GOW disk image format documentation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Leonardo E. Reiter" Cc: Stefan Hajnoczi , QEMU Developers Mailing List On Sun, Mar 11, 2012 at 04:03:01PM -0500, Leonardo E. Reiter wrote: > indeed mmap() is used in the code. This is unfortunate that it cannot be > used. It's a really high performance way to achieve what we want here, and > very safe for the use-case. Of course the only medium we support in the > product that uses this is filesystem, so I see your point. I'll see about > using some different mechanism. using shared writeable mmaps for disk I/O is never a safe approach, as there is no way for sane error handling.