All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Randy Thelen <rthelen@netapp.com>, xen-devel@lists.xensource.com
Subject: Re: Xen and SCSI
Date: Tue, 20 Jun 2006 18:38:49 -0500	[thread overview]
Message-ID: <44988709.80203@us.ibm.com> (raw)
In-Reply-To: <449869F3.5020105@garzik.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

      parent reply	other threads:[~2006-06-20 23:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20 21:34 Xen and SCSI Jeff Garzik
2006-06-20 23:25 ` FUJITA Tomonori
2006-06-20 23:38 ` Anthony Liguori [this message]

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=44988709.80203@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=jeff@garzik.org \
    --cc=rthelen@netapp.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.