From: Stefan Hajnoczi <stefanha@gmail.com>
To: Fam Zheng <famz@redhat.com>
Cc: kwolf@redhat.com, jcody@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 01/11] curl: introduce CURLSockInfo to BDRVCURLState.
Date: Tue, 14 May 2013 09:59:45 +0200 [thread overview]
Message-ID: <20130514075945.GC3632@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1368498390-20738-2-git-send-email-famz@redhat.com>
On Tue, May 14, 2013 at 10:26:20AM +0800, Fam Zheng wrote:
> We use socket provided by curl in the driver. Libcurl multi interface
> has option CURLMOPT_SOCKETFUNCTION for socket.
>
> Per man 3 curl_multi_setopt:
>
> ...
> CURLMOPT_SOCKETFUNCTION
>
> Pass a pointer to a function matching the curl_socket_callback
> prototype. The curl_multi_socket_action(3) function informs the
> application about updates in the socket (file descriptor) status by
> doing none, one, or multiple calls to the curl_socket_callback given in
> the param argument. They update the status with changes since the
> previous time a curl_multi_socket(3) function was called. If the given
> callback pointer is NULL, no callback will be called. Set the callback's
> userp argument with CURLMOPT_SOCKETDATA. See curl_multi_socket(3) for
> more callback details.
> ...
>
> The added structure store information for all the socket returned by
> libcurl. The most important field is action, which is used to keep what
> actions are needed when this socket's fd handler is called.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> block/curl.c | 21 +++++++++++++++++++--
> 1 file changed, 19 insertions(+), 2 deletions(-)
>
> diff --git a/block/curl.c b/block/curl.c
> index b8935fd..14f4552 100644
> --- a/block/curl.c
> +++ b/block/curl.c
> @@ -75,10 +75,18 @@ typedef struct CURLState
> char in_use;
> } CURLState;
>
> +typedef struct CURLSockInfo {
> + curl_socket_t fd;
> + int action;
> + struct BDRVCURLState *s;
> + QLIST_ENTRY(CURLSockInfo) next;
> +} CURLSockInfo;
This patch doesn't make sense by itself. CURLSockInfo is unused and
->action is never assigned to. I guess this will eventually replace
BDRVCURLState->states[] but at this point in the patch series it is hard
to tell - it would be nice to explain this in the commit description.
> typedef struct BDRVCURLState {
> CURLM *multi;
> size_t len;
> CURLState states[CURL_NUM_STATES];
> + QLIST_HEAD(, CURLSockInfo) socks;
> char *url;
> size_t readahead_size;
> } BDRVCURLState;
> @@ -90,7 +98,16 @@ static int curl_aio_flush(void *opaque);
> static int curl_sock_cb(CURL *curl, curl_socket_t fd, int action,
> void *s, void *sp)
> {
> + BDRVCURLState *bs = (BDRVCURLState *)s;
void * is automatically coerced to any pointer type. No need for a type
cast.
> DPRINTF("CURL (AIO): Sock action %d on fd %d\n", action, fd);
> + CURLSockInfo *sock = (CURLSockInfo *)sp;
Same here.
> + if (!sp) {
> + sock = g_malloc0(sizeof(CURLSockInfo));
> + sock->fd = fd;
> + sock->s = bs;
> + QLIST_INSERT_HEAD(&bs->socks, sock, next);
> + curl_multi_assign(bs->multi, fd, sock);
> + }
> switch (action) {
> case CURL_POLL_IN:
> qemu_aio_set_fd_handler(fd, curl_multi_do, NULL, curl_aio_flush, s);
> @@ -462,8 +479,8 @@ static int curl_open(BlockDriverState *bs, QDict *options, int flags)
> // initialize the multi interface!
>
> s->multi = curl_multi_init();
> - curl_multi_setopt( s->multi, CURLMOPT_SOCKETDATA, s);
> - curl_multi_setopt( s->multi, CURLMOPT_SOCKETFUNCTION, curl_sock_cb );
> + curl_multi_setopt(s->multi, CURLMOPT_SOCKETDATA, s);
> + curl_multi_setopt(s->multi, CURLMOPT_SOCKETFUNCTION, curl_sock_cb);
> curl_multi_do(s);
>
> qemu_opts_del(opts);
> --
> 1.8.1.4
>
>
next prev parent reply other threads:[~2013-05-14 7:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 2:26 [Qemu-devel] [PATCH v2 00/11] curl: fix curl read Fam Zheng
2013-05-14 2:26 ` [Qemu-devel] [PATCH v2 01/11] curl: introduce CURLSockInfo to BDRVCURLState Fam Zheng
2013-05-14 7:59 ` Stefan Hajnoczi [this message]
2013-05-14 2:26 ` [Qemu-devel] [PATCH v2 02/11] curl: change magic number to macro Fam Zheng
2013-05-14 8:04 ` Stefan Hajnoczi
2013-05-14 2:26 ` [Qemu-devel] [PATCH v2 03/11] curl: change curl_multi_do to curl_fd_handler Fam Zheng
2013-05-14 2:26 ` [Qemu-devel] [PATCH v2 04/11] curl: fix curl_open Fam Zheng
2013-05-14 8:13 ` Stefan Hajnoczi
2013-05-14 2:26 ` [Qemu-devel] [PATCH v2 05/11] curl: add timer to BDRVCURLState Fam Zheng
2013-05-14 2:26 ` [Qemu-devel] [PATCH v2 06/11] curl: introduce CURLDataCache Fam Zheng
2013-05-14 2:26 ` [Qemu-devel] [PATCH v2 07/11] curl: make use of CURLDataCache Fam Zheng
2013-05-14 2:26 ` [Qemu-devel] [PATCH v2 08/11] curl: use list to store CURLState Fam Zheng
2013-05-14 2:26 ` [Qemu-devel] [PATCH v2 09/11] curl: release everything on curl_close Fam Zheng
2013-05-14 8:20 ` Stefan Hajnoczi
2013-05-14 2:26 ` [Qemu-devel] [PATCH v2 10/11] curl: add cache quota Fam Zheng
2013-05-14 2:26 ` [Qemu-devel] [PATCH v2 11/11] curl: introduce ssl_no_cert runtime option Fam Zheng
2013-05-14 8:22 ` [Qemu-devel] [PATCH v2 00/11] curl: fix curl read Stefan Hajnoczi
2013-05-14 8:50 ` Fam Zheng
2013-05-15 3:46 ` Fam Zheng
2013-05-15 7:56 ` Stefan Hajnoczi
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=20130514075945.GC3632@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=famz@redhat.com \
--cc=jcody@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 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).