Add a second bool argument to H5F_vfd_swmr_writer_end_of_tick() that

tells whether the call may wait for the reader tick to catch up.

Add stub routines vfd_swmr_writer_may_increase_tick_to() and
vfd_swmr_reader_did_increase_tick_to() for tests---e.g.,
vfd_swmr_zoo_writer/_reader---to use to coordinate their tick numbers.

vfd_swmr_writer_may_increase_tick_to(new_tick, wait_for_reader) returns
true if the writer may increase its tick number to `new_tick` without
overrunning the reader.

A reader uses vfd_swmr_reader_did_increase_tick_to() to tell a writer
that its tick number has increased.

1 files changed, 1 insertions, 1 deletions

diff --git a/src/H5F.c b/src/H5F.c
index 144ffbe..70c0278 100644
--- a/src/H5F.c
+++ b/src/H5F.c
@@ -2046,7 +2046,7 @@ H5Fvfd_swmr_end_tick(hid_t file_id)
         HGOTO_ERROR(H5E_FILE, H5E_BADVALUE, FAIL, "must have VFD SWMR configured for this public routine")
 
     /* ??Trigger end of tick processing later */
-    H5F_vfd_swmr_writer_end_of_tick(file);
+    H5F_vfd_swmr_writer_end_of_tick(file, true);
 
 done:
     FUNC_LEAVE_API(ret_value)