Displaying 5 results from an estimated 5 matches for "block_size_pref".
2023 Oct 08
1
[libnbd PATCH 2/2] info: Show human sizes for block_size values
...10:18:09AM -0500, Eric Blake wrote:
>> Adding a human-readable size for block constraints is useful. For:
>>
>> $ ./run nbdinfo -- [ nbdkit memory \
>> --filter=blocksize-policy blocksize-preferred=32k 1M ] | grep pref
>>
>> this changes pre-patch:
>> block_size_preferred: 32768
>> to post-patch:
>> block_size_preferred: 32768 (32K)
>
> I think info/nbdinfo.pod needs to be updated.
Good catch!
With that:
series
Reviewed-by: Laszlo Ersek <lersek at redhat.com>
>
> Rich.
>
>> Signed-off-by: Eric Blake <eblake at...
2020 Jul 24
0
[libnbd PATCH 3/3] nbdinfo: Expose block size constraints
...fo.pod
index 9761551..d0d20a9 100644
--- a/info/nbdinfo.pod
+++ b/info/nbdinfo.pod
@@ -45,6 +45,9 @@ L<https://github.com/NetworkBlockDevice/nbd/blob/master/doc/uri.md>):
can_multi_conn: true
can_trim: true
can_zero: true
+ block_size_minimum: 1
+ block_size_preferred: 4096
+ block_size_maximum: 33554432
To display only the size in bytes of the NBD export (useful for
scripting) use the I<--size> parameter:
@@ -73,6 +76,9 @@ the I<--json> parameter:
"can_multi_conn": true,
"can_trim": false,...
2023 Oct 06
2
[libnbd PATCH 0/2] Improve nbdinfo display of block constraints
Based on Laszlo's approval of my idea here:
https://listman.redhat.com/archives/libguestfs/2023-September/032661.html
but as I would like to resync human-size.h back to nbdkit, I'm
reluctant to apply patch 1 this until I get Rich's consent to
relicensing (this email serves as my consent for my contribution here):
https://listman.redhat.com/archives/libguestfs/2023-October/032755.html
2020 Jul 24
4
[libnbd PATCH 0/3] Expose server block size constraints
Necessary when writing a client that wants to avoid unnecessary EINVAL
errors from sending unaligned requests.
At some point, we may want to add synchronous convenience API wrappers
that do request splitting or read-modify-write to obey server
constraints while still appearing to the library client as accepting
any possible request. But such a wrapper should only be synchronous
and not copied to
2020 Oct 06
2
[PATCH libnbd] info: Write output atomically.
...("\t%s: %" PRId64 "\n", "block_size_minimum", block_minimum);
+ fprintf (fp, "\t%s: %" PRId64 "\n", "block_size_minimum", block_minimum);
if (block_preferred > 0)
- printf ("\t%s: %" PRId64 "\n", "block_size_preferred", block_preferred);
+ fprintf (fp, "\t%s: %" PRId64 "\n", "block_size_preferred",
+ block_preferred);
if (block_maximum > 0)
- printf ("\t%s: %" PRId64 "\n", "block_size_maximum", block_maximum);
+...