From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Boaz Harrosh <bharrosh@panasas.com>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: Mike Christie <michaelc@cs.wisc.edu>,
Hannes Reinecke <hare@suse.de>,
James Bottomley <James.Bottomley@suse.de>,
Konrad Rzeszutek Wilk <konrad@darnok.org>,
Douglas Gilbert <dgilbert@interlog.com>,
Joe Eykholt <jeykholt@cisco.com>,
Nicholas Bellinger <nab@linux-iscsi.org>
Subject: [PATCH 0/2] tcm/tcm_loop: Add BIDI support and XDWRITE_READ_10 emulation
Date: Wed, 15 Sep 2010 05:06:34 -0700 [thread overview]
Message-ID: <1284552394-30525-1-git-send-email-nab@linux-iscsi.org> (raw)
From: Nicholas Bellinger <nab@linux-iscsi.org>
Greetings Boaz, Tomo-san and Co,
This series adds initial support for functional bidirectional CDBs into TCM_Core
and the TCM_Loop fabric module. So far this is limited to XDWRITE_READ_10 emulation
following scsi_debug.c, but everything appears to now be functioning as expected.
This first patch adds support for BIDI operations and XDWRITE_READ_10 emulation
into TCM_Core for the individual I/O descriptor setup, memory mapping, callback
and release codepaths.
The second patch enables BIDI operations with the TCM_Loop Virtual SCSI LLD
fabric module using the updated callers.
So far this has been lightly tested on v2.6.36-rc3 HVM using custom userspace BSG
code to issue XDWRITE_READ_10 I/O into TCM_Loop LUNs using FILEIO backstores.
Support for BIDI CDBs will also extend to LIO-Target and other TCM fabric modules
in the near future.
Comments are welcome!
Signed-off-by: Nicholas A. Bellinger <nab@linux-iscsi.org>
Nicholas Bellinger (2):
tcm: Add support for BIDI operation and XDWRITE_READ_10 emulation
tcm_loop: Add DMA_BIDIRECTIONAL CDB support
drivers/target/target_core_transport.c | 282 +++++++++++++++++++++---
drivers/target/tcm_loop/tcm_loop_fabric_scsi.c | 48 +++-
include/target/target_core_base.h | 9 +-
include/target/target_core_transport.h | 10 +-
4 files changed, 297 insertions(+), 52 deletions(-)
reply other threads:[~2010-09-15 12:06 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=1284552394-30525-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=hare@suse.de \
--cc=jeykholt@cisco.com \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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).