Displaying 3 results from an estimated 3 matches for "3561,6".
Did you mean:
356,6
2019 Jun 18
0
[libnbd RFC PATCH 9/8] wip: generator: Add ReadStatus enum type
...s a tuple of different\n";
pr " * lengths for the different socket types.\n";
@@ -3537,6 +3555,7 @@ let print_python_binding name { args; ret } =
| Int64 _
| Opaque _
| Path _
+ | ReadStatus _
| SockAddrAndLen _
| String _
| StringList _
@@ -3561,6 +3580,7 @@ let print_python_binding name { args; ret } =
| Int64 n -> pr " \"L\""
| Opaque _ -> pr " \"O\""
| Path n -> pr " \"O&\""
+ | ReadStatus n -> pr " XXX4"
| SockAddrAndLen (n, _)...
2019 Jun 20
1
Re: [libnbd RFC PATCH 9/8] wip: generator: Add ReadStatus enum type
...uot; * lengths for the different socket types.\n";
> @@ -3537,6 +3555,7 @@ let print_python_binding name { args; ret } =
> | Int64 _
> | Opaque _
> | Path _
> + | ReadStatus _
> | SockAddrAndLen _
> | String _
> | StringList _
> @@ -3561,6 +3580,7 @@ let print_python_binding name { args; ret } =
> | Int64 n -> pr " \"L\""
> | Opaque _ -> pr " \"O\""
> | Path n -> pr " \"O&\""
> + | ReadStatus n -> pr " XXX4"
>...
2019 Jun 18
17
[libnbd PATCH 0/8] Add nbd_pread_callback
I've mentioned this topic before (in fact, the idea of adding
NBD_CMD_FLAG_DF was first mentioned at [1]), but finally finished
enough of an implementation to feel confident in posting it.
I'd still like to add something under examples/ that uses the new API
to implement strict checking of a server's structured replies read
implementation (ensure that a server never sends data after