|
xen-devel
[Xen-devel] Re: [RFC PATCH 35/35] Add Xen virtual block device driver.
|
To: |
Dave C Boutcher <boutcher@xxxxxxxxxx> |
|
Subject: |
[Xen-devel] Re: [RFC PATCH 35/35] Add Xen virtual block device driver. |
|
From: |
Mike Christie <michaelc@xxxxxxxxxxx> |
|
Date: |
Fri, 24 Mar 2006 13:04:43 -0600 |
|
Cc: |
Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, SCSI Mailing List <linux-scsi@xxxxxxxxxxxxxxx>, Jeff Garzik <jeff@xxxxxxxxxx>, Ian Pratt <ian.pratt@xxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, Chris Wright <chrisw@xxxxxxxxxxxx>, virtualization@xxxxxxxxxxxxxx, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>, Arjan van de Ven <arjan@xxxxxxxxxxxxx> |
|
Delivery-date: |
Fri, 24 Mar 2006 19:06:28 +0000 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<17444.4455.240044.724257@xxxxxxxxxxxxxxxxxxxxx> |
|
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
|
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
|
List-post: |
<mailto:xen-devel@lists.xensource.com> |
|
List-subscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
References: |
<A95E2296287EAD4EB592B5DEEFCE0E9D4B9E8A@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <4421D943.1090804@xxxxxxxxxx> <1143202673.18986.5.camel@xxxxxxxxxxxxxxxxxxxxx> <4423E853.1040707@xxxxxxxxxx> <4423F60B.6020805@xxxxxxxxxx> <1143207657.2882.65.camel@xxxxxxxxxxxxxxxxxxxxx> <4423F91F.4060007@xxxxxxxxxx> <17444.4455.240044.724257@xxxxxxxxxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Thunderbird 1.5 (X11/20060313) |
Dave C Boutcher wrote:
Jeff Garzik wrote:
Arjan van de Ven wrote:
On Fri, 2006-03-24 at 08:37 -0500, Jeff Garzik wrote:
Jeff Garzik wrote:
In fact, SCSI should make a few things easier, because the notion of
host+bus topology is already present, and notion of messaging is already
present, so you don't have to recreate that in a Xen block device
infrastructure.
Another benefit of SCSI: when an IBM hypervisor in the Linux kernel
switched to SCSI, that allowed them to replace several drivers (virt
disk, virt cdrom, virt floppy?) with a single virt-SCSI driver.
but there's a generic one for that: iSCSI
so in theory you only need to provide a network driver then ;)
Talk about lots of overhead :)
OTOH, I bet that T10 is acting at high speed, right this second, to form
a committee, and multiple sub-committees, to standardize SCSI
transported over XenBus. SXP anyone? :)
Actually SRP (which T10 has now stopped working on) fits the bill very
nicely.
Does the IBM vscsi code/SPEC follow the SRP SPEC or is it slightly
modified? We also have a SRP initiator in kernel now too. It is just not
in the drivers/scsi dir.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
Home