From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Mjc9q-0008Vn-UX
	for qemu-devel@nongnu.org; Fri, 04 Sep 2009 13:01:07 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Mjc9l-0008Sl-Vr
	for qemu-devel@nongnu.org; Fri, 04 Sep 2009 13:01:06 -0400
Received: from [199.232.76.173] (port=39712 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Mjc9l-0008SW-Iu
	for qemu-devel@nongnu.org; Fri, 04 Sep 2009 13:01:01 -0400
Received: from verein.lst.de ([213.95.11.210]:36000)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60)
	(envelope-from <hch@lst.de>) id 1Mjc9i-0007qr-U7
	for qemu-devel@nongnu.org; Fri, 04 Sep 2009 13:00:59 -0400
Date: Fri, 4 Sep 2009 19:00:52 +0200
From: Christoph Hellwig <hch@lst.de>
Message-ID: <20090904170052.GA22640@lst.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [Qemu-devel] [PATCH 0/5] data integrity fixes V2
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

respin of the data integrity series.  Major changes since the first
version:

 - split ide use of bdrv_aio_flush into a separate patch
 - added a qemu_fdatasync helper that falls back to fsync if needed
 - enable barriers for data=writeback

The last might be a bit controversial, but I can't find a workload where
it really causes major regressions.  And then you can still mount your
guest filesystems with barrier=0/nobarrier (like the ext3 default) and
this code won't ever be called.