From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=53077 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OPGGP-0006t3-PX for qemu-devel@nongnu.org; Thu, 17 Jun 2010 10:40:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OPGGO-0000tB-4u for qemu-devel@nongnu.org; Thu, 17 Jun 2010 10:40:17 -0400 Received: from mx1.redhat.com ([209.132.183.28]:49897) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OPGGN-0000sk-Um for qemu-devel@nongnu.org; Thu, 17 Jun 2010 10:40:16 -0400 Message-ID: <4C1A33BA.4030303@redhat.com> Date: Thu, 17 Jun 2010 16:39:54 +0200 From: Kevin Wolf MIME-Version: 1.0 References: <1276776211-11174-1-git-send-email-kwolf@redhat.com> <1276776211-11174-3-git-send-email-kwolf@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [RFC][PATCH 2/2] qcow2: Use bdrv_(p)write_sync for metadata writes List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: qemu-devel@nongnu.org, hch@lst.de Am 17.06.2010 16:19, schrieb Stefan Hajnoczi: > On Thu, Jun 17, 2010 at 1:03 PM, Kevin Wolf wrote: >> Use bdrv_(p)write_sync to ensure metadata integrity in case of a crash. > > Any performance numbers? This change is necessary for correctness but > I wonder what the performance impact is for users. No numbers yet, but as you say we need to do it anyway. It should definitely be better than any other option that I can think of (cache=writethrough or some O_DIRECT|O_DSYNC mode) in that it only hurts performance when metadata is actually changed. As long as we only write guest data, there is no difference. Making it a barrier instead of a flush would probably be better, have you already had a look at this since we talked about it? Kevin