From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Levin Subject: RE: [RFC v2 PATCH] kvm tools, qcow: Add the support for copy-on-write clusters Date: Sun, 20 Nov 2011 08:23:02 +0200 Message-ID: <1321770182.3525.2.camel@lappy> References: <1321606038-29989-1-git-send-email-tianyu.lan@intel.com> <4EC62F14.6090505@redhat.com> <625BA99ED14B2D499DC4E29D8138F1506860C491FF@shsmsx502.ccr.corp.intel.com> <625BA99ED14B2D499DC4E29D8138F1506860C49247@shsmsx502.ccr.corp.intel.com> <1321719998.2974.9.camel@sasha> <625BA99ED14B2D499DC4E29D8138F150690D67CB02@shsmsx502.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Kevin Wolf , "penberg@kernel.org" , "kvm@vger.kernel.org" , "asias.hejun@gmail.com" , "prasadjoshi124@gmail.com" To: "Lan, Tianyu" Return-path: Received: from mail-gy0-f174.google.com ([209.85.160.174]:42217 "EHLO mail-gy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750817Ab1KTGZY (ORCPT ); Sun, 20 Nov 2011 01:25:24 -0500 Received: by ghbz2 with SMTP id z2so1841979ghb.19 for ; Sat, 19 Nov 2011 22:25:23 -0800 (PST) In-Reply-To: <625BA99ED14B2D499DC4E29D8138F150690D67CB02@shsmsx502.ccr.corp.intel.com> Sender: kvm-owner@vger.kernel.org List-ID: On Sun, 2011-11-20 at 14:14 +0800, Lan, Tianyu wrote: > OK. Thx. > But fsync is too slow. I try to find a way to sync a range of file. > Are there any solutions to meet my purpose? fdatasync() is as good as it'll get. tbh, maybe we should just consider opening QCOW images with O_SYNC and just get it over with? > Thanks > Tianyu Lan > > -----Original Message----- > From: Sasha Levin [mailto:levinsasha928@gmail.com] > Sent: Sunday, November 20, 2011 12:27 AM > To: Lan, Tianyu > Cc: Kevin Wolf; penberg@kernel.org; kvm@vger.kernel.org; asias.hejun@gmail.com; prasadjoshi124@gmail.com > Subject: RE: [RFC v2 PATCH] kvm tools, qcow: Add the support for copy-on-write clusters > > On Sat, 2011-11-19 at 23:30 +0800, Lan, Tianyu wrote: > > How about using the sync_file_range to sync the metadata? > > sync_file_range() is only a hint, it doesn't actually assure anything. > -- Sasha.