From: "Daniel P. Berrange" <berrange@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, armbru@redhat.com,
eblake@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/4] block/rbd: code movement
Date: Mon, 27 Feb 2017 09:28:56 +0000 [thread overview]
Message-ID: <20170227092856.GC18219@redhat.com> (raw)
In-Reply-To: <6f1d60bdbbb4e82991c699d4aa6666c4317a1c5d.1488180142.git.jcody@redhat.com>
Describing this as "code movement" when the added & removed chunks are not
identical is a bit misleading.
Can you expand the commit message to explain why the extra options are
being added
On Mon, Feb 27, 2017 at 02:30:39AM -0500, Jeff Cody wrote:
> Signed-off-by: Jeff Cody <jcody@redhat.com>
> ---
> block/rbd.c | 64 +++++++++++++++++++++++++++++++++++++++++++------------------
> 1 file changed, 45 insertions(+), 19 deletions(-)
>
> diff --git a/block/rbd.c b/block/rbd.c
> index 3f1a9de..c8d4eb1 100644
> --- a/block/rbd.c
> +++ b/block/rbd.c
> @@ -357,6 +357,51 @@ static void qemu_rbd_memset(RADOSCB *rcb, int64_t offs)
> }
> }
>
> +static QemuOptsList runtime_opts = {
> + .name = "rbd",
> + .head = QTAILQ_HEAD_INITIALIZER(runtime_opts.head),
> + .desc = {
> + {
> + .name = "filename",
> + .type = QEMU_OPT_STRING,
> + .help = "Specification of the rbd image",
> + },
> + {
> + .name = "password-secret",
> + .type = QEMU_OPT_STRING,
> + .help = "ID of secret providing the password",
> + },
> + {
> + .name = "conf",
> + .type = QEMU_OPT_STRING,
> + },
> + {
> + .name = "pool",
> + .type = QEMU_OPT_STRING,
> + },
> + {
> + .name = "image",
> + .type = QEMU_OPT_STRING,
> + },
> + {
> + .name = "snapshot",
> + .type = QEMU_OPT_STRING,
> + },
> + {
> + /* you might be tempted to call this 'id' to match
> + * the ceph documentation, but then it'll get gobbled
> + * up in the block layer before it gets to the image driver */
> + .name = "rbd-id",
> + .type = QEMU_OPT_STRING,
> + },
> + {
> + .name = "keyvalue-pairs",
> + .type = QEMU_OPT_STRING,
> + },
> + { /* end of list */ }
> + },
> +};
> +
> static int qemu_rbd_create(const char *filename, QemuOpts *opts, Error **errp)
> {
> Error *local_err = NULL;
> @@ -500,25 +545,6 @@ static void qemu_rbd_complete_aio(RADOSCB *rcb)
> qemu_aio_unref(acb);
> }
>
> -/* TODO Convert to fine grained options */
> -static QemuOptsList runtime_opts = {
> - .name = "rbd",
> - .head = QTAILQ_HEAD_INITIALIZER(runtime_opts.head),
> - .desc = {
> - {
> - .name = "filename",
> - .type = QEMU_OPT_STRING,
> - .help = "Specification of the rbd image",
> - },
> - {
> - .name = "password-secret",
> - .type = QEMU_OPT_STRING,
> - .help = "ID of secret providing the password",
> - },
> - { /* end of list */ }
> - },
> -};
> -
> static int qemu_rbd_open(BlockDriverState *bs, QDict *options, int flags,
> Error **errp)
> {
> --
> 2.9.3
>
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
next prev parent reply other threads:[~2017-02-27 9:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 7:30 [Qemu-devel] [PATCH 0/4] RBD: blockdev-add Jeff Cody
2017-02-27 7:30 ` [Qemu-devel] [PATCH 1/4] block/rbd: don't copy strings in qemu_rbd_next_tok() Jeff Cody
2017-02-27 16:39 ` Markus Armbruster
2017-02-27 18:07 ` Jeff Cody
2017-02-27 7:30 ` [Qemu-devel] [PATCH 2/4] block/rbd: code movement Jeff Cody
2017-02-27 9:28 ` Daniel P. Berrange [this message]
2017-02-27 13:14 ` Jeff Cody
2017-02-27 7:30 ` [Qemu-devel] [PATCH 3/4] block/rbd: parse all options via bdrv_parse_filename Jeff Cody
2017-02-27 7:30 ` [Qemu-devel] [PATCH 4/4] block/rbd: Add blockdev-add support Jeff Cody
2017-02-27 7:36 ` Jeff Cody
2017-02-27 9:31 ` Daniel P. Berrange
2017-02-27 13:18 ` Jeff Cody
2017-02-27 13:30 ` Daniel P. Berrange
2017-02-27 13:38 ` Jeff Cody
2017-02-27 13:45 ` Daniel P. Berrange
2017-02-27 15:27 ` Jeff Cody
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=20170227092856.GC18219@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=jcody@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 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).