All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ashijeet Acharya <ashijeetacharya@gmail.com>
Cc: lcapitulino@redhat.com, quintela@redhat.com,
	QEMU Developers <qemu-devel@nongnu.org>,
	armbru@redhat.com, "dgilbert@redhat.com" <dgilbert@redhat.com>,
	amit.shah@redhat.com, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] Move migrate_set_speed and migrate_set_downtime into migrate_set_parameter
Date: Mon, 5 Sep 2016 16:39:35 +0100	[thread overview]
Message-ID: <20160905153935.GJ24656@redhat.com> (raw)
In-Reply-To: <CAC2QTZbbSGL5VRBtHEbSp3Cmg9ZvVj9LsHcYJggRCw6ShKK4fg@mail.gmail.com>

On Mon, Sep 05, 2016 at 08:44:26PM +0530, Ashijeet Acharya wrote:
> On Mon, Sep 5, 2016 at 8:06 PM, Daniel P. Berrange <berrange@redhat.com> wrote:
> > On Mon, Sep 05, 2016 at 07:56:26PM +0530, Ashijeet Acharya wrote:

> >> diff --git a/qapi-schema.json b/qapi-schema.json
> >> index 5658723..250eac5 100644
> >> --- a/qapi-schema.json
> >> +++ b/qapi-schema.json
> >> @@ -637,12 +637,18 @@
> >>  #                hostname must be provided so that the server's x509
> >>  #                certificate identity can be validated. (Since 2.7)
> >>  #
> >> +# @max-bandwidth: to set maximum speed for migration. A value lesser than
> >> +#                 zero will be automatically round upto zero. Since 2.8)
> >
> > Document the units for this ? eg is it bits-per-second, kb-per-second,
> > mb-per-second, etc
> >
> 
> Should I document it the way it is for old-commands? Like this;
> 
> # @migrate_set_speed
> #
> # Set maximum speed for migration.
> #
> # @value: maximum speed in bytes.
> #
> # Returns: nothing on success
> #
> # Notes: A value lesser than zero will be automatically round up to zero.
> #
> # Since: 0.14.0
> ##

No, that syntax isn't appropriate for documenting parameters. You hjust
have to put it all together.

@max-bandwidth: set maximum speed for migration in bytes-per-second. A
                value lesser than zero will be automatically round upto
		zero. Since 2.8)

Oh and IMHO we should reject values less than zero as invalid, with an
error message, not silently interpret them as meaning zero.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2016-09-05 15:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05  7:45 [Qemu-devel] [PATCH] Move migrate_set_speed and migrate_set_downtime into migrate_set_parameter Ashijeet Acharya
2016-09-05  8:01 ` Paolo Bonzini
2016-09-05  8:11   ` Ashijeet Acharya
2016-09-05  8:16     ` Paolo Bonzini
2016-09-05  8:25       ` Ashijeet Acharya
2016-09-05 11:16         ` Dr. David Alan Gilbert
2016-09-05 11:37           ` [Qemu-devel] [PATCH v2] " Ashijeet Acharya
2016-09-05 11:45             ` Paolo Bonzini
2016-09-05 11:59               ` Ashijeet Acharya
2016-09-05 12:01                 ` Paolo Bonzini
2016-09-05 12:08                   ` Ashijeet Acharya
2016-09-05 13:09               ` Ashijeet Acharya
2016-09-05 13:16                 ` Paolo Bonzini
2016-09-05 14:26                   ` [Qemu-devel] [PATCH v3] " Ashijeet Acharya
2016-09-05 14:36                     ` Daniel P. Berrange
2016-09-05 15:14                       ` Ashijeet Acharya
2016-09-05 15:39                         ` Daniel P. Berrange [this message]
2016-09-05 15:46                           ` Ashijeet Acharya
2016-09-05 14:28                   ` [Qemu-devel] [PATCH v3] Move migrate_set_speed and migrate_set_downtime into migrate_set_parameter (reversed logic) Ashijeet Acharya
2016-09-05 15:56                   ` [Qemu-devel] [PATCH v2] Move migrate_set_speed and migrate_set_downtime into migrate_set_parameter Daniel P. Berrange
2016-09-06  8:16                     ` Markus Armbruster
2016-09-06 13:16           ` [Qemu-devel] [PATCH] " Juan Quintela

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=20160905153935.GJ24656@redhat.com \
    --to=berrange@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=armbru@redhat.com \
    --cc=ashijeetacharya@gmail.com \
    --cc=dgilbert@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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 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.