Displaying 5 results from an estimated 5 matches for "nbd_cmd_flag_payload_len".
2023 Mar 03
1
[PATCH v2 5/6] spec: Introduce NBD_FLAG_BLOCK_STATUS_PAYLOAD
...> > will be faster than a regular write). Clients MUST NOT set the
> > `NBD_CMD_FLAG_FAST_ZERO` request flag unless this transmission flag
> > is set.
> > +- bit 12, `NBD_FLAG_BLOCK_STATUS_PAYLOAD`: Indicates that the server
> > + understands the use of the `NBD_CMD_FLAG_PAYLOAD_LEN` flag to
> > + `NBD_CMD_BLOCK_STATUS` to allow the client to request that the
> > + server filters its response to a specific subset of negotiated
> > + metacontext ids passed in via a client payload, rather than the
> > + default of replying to all metacontext ids. Serv...
2023 May 30
2
[libnbd PATCH v3 04/22] states: Prepare to send 64-bit requests
On Tue, May 30, 2023 at 04:06:32PM +0200, Laszlo Ersek wrote:
> On 5/25/23 15:00, Eric Blake wrote:
> > Support sending 64-bit requests if extended headers were negotiated.
> > This includes setting NBD_CMD_FLAG_PAYLOAD_LEN any time we send an
> > extended NBD_CMD_WRITE; this is such a fundamental part of the
> > protocol that for now it is easier to silently ignore whatever value
> > the user passes in for that bit in the flags parameter of nbd_pwrite
> > regardless of the current settings in...
2022 Nov 14
2
[PATCH v2 3/6] spec: Add NBD_OPT_EXTENDED_HEADERS
...s:
C: 32 bits, 0x25609513, magic (`NBD_REQUEST_MAGIC`)
C: 16 bits, command flags
@@ -354,19 +376,54 @@ C: 64 bits, offset (unsigned)
C: 32 bits, length (unsigned)
C: (*length* bytes of data if the request is of type `NBD_CMD_WRITE`)
+In the compact style, the client MUST NOT use the
+`NBD_CMD_FLAG_PAYLOAD_LEN` flag; and the only command where *length*
+represents payload length instead of effect length is `NBD_CMD_WRITE`.
+
+If negotiation agreed on extended transactions with
+`NBD_OPT_EXTENDED_HEADERS`, the client instead uses extended requests:
+
+C: 32 bits, 0x21e41c71, magic (`NBD_EXTENDED_REQUEST_M...
2023 Apr 13
6
[PATCH v3 0/6] NBD 64-bit extensions (spec only)
v2 was here:
https://lists.debian.org/nbd/2022/11/msg00030.html
The bulk of the changes since then are:
- forbid NBD_OPT_EXPORT_NAME once extended headers are negotiated (Wouter)
- consistently use 'maximum payload', rather than a haphazard mix of
'maximum block payload' (Vladimir)
At this point, I want to make sure we are happy with the spec before
re-posting patches for
2023 Mar 03
1
[PATCH v2 3/6] spec: Add NBD_OPT_EXTENDED_HEADERS
...server replies with the following, or with an error permitted
> > + elsewhere in this document:
> > +
> > + - `NBD_REP_ACK`: Extended headers have been negotiated; the client
> > + MUST use the 32-byte extended request header, with proper use of
> > + `NBD_CMD_FLAG_PAYLOAD_LEN` for all commands sending a payload;
> > + and the server MUST use the 32-byte extended reply header.
> > + - For backwards compatibility, clients SHOULD be prepared to also
> > + handle `NBD_REP_ERR_UNSUP`; in this case, only the compact
> > + transmission...