From: Kevin Wolf <kwolf@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Ashish Mittal <ashmit602@gmail.com>,
qemu-devel@nongnu.org, pbonzini@redhat.com, armbru@redhat.com,
ashish.mittal@veritas.com, stefanha@gmail.com,
Ketan.Nilangekar@veritas.com, Abhijit.Dey@veritas.com
Subject: Re: [Qemu-devel] [PATCH v3 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support
Date: Mon, 15 Aug 2016 12:47:52 +0200 [thread overview]
Message-ID: <20160815104752.GE6024@noname.str.redhat.com> (raw)
In-Reply-To: <20160815102046.GC13261@redhat.com>
Am 15.08.2016 um 12:20 hat Daniel P. Berrange geschrieben:
> On Sat, Aug 13, 2016 at 09:35:12PM -0700, Ashish Mittal wrote:
> > +/*
> > + * vxhs_parse_uri: Parse the incoming URI and populate *conf with the
> > + * vdisk_id, and all the host(s) information. Host at index 0 is local storage
> > + * agent and the rest, reflection target storage agents. The local storage
> > + * agent ip is the efficient internal address in the uri, e.g. 192.168.0.2.
> > + * The local storage agent address is stored at index 0. The reflection target
> > + * ips, are the E-W data network addresses of the reflection node agents, also
> > + * extracted from the uri.
> > + */
> > +static int vxhs_parse_uri(BlockdevOptionsVxHS *conf,
> > + const char *filename)
>
> Delete this method entirely. We should not be adding URI syntax for any new
> block driver. The QAPI schema syntax is all we need.
I disagree. URI syntax is nice for human users.
However, you should use the proper interfaces to implement this, which
is .bdrv_parse_filename(). This is a function that gets a string and
converts it into a QDict, which is then passed to .bdrv_open(). So it
uses exactly the same code path in .bdrv_open() as if used directly with
QAPI.
Kevin
next prev parent reply other threads:[~2016-08-15 10:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-14 4:35 [Qemu-devel] [PATCH v3 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support Ashish Mittal
2016-08-14 4:41 ` no-reply
2016-08-14 4:43 ` no-reply
2016-08-15 10:20 ` Daniel P. Berrange
2016-08-15 10:47 ` Kevin Wolf [this message]
2016-08-15 10:54 ` Daniel P. Berrange
2016-08-17 11:20 ` Paolo Bonzini
2016-08-23 23:28 ` ashish mittal
2016-08-15 16:29 ` ashish mittal
2016-08-17 11:22 ` Paolo Bonzini
2016-08-17 21:58 ` ashish mittal
2016-08-20 18:42 ` ashish mittal
2016-08-23 21:58 ` Stefan Hajnoczi
2016-08-23 22:22 ` ashish mittal
2016-11-15 19:02 ` ashish mittal
2016-11-15 20:48 ` Stefan Hajnoczi
2016-11-15 20:51 ` ashish mittal
2017-02-07 23:20 ` ashish mittal
2016-08-23 22:57 ` ashish mittal
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=20160815104752.GE6024@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=Abhijit.Dey@veritas.com \
--cc=Ketan.Nilangekar@veritas.com \
--cc=armbru@redhat.com \
--cc=ashish.mittal@veritas.com \
--cc=ashmit602@gmail.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 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).