search for: zero_fua

Tested via: term1$ qemu-nbd -k $PWD/sock -t -f raw -x foo junk --trace=nbd_\* term2$ ./nbdkit -f -v -e bar nbd socket=$PWD/sock export=foo term3$ qemu-io -t none -f raw nbd://localhost:10809/bar --trace=nbd_\* and checking the traces to see that 'w 0 1' vs. 'w -f 0 1' was able to influence whether the FUA flag showed up at the server in term1. Still to go: figure out how to

...is sufficient), then return C<-1>. +Note that C<.flush> can be called both by the client doing an explicit +flush request, and by nbdkit when emulating Forced Unit Access (FUA) +semantics after a write or trim where the plugin did not provide FUA +callbacks (C<.pwrite_fua>, C<.zero_fua>, and C<.trim_fua>). + =head2 C<.trim> int trim (void *handle, uint32_t count, uint64_t offset); @@ -467,6 +522,21 @@ If there is an error, C<.trim> should call C<nbdkit_error> with an error message, and C<nbdkit_set_error> to record an appropriate error (unle...

...urn C<-1>. > > +Note that C<.flush> can be called both by the client doing an explicit > +flush request, and by nbdkit when emulating Forced Unit Access (FUA) > +semantics after a write or trim where the plugin did not provide FUA > +callbacks (C<.pwrite_fua>, C<.zero_fua>, and C<.trim_fua>). > + > =head2 C<.trim> > > int trim (void *handle, uint32_t count, uint64_t offset); > @@ -467,6 +522,21 @@ If there is an error, C<.trim> should call > C<nbdkit_error> with an > error message, and C<nbdkit_set_error> to...

A combination of the work that both Rich and I have been doing lately, where filters use only the new API with flags on every command that the client can send over the wire (we can then add support for more flags in nbdkit without having to add new callbacks, as NBD adds more flags upstream). Eric Blake (4): protocol: Split flags from cmd field in requests backend: Pass flags argument through