From: Eric Blake <eblake@redhat.com>
To: Max Reitz <mreitz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Peter Lieven <pl@kamp.de>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] qemu-img: Allow source cache mode specification
Date: Mon, 21 Jul 2014 09:52:08 -0600 [thread overview]
Message-ID: <53CD3728.1040904@redhat.com> (raw)
In-Reply-To: <1405802159-2355-2-git-send-email-mreitz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2299 bytes --]
On 07/19/2014 02:35 PM, Max Reitz wrote:
> Many qemu-img subcommands only read the source file(s) once. For these
> use cases, a full write-back cache is unnecessary and mainly clutters
> host cache memory. Though this is generally no concern as cache memory
> is freely available and can be scaled by the host OS, it may become a
> concern with thin provisioning.
>
> For these cases, it makes sense to allow users to freely specify the
> source cache mode (e.g. use no cache at all).
>
> This commit adds a new switch (-T) for the qemu-img subcommands check,
> compare, convert and rebase to specify the cache to be used for source
> images (the backing file in case of rebase).
What mnemonic did you have in mind when choosing -T? Or was it just a
universally available letter for the subcommands you were touching?
>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> qemu-img-cmds.hx | 16 ++++++------
> qemu-img.c | 78 ++++++++++++++++++++++++++++++++++++++++++++------------
> qemu-img.texi | 14 +++++++---
> 3 files changed, 80 insertions(+), 28 deletions(-)
>
> diff --git a/qemu-img-cmds.hx b/qemu-img-cmds.hx
> index d029609..5613628 100644
> --- a/qemu-img-cmds.hx
> +++ b/qemu-img-cmds.hx
> @@ -10,9 +10,9 @@ STEXI
> ETEXI
>
> DEF("check", img_check,
> - "check [-q] [-f fmt] [--output=ofmt] [-r [leaks | all]] filename")
> + "check [-q] [-f fmt] [--output=ofmt] [-r [leaks | all]] [-T src_cache] filename")
Might be nice to fix the unintentional double space before -r while
touching this line.
> DEF("convert", img_convert,
> - "convert [-c] [-p] [-q] [-n] [-f fmt] [-t cache] [-O output_fmt] [-o options] [-s snapshot_id_or_name] [-l snapshot_param] [-S sparse_size] filename [filename2 [...]] output_filename")
> + "convert [-c] [-p] [-q] [-n] [-f fmt] [-t cache] [-T src_cache] [-O output_fmt] [-o options] [-s snapshot_id_or_name] [-l snapshot_param] [-S sparse_size] filename [filename2 [...]] output_filename")
Oh, maybe you just picked -T for source because -t was already picked
for destination?
At any rate, seems reasonable.
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-07-21 15:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-19 20:35 [Qemu-devel] [PATCH 0/2] qemu-img: Allow source cache mode specification Max Reitz
2014-07-19 20:35 ` [Qemu-devel] [PATCH 1/2] " Max Reitz
2014-07-21 15:52 ` Eric Blake [this message]
2014-07-22 20:06 ` Max Reitz
2014-07-23 8:10 ` Kevin Wolf
2014-07-24 23:44 ` Max Reitz
2014-07-19 20:35 ` [Qemu-devel] [PATCH 2/2] qemu-img: Allow cache mode specification for amend Max Reitz
2014-07-21 15:57 ` Eric Blake
2014-07-22 20:09 ` Max Reitz
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=53CD3728.1040904@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pl@kamp.de \
--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).