From: Jamie Lokier <jamie@shareable.org>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Nolan <nolan@sigbus.net>, Alexander Graf <agraf@suse.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Allow adjustment of http block device's readahead size.
Date: Tue, 30 Jun 2009 17:44:50 +0100 [thread overview]
Message-ID: <20090630164450.GA18666@shareable.org> (raw)
In-Reply-To: <4A4A14D4.8010204@codemonkey.ws>
Anthony Liguori wrote:
> Alexander Graf wrote:
> >
> >On 29.06.2009, at 15:45, Anthony Liguori wrote:
> >
> >>Nolan wrote:
> >>>Allow adjustment of http block device's readahead size, via the
> >>>environment variable "HTTP_READAHEAD_SIZE".
> >>>
> >>>Signed-off-by: Nolan Leake <nolan <at> sigbus.net>
> >>>
> >>
> >>I'd rather a command line option than an environmental variable.
> >
> >Wouldn't it make sense to pass arbitrary options via -drive to backends?
> >
> >That way we could have -drive
> >file=http://sample.com/test.iso,http-readahead=1024.
>
> Where it gets complex is that you probably want those options to be
> included as qcow2 backing_file too. I've thought about this in the past
> and haven't been able to come to a great solution.
And sometimes you want to change or override the qcow2 backing_file options...
It's already awkward when you want to rename a bunch of image files,
that the backing relative file path is fixed in the qcow2 file and
cannot be overridden by a management program (without rewriting the
qcow2 file).
Options like http-readahead=1024 on the backing file are the sort of
thing it's reasonable to want to change more often. Imho they are in
the same category as the cache= option, which should be controllable
for backing files when invoking QEMU independently from the main file.
-- Jamie
prev parent reply other threads:[~2009-06-30 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 2:11 [Qemu-devel] [PATCH] Allow adjustment of http block device's readahead size Nolan
2009-06-29 13:45 ` Anthony Liguori
2009-06-30 13:09 ` Alexander Graf
2009-06-30 13:36 ` Anthony Liguori
2009-06-30 16:44 ` Jamie Lokier [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=20090630164450.GA18666@shareable.org \
--to=jamie@shareable.org \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=nolan@sigbus.net \
--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).