[Qemu-devel] [PATCH 0/7] block: Preallocated truncation for gluster and sheepdog

Max Reitz posted 7 patches 6 years, 2 months ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/20180213130356.8885-1-mreitz@redhat.com
Test checkpatch passed
Test docker-build@min-glib passed
Test docker-mingw@fedora passed
Test docker-quick@centos6 passed
Test ppcbe passed
Test ppcle passed
Test s390x passed
block/gluster.c  | 116 ++++++++++++++++++++++++++++++-------------------------
block/sheepdog.c |  56 +++++++++++++++++----------
2 files changed, 99 insertions(+), 73 deletions(-)
[Qemu-devel] [PATCH 0/7] block: Preallocated truncation for gluster and sheepdog
Posted by Max Reitz 6 years, 2 months ago
As far as I can see, these are the only protocols beside file-posix that
support preallocated creation.  In contrast to file-posix, however, they
have not supported preallocated truncation so far.  This series brings
their truncation code to feature parity with their creation code in this
regard.

Note that I do not have a test setup for either of the two drivers, so I
do not actually know whether this works.  Anyone with a setup is more
than welcome to test this series.


Max Reitz (7):
  gluster: Move glfs_close() to create's clean-up
  gluster: Pull truncation from qemu_gluster_create
  gluster: Query current size in do_truncate()
  gluster: Add preallocated truncation
  sheepdog: Make sd_prealloc() take a BDS
  sheepdog: Pass old and new size to sd_prealloc()
  sheepdog: Allow fully preallocated truncation

 block/gluster.c  | 116 ++++++++++++++++++++++++++++++-------------------------
 block/sheepdog.c |  56 +++++++++++++++++----------
 2 files changed, 99 insertions(+), 73 deletions(-)

-- 
2.14.3


Re: [Qemu-devel] [PATCH 0/7] block: Preallocated truncation for gluster and sheepdog
Posted by Kevin Wolf 6 years, 2 months ago
Am 13.02.2018 um 14:03 hat Max Reitz geschrieben:
> As far as I can see, these are the only protocols beside file-posix that
> support preallocated creation.  In contrast to file-posix, however, they
> have not supported preallocated truncation so far.  This series brings
> their truncation code to feature parity with their creation code in this
> regard.
> 
> Note that I do not have a test setup for either of the two drivers, so I
> do not actually know whether this works.  Anyone with a setup is more
> than welcome to test this series.

Thanks, applied to the block branch.

We'll see if someone screams once this hits master.

Kevin