Re: [Qemu-devel] [PATCH v8 1/2] block/vxhs.c: Add support for a new block device type called "vxhs"

> On Mar 8, 2017, at 1:13 AM, Daniel P. Berrange wrote: > >> On Tue, Mar 07, 2017 at 05:27:55PM -0800, ashish mittal wrote: >> Thanks! There is one more input I need some help with! >> >> VxHS network library opens a fixed number of connection channels to a >> given host,

Re: [Qemu-devel] [PATCH v8 1/2] block/vxhs.c: Add support for a new block device type called "vxhs"

On 2/21/17, 5:59 AM, "Stefan Hajnoczi" <stefa...@gmail.com> wrote: On Mon, Feb 20, 2017 at 03:34:57AM -0800, ashish mittal wrote: > On Mon, Feb 20, 2017 at 3:02 AM, Stefan Hajnoczi <stefa...@gmail.com> wrote: > > On Sat, Feb 18, 2017 at 12:30:31A

Re: [Qemu-devel] [PATCH v8 1/2] block/vxhs.c: Add support for a new block device type called "vxhs"

On 2/17/17, 1:42 PM, "Jeff Cody" wrote: On Thu, Feb 16, 2017 at 02:24:19PM -0800, ashish mittal wrote: > Hi, > > I am getting the following error with checkpatch.pl > > ERROR: externs should be avoided in .c files > #78: FILE: block/vxhs.c:28:

Re: [Qemu-devel] [PATCH v6 2/2] block/vxhs.c: Add qemu-iotests for new block device type "vxhs"

On 2/13/17, 3:23 PM, "Jeff Cody" <jc...@redhat.com> wrote: On Mon, Feb 13, 2017 at 10:36:53PM +, Ketan Nilangekar wrote: > > > On 2/13/17, 8:32 AM, "Jeff Cody" <jc...@redhat.com> wrote: > > On Mon, Feb 13,

Re: [Qemu-devel] [PATCH v7 1/2] block/vxhs.c: Add support for a new block device type called "vxhs"

On 2/8/17, 2:21 PM, "Jeff Cody" wrote: On Tue, Feb 07, 2017 at 08:18:13PM -0800, Ashish Mittal wrote: > From: Ashish Mittal > > Source code for the qnio library that this code loads can be downloaded from: >

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

On 2/3/17, 1:45 AM, "Daniel P. Berrange" <berra...@redhat.com> wrote: On Thu, Feb 02, 2017 at 09:22:46PM +, Ketan Nilangekar wrote: > > On 2/2/17, 12:57 PM, "Ketan Nilangekar" <ketan.nilange...@veritas.com> wrote: >

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

On 2/2/17, 12:57 PM, "Ketan Nilangekar" <ketan.nilange...@veritas.com> wrote: On 2/2/17, 2:15 AM, "Daniel P. Berrange" <berra...@redhat.com> wrote: On Thu, Feb 02, 2017 at 10:07:28AM +, Stefan Hajnoczi wrote: > On We

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

On 2/2/17, 2:15 AM, "Daniel P. Berrange" <berra...@redhat.com> wrote: On Thu, Feb 02, 2017 at 10:07:28AM +, Stefan Hajnoczi wrote: > On Wed, Feb 01, 2017 at 11:59:53PM +0000, Ketan Nilangekar wrote: > > Patch for secure implementation in libqnio is

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

On 2/2/17, 2:07 AM, "Stefan Hajnoczi" <stefa...@gmail.com> wrote: On Wed, Feb 01, 2017 at 11:59:53PM +, Ketan Nilangekar wrote: > Patch for secure implementation in libqnio is available for review here: > > https://github.com/VeritasH

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

Patch for secure implementation in libqnio is available for review here: https://github.com/VeritasHyperScale/libqnio/pull/12 libqnio client initialization now has an option to use X.509 certificates to authenticate itself to the vxhs server. Also each client IO request now includes an

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

On 11/25/16, 5:05 PM, "Stefan Hajnoczi" <stefa...@gmail.com> wrote: On Fri, Nov 25, 2016 at 08:27:26AM +, Ketan Nilangekar wrote: > On 11/24/16, 9:38 PM, "Stefan Hajnoczi" <stefa...@gmail.com> wrote: > On Thu, Nov 24, 2016 at 11

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

On 11/24/16, 9:38 PM, "Stefan Hajnoczi" <stefa...@gmail.com> wrote: On Thu, Nov 24, 2016 at 11:31:14AM +, Ketan Nilangekar wrote: > > > On 11/24/16, 4:41 PM, "Stefan Hajnoczi" <stefa...@gmail.com> wrote: > >

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

