From: David Edmondson <dme@dme.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <fam@euphon.net>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
Max Reitz <mreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [RFC PATCH 5/9] block/curl: Allow the blocksize to be specified by the user
Date: Mon, 24 Aug 2020 15:21:36 +0100 [thread overview]
Message-ID: <m2pn7g15vz.fsf@dme.org> (raw)
In-Reply-To: <87a6ykqizn.fsf@dusky.pond.sub.org>
On Monday, 2020-08-24 at 15:19:24 +02, Markus Armbruster wrote:
> David Edmondson <david.edmondson@oracle.com> writes:
>
>> Rather than a fixed 256kB blocksize, allow the user to specify the
>> size used. It must be a non-zero power of two, defaulting to 256kB.
>
> Nitpick: any power of two is non-zero. Scratch "non-zero".
Indeed.
>> Signed-off-by: David Edmondson <david.edmondson@oracle.com>
>> ---
> [...]
>> diff --git a/docs/system/device-url-syntax.rst.inc b/docs/system/device-url-syntax.rst.inc
>> index bc38b9df38..ee504ee41a 100644
>> --- a/docs/system/device-url-syntax.rst.inc
>> +++ b/docs/system/device-url-syntax.rst.inc
>> @@ -194,6 +194,13 @@ These are specified using a special URL syntax.
>> Add an offset, in bytes, to all range requests sent to the
>> remote server.
>>
>> + ``blocksize``
>> + The size of all IO requests sent to the remote server. This
>> + value may optionally have the suffix 'T', 'G', 'M', 'K', 'k' or
>> + 'b'. If it does not have a suffix, it will be assumed to be in
>> + bytes. The value must be a non-zero power of two. It defaults
>> + to 256kB.
>> +
>> Note that when passing options to qemu explicitly, ``driver`` is the
>> value of <protocol>.
>>
>> diff --git a/qapi/block-core.json b/qapi/block-core.json
>> index d6f5e91cc3..cd16197e1e 100644
>> --- a/qapi/block-core.json
>> +++ b/qapi/block-core.json
>> @@ -3764,10 +3764,14 @@
>> # @proxy-password-secret: ID of a QCryptoSecret object providing a password
>> # for proxy authentication (defaults to no password)
>> #
>> +# @blocksize: Size of all IO requests sent to the remote server; must
>> +# be a non-zero power of two (defaults to 1 256kB)
>
> Scratch "non-zero".
>
> "(defaults to 1 256kB)" confuses me. Do you mean "(defaults to 256kB)"?
Yes, thanks for catching it.
> Please add "(since 5.2)".
Will do.
>> +#
>> # Since: 2.9
>> ##
>> { 'struct': 'BlockdevOptionsCurlBase',
>> 'data': { 'url': 'str',
>> + '*blocksize': 'int',
>
> Should we use 'size' rather than 'int'?
Yes.
>> '*timeout': 'int',
>> '*username': 'str',
>> '*password-secret': 'str',
dme.
--
But are you safe Miss Gradenko?
next prev parent reply other threads:[~2020-08-24 14:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 11:08 [RFC PATCH 0/9] block/curl: Add caching of data downloaded from the remote server David Edmondson
2020-08-18 11:08 ` [RFC PATCH 1/9] block/curl: Add an 'offset' parameter, affecting all range requests David Edmondson
2020-08-18 11:08 ` [RFC PATCH 2/9] block/curl: Remove readahead support David Edmondson
2020-08-18 11:08 ` [RFC PATCH 3/9] block/curl: Tracing David Edmondson
2020-08-18 11:08 ` [RFC PATCH 4/9] block/curl: Perform IO in fixed size chunks David Edmondson
2020-08-18 11:08 ` [RFC PATCH 5/9] block/curl: Allow the blocksize to be specified by the user David Edmondson
2020-08-24 13:19 ` Markus Armbruster
2020-08-24 14:21 ` David Edmondson [this message]
2020-08-18 11:08 ` [RFC PATCH 6/9] block/curl: Cache downloaded blocks David Edmondson
2020-08-18 11:08 ` [RFC PATCH 7/9] block/curl: Allow the user to control the number of cache blocks David Edmondson
2020-08-18 11:08 ` [RFC PATCH 8/9] block/curl: Allow 16 sockets/ACB David Edmondson
2020-08-18 11:08 ` [RFC PATCH 9/9] block/curl: Add readahead support David Edmondson
2020-08-19 14:11 ` [RFC PATCH 0/9] block/curl: Add caching of data downloaded from the remote server Stefan Hajnoczi
2020-08-19 14:19 ` David Edmondson
2020-08-25 10:03 ` Max Reitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2pn7g15vz.fsf@dme.org \
--to=dme@dme.org \
--cc=armbru@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.