All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Randy Thelen <rthelen@netapp.com>
Cc: xen-devel@lists.xensource.com
Subject: Xen and SCSI
Date: Tue, 20 Jun 2006 17:34:43 -0400	[thread overview]
Message-ID: <449869F3.5020105@garzik.org> (raw)

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

             reply	other threads:[~2006-06-20 21:34 UTC|newest]

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

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=449869F3.5020105@garzik.org \
    --to=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.