From: Daniel H Barboza <danielhb@linux.vnet.ibm.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Qemu Devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] block.curl: adding 'curltimeout' option
Date: Wed, 13 Aug 2014 09:39:17 -0300 [thread overview]
Message-ID: <53EB5C75.3020909@linux.vnet.ibm.com> (raw)
In-Reply-To: <871tsk698v.fsf@blackfin.pond.sub.org>
On 08/13/2014 06:15 AM, Markus Armbruster wrote:
> Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com> writes:
>
>> The curl hardcoded timeout (5 seconds) sometimes is not long
>> enough depending on the remote server configuration and network
>> traffic. The user should be able to set how much long he is
>> willing to wait for the connection.
>>
>> Adding a new option to set this timeout gives the user this
>> flexibility. The previous default timeout of 5 seconds will be
>> used if this option is not present.
>>
>> Signed-off-by: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>
>> ---
>> block/curl.c | 13 ++++++++++++-
>> qemu-options.hx | 10 ++++++++--
>> 2 files changed, 20 insertions(+), 3 deletions(-)
>>
>> diff --git a/block/curl.c b/block/curl.c
>> index 79ff2f1..a9e43f1 100644
>> --- a/block/curl.c
>> +++ b/block/curl.c
>> @@ -63,6 +63,7 @@ static CURLMcode __curl_multi_socket_action(CURLM *multi_handle,
>> #define CURL_NUM_ACB 8
>> #define SECTOR_SIZE 512
>> #define READ_AHEAD_DEFAULT (256 * 1024)
>> +#define CURL_TIMEOUT_DEFAULT 5
>>
>> #define FIND_RET_NONE 0
>> #define FIND_RET_OK 1
>> @@ -71,6 +72,7 @@ static CURLMcode __curl_multi_socket_action(CURLM *multi_handle,
>> #define CURL_BLOCK_OPT_URL "url"
>> #define CURL_BLOCK_OPT_READAHEAD "readahead"
>> #define CURL_BLOCK_OPT_SSLVERIFY "sslverify"
>> +#define CURL_BLOCK_OPT_TIMEOUT "curltimeout"
> To what could this timeout apply other than Curl?
>
> If nothing, then just "timeout", please.
>
> Else, "curl-timeout".
I will investigate a little to check if there are any option called
"timeout" used elsewhere. If not, I see no issues rename this option to
"timeout".
Thanks!
>>
>> struct BDRVCURLState;
>>
>> @@ -109,6 +111,7 @@ typedef struct BDRVCURLState {
>> char *url;
>> size_t readahead_size;
>> bool sslverify;
>> + int curltimeout;
>> bool accept_range;
>> AioContext *aio_context;
>> } BDRVCURLState;
> Likewise: either timeout, or curl_timeout.
>
> [...]
>
next prev parent reply other threads:[~2014-08-13 12:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 14:35 [Qemu-devel] [PATCH] block.curl: adding 'curltimeout' option Daniel Henrique Barboza
2014-08-12 15:36 ` Eric Blake
2014-08-12 16:04 ` Daniel H Barboza
2014-08-13 9:15 ` Markus Armbruster
2014-08-13 12:39 ` Daniel H Barboza [this message]
2014-08-13 13:28 ` Daniel H Barboza
2014-08-13 14:07 ` Markus Armbruster
2014-08-13 14:17 ` 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=53EB5C75.3020909@linux.vnet.ibm.com \
--to=danielhb@linux.vnet.ibm.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--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.