From: Anthony Liguori <anthony@codemonkey.ws>
To: akataria@vmware.com
Cc: James Bottomley <James.Bottomley@suse.de>,
Rolf Eike Beer <eike-kernel@sf-tec.de>,
Brian King <brking@linux.vnet.ibm.com>,
"Chetan.Loke@Emulex.Com" <Chetan.Loke@Emulex.Com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"pv-drivers@vmware.com" <pv-drivers@vmware.com>,
virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH] SCSI driver for VMware's virtual HBA - V4.
Date: Wed, 09 Sep 2009 17:12:26 -0500 [thread overview]
Message-ID: <4AA8284A.3010908@codemonkey.ws> (raw)
In-Reply-To: <1252533093.24633.40.camel@ank32.eng.vmware.com>
Alok Kataria wrote:
> I see your point, but the ring logic or the ABI that we use to
> communicate between the hypervisor and guest is not shared between our
> storage and network drivers. As a result, I don't see any benefit of
> separating out this ring handling mechanism, on the contrary it might
> just add some overhead of translating between various layers for our
> SCSI driver.
>
But if you separate out the ring logic, it allows the scsi logic to be
shared by other paravirtual device drivers. This is significant and
important from a Linux point of view.
There is almost nothing vmware specific about the vast majority of your
code. If you split out the scsi logic, then you will receive help
debugging, adding future features, and improving performance from other
folks interested in this. In the long term, it will make your life
much, much easier by making the driver relevant to a wider audience :-)
> Having said that, I will like to add that yes if in some future
> iteration of our paravirtualized drivers, if we decide to share this
> ring mechanism for our various device drivers this might be an
> interesting proposition.
>
I am certainly not the block subsystem maintainer, but I'd hate to see
this merged without any attempt at making the code more reusable. If
adding the virtio layering is going to somehow hurt performance, break
your ABI, or in some way limit you, then that's something to certainly
discuss and would be valid concerns. That said, I don't think it's a
huge change to your current patch and I don't see any obvious problems
it would cause.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-09-09 22:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 1:15 [PATCH] SCSI driver for VMware's virtual HBA - V4 Alok Kataria
2009-09-09 1:26 ` Daniel Walker
2009-09-09 5:01 ` Alok Kataria
2009-09-09 5:54 ` Rolf Eike Beer
2009-09-09 16:56 ` Alok Kataria
2009-09-29 17:05 ` [Pv-drivers] " Alok Kataria
2009-09-09 21:00 ` Anthony Liguori
2009-09-09 21:51 ` Alok Kataria
2009-09-09 22:12 ` Anthony Liguori [this message]
2009-09-09 23:08 ` Christoph Hellwig
2009-09-09 23:34 ` Anthony Liguori
2009-09-09 23:54 ` Jeremy Fitzhardinge
2009-09-10 0:11 ` Anthony Liguori
2009-09-10 23:43 ` Alok Kataria
2009-09-10 23:43 ` Alok Kataria
2009-09-14 3:05 ` [Pv-drivers] " Alok Kataria
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=4AA8284A.3010908@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Chetan.Loke@Emulex.Com \
--cc=James.Bottomley@suse.de \
--cc=akataria@vmware.com \
--cc=akpm@linux-foundation.org \
--cc=brking@linux.vnet.ibm.com \
--cc=eike-kernel@sf-tec.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox