NBD spec changes for 64-bit extensions
Get series with b4
b4 am [email protected]Versions newest first
- v2 Latest6 patches 17 repliesIn review
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | spec: Recommend cap on NBD_REPLY_TYPE_BLOCK_STATUS lengthdoc/ | +31 | 5 replies | |
| 2/6 | spec: Tweak description of maximum block sizedoc/ | +73 | 5 replies | |
| 3/6 | spec: Add NBD_OPT_EXTENDED_HEADERSdoc/ | +358 | 4 replies | |
| 4/6 | spec: Allow 64-bit block status resultsdoc/ | +49 | 0 replies | |
| 5/6 | spec: Introduce NBD_FLAG_BLOCK_STATUS_PAYLOADdoc/ | +49 | 3 replies | |
| 6/6 | RFC: spec: Introduce NBD_REPLY_TYPE_OFFSET_HOLE_EXTdoc/ | +40 | 0 replies |
Reviews trailers per patch
1 of 6 patches has a Reviewed-by or Acked-by.
| Patch | Vladimir Sementsov-Ogievskiy |
|---|---|
| 1/6 | R-b |
| 2/6 | |
| 3/6 | |
| 4/6 | |
| 5/6 | |
| 6/6 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v2 0/6] NBD spec changes for 64-bit extensions
This is the NBD spec series; there are matching qemu and libnbd patches that implement the changes in this series. I'm happy to drop the RFC patches from all three, but wanted the conversation on whether it makes sense to have 64-bit holes during NBD_CMD_READ first (it would make more sense if we had a way for a client and server to agree on a single-transaction buffer limit much larger than 32M).
Eric Blake (6):
spec: Recommend cap on NBD_REPLY_TYPE_BLOCK_STATUS length
spec: Tweak description of maximum block size
spec: Add NBD_OPT_EXTENDED_HEADERS
spec: Allow 64-bit block status results
spec: Introduce NBD_FLAG_BLOCK_STATUS_PAYLOAD
RFC: spec: Introduce NBD_REPLY_TYPE_OFFSET_HOLE_EXT
doc/proto.md | 698 ++++++++++++++++++++++++++++++++++++++------------- 1 file changed, 521 insertions(+), 177 deletions(-)
Signature · 1 line
2.38.1