From: Stefan Hajnoczi <stefanha@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>,
kwolf@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] curl: fix curl read
Date: Wed, 15 May 2013 09:46:53 +0200 [thread overview]
Message-ID: <20130515074653.GA16991@stefanha-thinkpad.muc.redhat.com> (raw)
In-Reply-To: <20130515032929.GA23662@fam-laptop.nay.redhat.com>
On Wed, May 15, 2013 at 11:29:29AM +0800, Fam Zheng wrote:
> On Thu, 05/09 17:16, Stefan Hajnoczi wrote:
> > On Thu, May 09, 2013 at 02:56:50PM +0800, Fam Zheng wrote:
> > > On Thu, 05/09 08:41, Stefan Hajnoczi wrote:
> > > > On Fri, May 03, 2013 at 04:00:09PM +0800, Fam Zheng wrote:
> > > > > + cache = curl_find_cache(s, aio_base, aio_bytes);
> > > > > + if (cache) {
> > > > > + curl_complete_io(s, acb, cache);
> > > > > + return;
> > > > > }
> > > >
> > > > What is the point of the cache? Can you split it into a separate patch?
> > >
> > > The cache is for prefetch. Data is fetched by 256k chunks using libcurl
> > > and stored in cache to fill future io request, reducing overall http
> > > request overhead.
> >
> > That sounds like a performance optimization which is not part of fixing
> > broken block/curl.c :).
> >
>
> I didn't invent it here. Read ahead is already in curl.c, (see
> BDRVCURLState.readahead_size). I don't think it's time to remove it here
> either, but rename to a better name should be OK. What do you think?
Yes, that's true. Although I'm not a fan of readahead I guess it's
already implemented.
> BTW please keep me CC'ed when reply so that I can notice it better.
Please check the headers that your email client is sending:
Mail-Followup-To: Stefan Hajnoczi <stefanha@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>, kwolf@redhat.com,
qemu-devel@nongnu.org
Stefan
prev parent reply other threads:[~2013-05-15 7:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 8:00 [Qemu-devel] [PATCH] curl: fix curl read Fam Zheng
2013-05-03 11:09 ` Stefan Hajnoczi
2013-05-03 11:23 ` Fam Zheng
2013-05-09 5:47 ` Stefan Hajnoczi
2013-05-09 6:41 ` Stefan Hajnoczi
2013-05-09 6:56 ` Fam Zheng
2013-05-09 15:16 ` Stefan Hajnoczi
2013-05-15 3:29 ` Fam Zheng
2013-05-15 7:46 ` Stefan Hajnoczi [this message]
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=20130515074653.GA16991@stefanha-thinkpad.muc.redhat.com \
--to=stefanha@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).