From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Xen and SCSI Date: Tue, 20 Jun 2006 18:38:49 -0500 Message-ID: <44988709.80203@us.ibm.com> References: <449869F3.5020105@garzik.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <449869F3.5020105@garzik.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeff Garzik Cc: Randy Thelen , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hi Jeff, Jeff Garzik wrote: > 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. Neat! Is it a standard XenBus device? Does it use the existing blkfront/blkback ring queue? Do you have a sneak peak of the code you could possible point us to? REgards, Anthony Liguori > 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 > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel