Displaying 5 results from an estimated 5 matches for "vixdisklib_flush".
2019 Apr 29
0
[nbdkit PATCH 1/3] vddk: Use a separate handle for single-link=true
...ink");
+ VixDiskLib_Close (h->handle_single_link);
+ }
DEBUG_CALL ("VixDiskLib_Disconnect", "connection");
VixDiskLib_Disconnect (h->connection);
free (h);
@@ -698,7 +716,7 @@ vddk_flush (void *handle, uint32_t flags)
return 0;
DEBUG_CALL ("VixDiskLib_Flush", "handle");
- err = VixDiskLib_Flush (h->handle);
+ err = VixDiskLib_Flush (single_link ? h->handle_single_link : h->handle);
if (err != VIX_OK) {
VDDK_ERROR (err, "VixDiskLib_Flush");
return -1;
@@ -730,7 +748,7 @@ vddk_can_extents (void *handle)...
2019 Apr 29
5
[nbdkit PATCH 0/3] Fix data integrity in vddk plugin
Couple of fixes to return correct data and one nice-to-have clean-up which is not needed. I just find it nicer to read.
Martin Kletzander (3):
vddk: Use a separate handle for single-link=true
vddk: Do not report hole extents to be zero with single-link=true
vddk: Eliminate one needless goto
plugins/vddk/vddk.c | 48 +++++++++++++++++++++++++++++++++------------
1 file changed, 36
2020 Aug 06
5
[PATCH nbdkit NOT WORKING 0/2] vddk: Relax threading model.
I believe this roughly implements Nir's proposal here:
https://www.redhat.com/archives/libguestfs/2020-August/msg00028.html
Unfortunately it doesn't work for me. It actually slows things down
quite a lot, for reasons I don't understand. Note the adjustment of
the pool-max parameter and how it affects the total time. The results
are quite reproducible.
$ ./nbdkit -r -U - vddk
2020 Aug 06
0
[PATCH nbdkit 2/2] vddk: Relax thread model to PARALLEL and implement a disk handle pool.
...k_handle *h = handle;
+ struct handle *h = handle;
+ GET_VDDK_HANDLE_FOR_CURRENT_SCOPE (h, vddk_handle);
VixError err;
/* The Flush call was not available in VDDK < 6.0 so this is simply
@@ -771,7 +882,7 @@ vddk_flush (void *handle, uint32_t flags)
return 0;
DEBUG_CALL ("VixDiskLib_Flush", "handle");
- err = VixDiskLib_Flush (h->handle);
+ err = VixDiskLib_Flush (vddk_handle);
if (err != VIX_OK) {
VDDK_ERROR (err, "VixDiskLib_Flush");
return -1;
@@ -783,7 +894,8 @@ vddk_flush (void *handle, uint32_t flags)
static int
vddk_can_extents (vo...
2020 Aug 06
3
Re: [PATCH nbdkit 2/2] vddk: Relax thread model to PARALLEL and implement a disk handle pool.
...le *h = handle;
> + GET_VDDK_HANDLE_FOR_CURRENT_SCOPE (h, vddk_handle);
> VixError err;
>
> /* The Flush call was not available in VDDK < 6.0 so this is simply
> @@ -771,7 +882,7 @@ vddk_flush (void *handle, uint32_t flags)
> return 0;
>
> DEBUG_CALL ("VixDiskLib_Flush", "handle");
> - err = VixDiskLib_Flush (h->handle);
> + err = VixDiskLib_Flush (vddk_handle);
> if (err != VIX_OK) {
> VDDK_ERROR (err, "VixDiskLib_Flush");
> return -1;
> @@ -783,7 +894,8 @@ vddk_flush (void *handle, uint32_t flags)
>...