RE: [RFC v2 PATCH] kvm tools, qcow: Add the support for copy-on-write clusters

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Yeah. That will make the work quite simple.
After testing, fdatasync is better than fsync.

-----Original Message-----
From: Sasha Levin [mailto:levinsasha928@xxxxxxxxx] 
Sent: Sunday, November 20, 2011 2:23 PM
To: Lan, Tianyu
Cc: Kevin Wolf; penberg@xxxxxxxxxx; kvm@xxxxxxxxxxxxxxx; asias.hejun@xxxxxxxxx; prasadjoshi124@xxxxxxxxx
Subject: RE: [RFC v2 PATCH] kvm tools, qcow: Add the support for copy-on-write clusters

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@xxxxxxxxx] 
> Sent: Sunday, November 20, 2011 12:27 AM
> To: Lan, Tianyu
> Cc: Kevin Wolf; penberg@xxxxxxxxxx; kvm@xxxxxxxxxxxxxxx; asias.hejun@xxxxxxxxx; prasadjoshi124@xxxxxxxxx
> 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.

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux