From 5da14da22c1e26aff24baf41fb2ae0f2832acae1 Mon Sep 17 00:00:00 2001 From: "Richard W.M. Jones" Date: Sat, 27 Nov 2021 16:44:41 +0000 Subject: [PATCH] vddk: Drop obsolete documentation related to thread model Since commit 1eecf15fc3 ("vddk: Implement parallel thread model") we have implemented a parallel thread model in this plugin, and thread handling is believed to be safe and in conformity with the VDDK documentation. Remove obsolete documentation contradicting this. Reported-by: Ming Xie Fixes: commit 1eecf15fc3d8ea253ccec4f5883fdbb9aa6f8c2b (cherry picked from commit 370ecb711c23f9143c933e13468e11d688d0d651) --- plugins/vddk/nbdkit-vddk-plugin.pod | 8 -------- 1 file changed, 8 deletions(-) diff --git a/plugins/vddk/nbdkit-vddk-plugin.pod b/plugins/vddk/nbdkit-vddk-plugin.pod index ce82a734..acec0bd2 100644 --- a/plugins/vddk/nbdkit-vddk-plugin.pod +++ b/plugins/vddk/nbdkit-vddk-plugin.pod @@ -452,14 +452,6 @@ sector boundaries. This is because the VDDK Read and Write APIs only take sector numbers. If your client needs finer granularity, you can use L with the setting C. -=head2 Threads - -Handling threads in the VDDK API is complex and does not map well to -any of the thread models offered by nbdkit (see -L). The plugin uses the nbdkit -C model, but technically even this is not -completely safe. This is a subject of future work. - =head2 Out of memory errors In the verbose log you may see errors like: -- 2.31.1