From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeff Garzik <jeff@garzik.org>
Subject: Xen and SCSI
Date: Tue, 20 Jun 2006 17:34:43 -0400
Message-ID: <449869F3.5020105@garzik.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Randy Thelen <rthelen@netapp.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

FWIW, I'm about to complete a domU scsi driver for Xen (initiator, aka 
front-end).  Additionally, I'm writing "the other side", the associated 
target (tunnel, aka back-end) for dom0-style kernels.

I was planning on sending it to linux-scsi for review this week, then 
figure out the best path to get it upstream.

The basic message protocol draws heavily on native SCSI RPC model, and 
by that, I mean SAM and "SMP-ish".  This allows communication with any 
number of SCSI targets/LUNs/etc. between any domU or dom0.

Reading your email earlier today, I would recommend against using the 
SCSI generic driver, unless you're doing something strange like passing 
everything through userspace.  Just put SCSI commands on the request 
queue...

	Jeff