From: Sasha Levin <levinsasha928@gmail.com>
To: "Lan, Tianyu" <tianyu.lan@intel.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
"penberg@kernel.org" <penberg@kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"asias.hejun@gmail.com" <asias.hejun@gmail.com>,
"prasadjoshi124@gmail.com" <prasadjoshi124@gmail.com>
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 [thread overview]
Message-ID: <1321770182.3525.2.camel@lappy> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F150690D67CB02@shsmsx502.ccr.corp.intel.com>
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.
next prev parent reply other threads:[~2011-11-20 6:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 8:47 [RFC v2 PATCH] kvm tools, qcow: Add the support for copy-on-write clusters Lan Tianyu
2011-11-18 10:10 ` Kevin Wolf
2011-11-19 2:09 ` Lan, Tianyu
2011-11-19 15:30 ` Lan, Tianyu
2011-11-19 16:26 ` Sasha Levin
2011-11-20 6:14 ` Lan, Tianyu
2011-11-20 6:23 ` Sasha Levin [this message]
2011-11-20 7:03 ` Lan, Tianyu
2011-11-20 10:59 ` Pekka Enberg
2011-11-21 8:30 ` Kevin Wolf
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=1321770182.3525.2.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=asias.hejun@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=penberg@kernel.org \
--cc=prasadjoshi124@gmail.com \
--cc=tianyu.lan@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.