From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55823) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bgvzs-0000CD-NT for qemu-devel@nongnu.org; Mon, 05 Sep 2016 11:39:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bgvzo-0000cm-0R for qemu-devel@nongnu.org; Mon, 05 Sep 2016 11:39:43 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45364) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bgvzn-0000ci-RS for qemu-devel@nongnu.org; Mon, 05 Sep 2016 11:39:39 -0400 Date: Mon, 5 Sep 2016 16:39:35 +0100 From: "Daniel P. Berrange" Message-ID: <20160905153935.GJ24656@redhat.com> Reply-To: "Daniel P. Berrange" References: <1473085586-6834-1-git-send-email-ashijeetacharya@gmail.com> <20160905143603.GF24656@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH v3] Move migrate_set_speed and migrate_set_downtime into migrate_set_parameter List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ashijeet Acharya Cc: lcapitulino@redhat.com, quintela@redhat.com, QEMU Developers , armbru@redhat.com, "dgilbert@redhat.com" , amit.shah@redhat.com, Paolo Bonzini 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 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 :|