From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: armbru@redhat.com, mreitz@redhat.com, berrange@redhat.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] doc: Document driver-specific -blockdev options
Date: Thu, 22 Sep 2016 14:02:26 -0500 [thread overview]
Message-ID: <e189ae18-010b-eda8-1758-f20d25e9560d@redhat.com> (raw)
In-Reply-To: <1474558931-8968-4-git-send-email-kwolf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2016 bytes --]
On 09/22/2016 10:42 AM, Kevin Wolf wrote:
> This documents the driver-specific options for the raw, qcow2 and file
> block drivers for the man page. For everything else, we refer to the
> QAPI documentation.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> qemu-options.hx | 62 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 62 insertions(+)
>
>
> +@item Driver-specific options for @code{file}
> +@table @code
> +@item filename
> +The path to the image file in the local filesystem
> +@item aio
> +Specifies the AIO backend (threads/native, default: threads)
> +@end table
> +
> +@item Driver-specific options for @code{raw}
> +@table @code
> +@item file
> +Reference to or definition of the data source block device
> +@end table
Would an example command line make things any easier to read, for giving
hints on how many dotted names are needed as you describe further
nesting levels in relation to the top level?
> +@item cache-clean-interval
> +Clean unused entries in the L2 and refcount caches. The interval is in seconds.
> +The default value is 0 and it disables this feature.
> +
> +@item pass-discard-request
> +Whether discard requests to the qcow2 device should be forwarded to the data
> +source (on/off)
> +
> +@item pass-discard-snapshot
> +Whether discard requests for the data source should be issued when a snapshot
> +operation (e.g. deleting a snapshot) frees clusters in the qcow2 file (on/off)
> +
> +@item pass-discard-other
> +Whether discard requests for the data source should be issued on other
> +occasions where a cluster gets freed (on/off)
I like that cache-clean-interval mentioned a default; should these other
lines do likewise?
At any rate, those ideas can be followups if desired, as this patch is
strictly an improvement.
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:[~2016-09-22 19:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 15:42 [Qemu-devel] [PATCH 0/3] Add -blockdev command line option Kevin Wolf
2016-09-22 15:42 ` [Qemu-devel] [PATCH 1/3] block: Add '-blockdev' " Kevin Wolf
2016-09-22 18:45 ` Eric Blake
2016-09-23 9:37 ` Kevin Wolf
2016-09-23 14:09 ` Eric Blake
2016-09-22 15:42 ` [Qemu-devel] [PATCH 2/3] doc: Document generic -blockdev options Kevin Wolf
2016-09-22 18:56 ` Eric Blake
2016-09-22 15:42 ` [Qemu-devel] [PATCH 3/3] doc: Document driver-specific " Kevin Wolf
2016-09-22 19:02 ` Eric Blake [this message]
2016-09-23 9:46 ` Kevin Wolf
2016-09-22 17:12 ` [Qemu-devel] [PATCH 0/3] Add -blockdev command line option no-reply
2016-09-22 18:58 ` Eric Blake
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=e189ae18-010b-eda8-1758-f20d25e9560d@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.