From: Kevin Wolf <kwolf@redhat.com>
To: Laurent Desnogues <laurent.desnogues@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Matthew Booth <mbooth@redhat.com>
Subject: Re: [Qemu-devel] [PULL 28/31] curl: Remove unnecessary explicit calls to internal event handler
Date: Tue, 6 May 2014 11:56:24 +0200 [thread overview]
Message-ID: <20140506095624.GB3941@noname.str.redhat.com> (raw)
In-Reply-To: <CABoDooP+0uyKPNXGKh0bGjaK1sb8vmLmXZCkjYspfZKTdy37Zg@mail.gmail.com>
Am 06.05.2014 um 11:44 hat Laurent Desnogues geschrieben:
> Hello,
>
> sorry for another late detection of the use of too recent features.
>
> On Wed, Apr 30, 2014 at 8:24 PM, Kevin Wolf <kwolf@redhat.com> wrote:
> > From: Matthew Booth <mbooth@redhat.com>
> >
> > Remove calls to curl_multi_do where the relevant handles are already
> > registered to the event loop.
> >
> > Ensure that we kick off socket handling with CURL_SOCKET_TIMEOUT after
> > adding a new handle.
> >
> > Signed-off-by: Matthew Booth <mbooth@redhat.com>
> > Tested-by: Richard W.M. Jones <rjones@redhat.com>
> > Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> > ---
> > block/curl.c | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/block/curl.c b/block/curl.c
> > index 50bd05f..fd2756e 100644
> > --- a/block/curl.c
> > +++ b/block/curl.c
> > @@ -535,7 +535,6 @@ static int curl_open(BlockDriverState *bs, QDict *options, int flags,
> > curl_multi_setopt(s->multi, CURLMOPT_TIMERDATA, s);
> > curl_multi_setopt(s->multi, CURLMOPT_TIMERFUNCTION, curl_timer_cb);
> > #endif
> > - curl_multi_do(s);
> >
> > qemu_opts_del(opts);
> > return 0;
> > @@ -564,6 +563,7 @@ static const AIOCBInfo curl_aiocb_info = {
> > static void curl_readv_bh_cb(void *p)
> > {
> > CURLState *state;
> > + int running;
> >
> > CURLAIOCB *acb = p;
> > BDRVCURLState *s = acb->common.bs->opaque;
> > @@ -612,8 +612,9 @@ static void curl_readv_bh_cb(void *p)
> > curl_easy_setopt(state->curl, CURLOPT_RANGE, state->range);
> >
> > curl_multi_add_handle(s->multi, state->curl);
> > - curl_multi_do(s);
> >
> > + /* Tell curl it needs to kick things off */
> > + curl_multi_socket_action(s->multi, CURL_SOCKET_TIMEOUT, 0, &running);
>
> curl_multi_socket_action isn't available on the CURL lib used
> by CentOS 5.6. The obvious workaround is to disable CURL
> when calling configure.
Matthew, can you please check whether this call can be avoided, or
otherwise change configure to check the presence of the function?
Kevin
next prev parent reply other threads:[~2014-05-06 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1398882243-14783-1-git-send-email-kwolf@redhat.com>
2014-05-02 10:34 ` [Qemu-devel] [PULL 00/31] Block patches Peter Maydell
[not found] ` <1398882243-14783-17-git-send-email-kwolf@redhat.com>
2014-05-04 10:13 ` [Qemu-devel] [PULL 16/31] block: Fix open_flags in bdrv_reopen() Jan Kiszka
[not found] ` <1398882243-14783-29-git-send-email-kwolf@redhat.com>
2014-05-06 9:44 ` [Qemu-devel] [PULL 28/31] curl: Remove unnecessary explicit calls to internal event handler Laurent Desnogues
2014-05-06 9:56 ` Kevin Wolf [this message]
2014-05-06 12:41 ` Matthew Booth
2014-05-06 13:12 ` Kevin Wolf
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=20140506095624.GB3941@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=laurent.desnogues@gmail.com \
--cc=mbooth@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).