From: Eric Blake <eblake@redhat.com>
To: Fam Zheng <famz@redhat.com>, "Richard W.M. Jones" <rjones@redhat.com>
Cc: kwolf@redhat.com, danielhb@linux.vnet.ibm.com,
qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] curl: Add override_accept_ranges flag to force sending range requests.
Date: Tue, 26 Aug 2014 20:57:30 -0600 [thread overview]
Message-ID: <53FD491A.9060303@redhat.com> (raw)
In-Reply-To: <20140827023845.GA2977@T430.nay.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
On 08/26/2014 08:38 PM, Fam Zheng wrote:
> On Tue, 08/26 21:48, Richard W.M. Jones wrote:
>> Some servers (notably VMware ESX) accept range requests, but don't
>> send back the Accept-Ranges: bytes header in their initial response.
>>
>> For these servers you can set override_accept_ranges to 'on' which
>> forces this block driver to send range requests anyway.
Is this a case where we should be naming with dashes instead of
underscores, as in override-accept-ranges?
>> @@ -489,6 +490,11 @@ static QemuOptsList runtime_opts = {
>> .type = QEMU_OPT_BOOL,
>> .help = "Verify SSL certificate"
>> },
>> + {
>> + .name = CURL_BLOCK_OPT_OVERRIDE_ACCEPT_RANGES,
>> + .type = QEMU_OPT_BOOL,
>> + .help = "Server accepts range requests"
>> + },
It would be nice for someone to finally port the QAPI counterpart
(BlockdevOptions) so that curl devices can be hotplugged via
blockdev-add. But I guess that's a separate patch.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]
next prev parent reply other threads:[~2014-08-27 2:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 20:48 [Qemu-devel] [PATCH] curl: Add override_accept_ranges flag to force sending range Richard W.M. Jones
2014-08-26 20:48 ` [Qemu-devel] [PATCH] curl: Add override_accept_ranges flag to force sending range requests Richard W.M. Jones
2014-08-27 2:38 ` Fam Zheng
2014-08-27 2:57 ` Eric Blake [this message]
2014-08-27 6:37 ` Markus Armbruster
2014-08-27 10:16 ` Richard W.M. Jones
2014-08-27 7:57 ` Richard W.M. Jones
2014-08-27 12:51 ` Daniel H Barboza
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=53FD491A.9060303@redhat.com \
--to=eblake@redhat.com \
--cc=danielhb@linux.vnet.ibm.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).