On 11/24/16, 4:41 PM, "Stefan Hajnoczi" <stefa...@gmail.com> wrote: On Thu, Nov 24, 2016 at 05:44:37AM +, Ketan Nilangekar wrote: > On 11/24/16, 4:07 AM, "Paolo Bonzini" <pbonz...@redhat.com> wrote: > >On 23/11/2016 23:09, ashish mittal

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

se a big reason for the performance is also the HyperScale storage backend but we believe this method of IO tapping/redirecting can be leveraged by other solutions as well. Ketan > >Paolo > >> On Wed, Nov 23, 2016 at 12:25 AM, Ketan Nilangekar >> <ketan.nilange...@veritas

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

+Nitin Jerath from Veritas. On 11/18/16, 7:06 PM, "Daniel P. Berrange" <berra...@redhat.com> wrote: >On Fri, Nov 18, 2016 at 01:25:43PM +0000, Ketan Nilangekar wrote: >> >> >> > On Nov 18, 2016, at 5:25 PM, Daniel P. Berrange <berra...@redhat.c

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

> On Nov 18, 2016, at 5:25 PM, Daniel P. Berrange <berra...@redhat.com> wrote: > >> On Fri, Nov 18, 2016 at 11:36:02AM +, Ketan Nilangekar wrote: >> >> >> >> >> >>> On 11/18/16, 3:32 PM, "Stefan Hajnoczi" <stefa..

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

On 11/18/16, 3:32 PM, "Stefan Hajnoczi" wrote: >On Fri, Nov 18, 2016 at 02:26:21AM -0500, Jeff Cody wrote: >> * Daniel pointed out that there is no authentication method for taking to a >> remote server. This seems a bit scary. Maybe all that is needed here is >>

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

On 11/18/16, 3:32 PM, "Stefan Hajnoczi" wrote: >On Fri, Nov 18, 2016 at 02:26:21AM -0500, Jeff Cody wrote: >> * Daniel pointed out that there is no authentication method for taking to a >> remote server. This seems a bit scary. Maybe all that is needed here is >>

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

On 11/18/16, 12:56 PM, "Jeff Cody" wrote: >On Wed, Nov 16, 2016 at 08:12:41AM +, Stefan Hajnoczi wrote: >> On Tue, Nov 15, 2016 at 10:38 PM, ashish mittal wrote: >> > On Wed, Sep 28, 2016 at 2:45 PM, Stefan Hajnoczi >> >

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

On 11/7/16, 2:22 AM, "Stefan Hajnoczi" <stefa...@gmail.com> wrote: >On Fri, Nov 04, 2016 at 06:30:47PM +0000, Ketan Nilangekar wrote: >> > On Nov 4, 2016, at 2:52 AM, Stefan Hajnoczi <stefa...@gmail.com> wrote: >> >> On Thu, Oct 20, 2016 at 01:

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

> On Nov 4, 2016, at 2:49 AM, Stefan Hajnoczi <stefa...@gmail.com> wrote: > >> On Thu, Oct 20, 2016 at 01:31:15AM +, Ketan Nilangekar wrote: >> 2. The idea of having multi-threaded epoll based network client was to drive >> more throughput by using mu

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

> On Nov 4, 2016, at 2:52 AM, Stefan Hajnoczi <stefa...@gmail.com> wrote: > >> On Thu, Oct 20, 2016 at 01:31:15AM +, Ketan Nilangekar wrote: >> 2. The idea of having multi-threaded epoll based network client was to drive >> more throughput by using mu

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

Including the rest of the folks from the original thread. Ketan. On 10/26/16, 9:33 AM, "Paolo Bonzini" <pbonz...@redhat.com> wrote: > > >On 26/10/2016 00:39, Ketan Nilangekar wrote: >> >> >>> On Oct 26, 2016, at 12:00 AM, Paolo Bonzini <p

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

gt; wrote: > > > >> On 25/10/2016 07:07, Ketan Nilangekar wrote: >> We are able to derive significant performance from the qemu block >> driver as compared to nbd/iscsi/nfs. We have prototyped nfs and nbd >> based io tap in the past and the performance of qemu block d

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

> On Oct 24, 2016, at 4:24 PM, Paolo Bonzini <pbonz...@redhat.com> wrote: > > > >> On 20/10/2016 03:31, Ketan Nilangekar wrote: >> This way the failover logic will be completely out of qemu address >> space. We are considering use of some of our proprieta

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

Hi Stefan, 1. You suggestion to move the failover implementation to libqnio is well taken. Infact we are proposing that service/network failovers should not be handled in gemu address space at all. The vxhs driver will know and talk to only a single virtual IP. The service behind the virtual

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

Hi Jeff, Please see my comments inline. Thanks, Ketan. On 10/18/16, 12:10 PM, "Jeff Cody" wrote: >On Tue, Oct 11, 2016 at 12:56:06AM -0700, ashish mittal wrote: >> Checked in a test server to libqnio that allows to open, read, write >> to a vxhs vdisk using the qemu-io