data integrity fixes V2
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | block: add enable_write_cache flagblock.c block.h block_int.h +2 more | +27 | 0 replies | |
| 2/5 | block: use fdatasync instead of fsync if possibleblock/ block/ cutils.c +1 more | +19 | 0 replies | |
| 3/5 | block: add aio_flush operationblock.c block.h block/ +3 more | +80 | 0 replies | |
| 4/5 | ide: use bdrv_aio_flushhw/ | +13 | 0 replies | |
| 5/5 | virtio-blk: add volatile writecache featurehw/ hw/ | +27 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Qemu-devel] [PATCH 0/5] data integrity fixes V2
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.