From: Jeff Cody <jcody@redhat.com>
To: Ashish Mittal <ashmit602@gmail.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, kwolf@redhat.com,
armbru@redhat.com, berrange@redhat.com, famz@redhat.com,
ashish.mittal@veritas.com, stefanha@gmail.com,
Ketan.Nilangekar@veritas.com, jferlan@redhat.com,
Buddhi.Madhav@veritas.com, Suraj.Singh@veritas.com,
Nitin.Jerath@veritas.com, peter.maydell@linaro.org,
venkatesha.mg@veritas.com, Rakesh.Ranjan@veritas.com,
eblake@redhat.com, Abhijit.Dey@veritas.com
Subject: Re: [Qemu-devel] [PATCH v11 0/2] block/vxhs.c: Add support for a new block device type called "vxhs"
Date: Thu, 20 Apr 2017 11:03:39 -0400 [thread overview]
Message-ID: <20170420150339.GH15762@localhost.localdomain> (raw)
In-Reply-To: <1491277689-24949-1-git-send-email-Ashish.Mittal@veritas.com>
On Mon, Apr 03, 2017 at 08:48:07PM -0700, Ashish Mittal wrote:
> - Veritas HyperScale block driver in QEMU is designed to provide an accelerated
> IO path from KVM virtual machines to Veritas HyperScale storage service.
>
> - A network IO transfer library that translates block IO from HyperScale block
> driver to a network IO format to send it to Veritas HyperScale storage
> service. This library (libvxhs) has been open sourced and is available on
> github here: https://github.com/VeritasHyperScale/libqnio.git
>
> Ashish Mittal (2):
> block/vxhs.c: Add support for a new block device type called "vxhs"
> block/vxhs.c: Add qemu-iotests for new block device type "vxhs"
>
> block/Makefile.objs | 2 +
> block/trace-events | 17 ++
> block/vxhs.c | 575 +++++++++++++++++++++++++++++++++++++++
> configure | 39 +++
> qapi/block-core.json | 23 +-
> tests/qemu-iotests/common | 6 +
> tests/qemu-iotests/common.config | 13 +
> tests/qemu-iotests/common.filter | 1 +
> tests/qemu-iotests/common.rc | 19 ++
> 9 files changed, 693 insertions(+), 2 deletions(-)
> create mode 100644 block/vxhs.c
>
> --
> 2.5.5
>
Thanks,
Applied to my block branch:
git://github.com/codyprime/qemu-kvm-jtc block
-Jeff
next prev parent reply other threads:[~2017-04-20 15:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 3:48 [Qemu-devel] [PATCH v11 0/2] block/vxhs.c: Add support for a new block device type called "vxhs" Ashish Mittal
2017-04-04 3:48 ` [Qemu-devel] [PATCH v11 1/2] " Ashish Mittal
2017-04-04 15:55 ` Daniel P. Berrange
2017-04-11 19:47 ` Jeff Cody
2017-04-12 8:10 ` ashish mittal
2017-04-12 12:15 ` Jeff Cody
2017-04-19 16:27 ` Stefan Hajnoczi
2017-04-20 1:01 ` ashish mittal
2017-04-04 3:48 ` [Qemu-devel] [PATCH v11 2/2] block/vxhs.c: Add qemu-iotests for new block device type "vxhs" Ashish Mittal
2017-04-04 18:02 ` [Qemu-devel] [PATCH v11 0/2] block/vxhs.c: Add support for a new block device type called "vxhs" Jeff Cody
2017-04-20 15:03 ` Jeff Cody [this message]
2017-04-20 16:03 ` 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=20170420150339.GH15762@localhost.localdomain \
--to=jcody@redhat.com \
--cc=Abhijit.Dey@veritas.com \
--cc=Buddhi.Madhav@veritas.com \
--cc=Ketan.Nilangekar@veritas.com \
--cc=Nitin.Jerath@veritas.com \
--cc=Rakesh.Ranjan@veritas.com \
--cc=Suraj.Singh@veritas.com \
--cc=armbru@redhat.com \
--cc=ashish.mittal@veritas.com \
--cc=ashmit602@gmail.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=jferlan@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=venkatesha.mg@veritas.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).