From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: James Bottomley <James.Bottomley@suse.de>,
Douglas Gilbert <dgilbert@interlog.com>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Boaz Harrosh <bharrosh@panasas.com>,
Nicholas Bellinger <nab@linux-iscsi.org>
Subject: [PATCH 0/2] scsi/scsi_debug: Add missing scsi.h defs and XDWRITEREAD_32 support
Date: Tue, 21 Sep 2010 22:50:40 -0700 [thread overview]
Message-ID: <1285134640-7720-1-git-send-email-nab@linux-iscsi.org> (raw)
From: Nicholas Bellinger <nab@linux-iscsi.org>
Hi Doug and James,
Attached are two patches for Linux/SCSI that I ended up needing to allow the
simple XDWRITEREAD_32 passthrough into TCM/pSCSI -> struct request -> SCSI Midlayer
in recent lio-core-2.6.git/lio-4.0 commits.
The first adds some missing SPC-4 CDB and MAINTENANCE_[IN,OUT] +
VARIABLE_LENGTH_CMD service actions to include/scsi/scsi.h. These
are used by TCM Core code and pieces of this patch have been posted
here for the RFC before:
http://marc.info/?l=linux-scsi&m=128316041105964&w=2
The second adds XDWRITEREAD_32 emulation to scsi_debug, which
is pretty quite simple because everything we need is already
handled by XDWRITEREAD_10. 8-)
This has been tested using 'sgv4_xdwriteread -e' with TCM_Loop ->
TCM/pSCSI -> scsi_debug 32-byte BIDI-COMMAND CDB passthrough on
v2.6.36-rc4.
Thanks!
Signed-off-by: Nicholas A. Bellinger <nab@linux-iscsi.org>
Nicholas Bellinger (2):
scsi: Add missing SPC-4 CDB and MAINTENANCE_[IN,OUT] and
VARIABLE_LENGTH_CMD service actions
scsi_debug: Add XDWRITEREAD_32 support
drivers/scsi/scsi_debug.c | 3 +++
include/scsi/scsi.h | 28 ++++++++++++++++++++++++++++
2 files changed, 31 insertions(+), 0 deletions(-)
--
1.7.3
reply other threads:[~2010-09-22 5:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1285134640-7720-1-git-send-email-nab@linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=James.Bottomley@suse.de \
--cc=bharrosh@panasas.com \
--cc=dgilbert@interlog.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).