From: Kevin Wolf <kwolf@redhat.com>
To: Ashijeet Acharya <ashijeetacharya@gmail.com>
Cc: eblake@redhat.com, pl@kamp.de, jcody@redhat.com,
mreitz@redhat.com, armbru@redhat.com, qemu-devel@nongnu.org,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 2/2] qapi: allow blockdev-add for NFS
Date: Thu, 27 Oct 2016 18:45:21 +0200 [thread overview]
Message-ID: <20161027164521.GM4027@noname.redhat.com> (raw)
In-Reply-To: <1477565022-11377-3-git-send-email-ashijeetacharya@gmail.com>
Am 27.10.2016 um 12:43 hat Ashijeet Acharya geschrieben:
> Introduce new object 'BlockdevOptionsNFS' in qapi/block-core.json to
> support blockdev-add for NFS network protocol driver. Also make a new
> struct NFSServer to support tcp connection.
>
> Signed-off-by: Ashijeet Acharya <ashijeetacharya@gmail.com>
> ---
> qapi/block-core.json | 77 +++++++++++++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 73 insertions(+), 4 deletions(-)
>
> diff --git a/qapi/block-core.json b/qapi/block-core.json
> index 9d797b8..75e28aa 100644
> --- a/qapi/block-core.json
> +++ b/qapi/block-core.json
> @@ -1708,15 +1708,16 @@
> #
> # @host_device, @host_cdrom: Since 2.1
> # @gluster: Since 2.7
> +# @nfs: Since 2.8
> #
> # Since: 2.0
> ##
> { 'enum': 'BlockdevDriver',
> 'data': [ 'archipelago', 'blkdebug', 'blkverify', 'bochs', 'cloop',
> 'dmg', 'file', 'ftp', 'ftps', 'gluster', 'host_cdrom',
> - 'host_device', 'http', 'https', 'luks', 'null-aio', 'null-co',
> - 'parallels', 'qcow', 'qcow2', 'qed', 'quorum', 'raw',
> - 'replication', 'tftp', 'vdi', 'vhdx', 'vmdk', 'vpc', 'vvfat' ] }
> + 'host_device', 'http', 'https', 'luks', 'nfs', 'null-aio',
> + 'null-co', 'parallels', 'qcow', 'qcow2', 'qed', 'quorum', 'raw',
> + 'replication', 'tftp', 'vdi', 'vhdx', 'vmdk', 'vpc', 'vvfat' ] }
>
> ##
> # @BlockdevOptionsFile
> @@ -2212,6 +2213,74 @@
> '*top-id': 'str' } }
>
> ##
> +# @NFSTransport
> +#
> +# An enumeration of NFS transport types
> +#
> +# @inet: host address for NFS server
This description belongs to the 'host' field in NFSServer. Here it
should probably say something like "TCP transport".
> +# Since 2.8
> +##
> +{ 'enum': 'NFSTransport',
> + 'data': [ 'inet' ] }
> +
> +##
> +# @NFSServer
> +#
> +# Captures the address of the socket
> +#
> +# @type: transport type used for NFS (only TCP supported)
> +#
> +# @inet: host address for NFS server
Here the description is right, but the field name is wrong (should be
@host instead of @inet).
> +# Since 2.8
> +##
> +{ 'struct': 'NFSServer',
> + 'data': { 'type': 'NFSTransport',
> + 'host': 'str' } }
> +
Kevin
next prev parent reply other threads:[~2016-10-27 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 10:43 [Qemu-devel] [PATCH v3 0/2] block: allow blockdev-add for NFS Ashijeet Acharya
2016-10-27 10:43 ` [Qemu-devel] [PATCH v3 1/2] block/nfs: Introduce runtime_opts in NFS Ashijeet Acharya
2016-10-27 10:43 ` [Qemu-devel] [PATCH v3 2/2] qapi: allow blockdev-add for NFS Ashijeet Acharya
2016-10-27 16:45 ` Kevin Wolf [this message]
2016-10-27 16:43 ` [Qemu-devel] [PATCH v3 0/2] block: " Kevin Wolf
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=20161027164521.GM4027@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=ashijeetacharya@gmail.com \
--cc=eblake@redhat.com \
--cc=jcody@redhat.com \
--cc=mreitz@redhat.com \
--cc=pl@kamp.de \
--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.