From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arjan van de Ven Subject: Re: [RFC PATCH 35/35] Add Xen virtual block device driver. Date: Fri, 24 Mar 2006 14:40:56 +0100 Message-ID: <1143207657.2882.65.camel@laptopd505.fenrus.org> References: <4421D943.1090804@garzik.org> <1143202673.18986.5.camel@localhost.localdomain> <4423E853.1040707@garzik.org> <4423F60B.6020805@garzik.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:27342 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S1422787AbWCXNlN (ORCPT ); Fri, 24 Mar 2006 08:41:13 -0500 In-Reply-To: <4423F60B.6020805@garzik.org> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Jeff Garzik Cc: Alan Cox , Ian Pratt , Anthony Liguori , Chris Wright , virtualization@lists.osdl.org, xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org, Ian Pratt , ian.pratt@cl.cam.ac.uk, SCSI Mailing List 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 ;)