Displaying 2 results from an estimated 2 matches for "get_concurrent_writer".
Did you mean:
set_concurrent_writer
2019 Jun 03
1
Re: [PATCH libnbd discussion only 4/5] api: Implement concurrent writer.
...n intentional.
> + */
> + if (h->writer != NULL) {
> + set_error (EINVAL, "concurrent writer was already set for this handle");
> + return -1;
> + }
> +
> + h->writer = writer;
> + h->writer_data = data;
> + return 0;
> +}
Is it worth a get_concurrent_writer()? Not strictly necessary, though.
> +
> +int
> +nbd_unlocked_concurrent_writer_error (struct nbd_handle *h, int err)
> +{
> + if (err != 0) {
> + set_error (EINVAL, "concurrent writer error parameter must be non-zero");
> + return -1;
> + }
> +
> +...
2019 Jun 03
10
[PATCH libnbd discussion only 0/5] api: Implement concurrent writer.
This works, but there's no time saving and I'm still investigating
whether it does what I think it does. Nevertheless I thought I would
post it because it (probably) implements the idea I had last night
outlined in:
https://www.redhat.com/archives/libguestfs/2019-June/msg00010.html
The meat of the change is patch 4. Patch 5 is an example which I
would probably fold into patch 4 for