All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@kernel.org>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: "Lan, Tianyu" <tianyu.lan@intel.com>,
	Kevin Wolf <kwolf@redhat.com>,
	"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 12:59:31 +0200	[thread overview]
Message-ID: <1321786772.1428.116.camel@jaguar> (raw)
In-Reply-To: <1321770182.3525.2.camel@lappy>

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?

On Sun, 2011-11-20 at 08:23 +0200, Sasha Levin wrote:
> 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?

No, lets not do that. It's easier to improve the performance of correct
code that doesn't use O_SYNC.

			Pekka


  parent reply	other threads:[~2011-11-20 10:59 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
2011-11-20  7:03             ` Lan, Tianyu
2011-11-20 10:59             ` Pekka Enberg [this message]
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=1321786772.1428.116.camel@jaguar \
    --to=penberg@kernel.org \
    --cc=asias.hejun@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@redhat.com \
    --cc=levinsasha928@gmail.com \
    --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.