Displaying 3 results from an estimated 3 matches for "noextents_init_zero".
2020 Feb 10
2
[nbdkit PATCH 03/10] filters: Wire up filter support for NBD_INFO_INIT_STATE
...d that the following conditions are
@@ -41,10 +41,26 @@ noextents_can_extents (struct nbdkit_next_ops *next_ops, void *nxdata,
return 0;
}
+static int
+noextents_init_sparse (struct nbdkit_next_ops *next_ops, void *nxdata,
+ void *handle)
+{
+ return 0;
+}
+
+static int
+noextents_init_zero (struct nbdkit_next_ops *next_ops, void *nxdata,
+ void *handle)
+{
+ return 0;
+}
+
static struct nbdkit_filter filter = {
.name = "noextents",
.longname = "nbdkit noextents filter",
.can_extents = noextents_can_extents...
2020 Feb 11
0
Re: [nbdkit PATCH 03/10] filters: Wire up filter support for NBD_INFO_INIT_STATE
...tents_can_extents (struct nbdkit_next_ops *next_ops, void *nxdata,
> return 0;
> }
>
> +static int
> +noextents_init_sparse (struct nbdkit_next_ops *next_ops, void *nxdata,
> + void *handle)
> +{
> + return 0;
> +}
> +
> +static int
> +noextents_init_zero (struct nbdkit_next_ops *next_ops, void *nxdata,
> + void *handle)
> +{
> + return 0;
> +}
Is this true? If so it could at least be worth a comment in the code
about why because I'm not clear about it.
Rich.
--
Richard Jones, Virtualization Group, Red Hat h...
2020 Feb 10
17
Cross-project NBD extension proposal: NBD_INFO_INIT_STATE
I will be following up to this email with four separate threads each
addressed to the appropriate single list, with proposed changes to:
- the NBD protocol
- qemu: both server and client
- libnbd: client
- nbdkit: server
The feature in question adds a new optional NBD_INFO_ packet to the
NBD_OPT_GO portion of handshake, adding up to 16 bits of information
that the server can advertise to the