[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [PATCH 0/5] data integrity fixes V2
From: |
Christoph Hellwig |
Subject: |
[Qemu-devel] [PATCH 0/5] data integrity fixes V2 |
Date: |
Fri, 4 Sep 2009 19:00:52 +0200 |
User-agent: |
Mutt/1.3.28i |
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.
- [Qemu-devel] [PATCH 0/5] data integrity fixes V2,
Christoph Hellwig <=
- [Qemu-devel] [PATCH 1/5] block: add enable_write_cache flag, Christoph Hellwig, 2009/09/04
- [Qemu-devel] [PATCH 2/5] block: use fdatasync instead of fsync if possible, Christoph Hellwig, 2009/09/04
- [Qemu-devel] [PATCH 3/5] block: add aio_flush operation, Christoph Hellwig, 2009/09/04
- [Qemu-devel] [PATCH 4/5] ide: use bdrv_aio_flush, Christoph Hellwig, 2009/09/04
- [Qemu-devel] [PATCH 5/5] virtio-blk: add volatile writecache feature, Christoph Hellwig, 2009/09/04