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 v2 0/2] tcm/tcm_loop: Add BIDI-COMMAND support
Date: Wed, 15 Sep 2010 15:41:43 -0700 [thread overview]
Message-ID: <1284590503-6210-1-git-send-email-nab@linux-iscsi.org> (raw)
From: Nicholas Bellinger <nab@linux-iscsi.org>
Greetings Boaz and Co,
This is the rebased TCM Core + TCM_Loop module BIDI-COMMAND v2 patch series to
address Boaz's comments about the proper usage of DMA_BIDIRECTIONAL within
TCM Core and TCM_Loop and his other points. I have already pushed the follow up
patches into lio-core-2.6.git/lio-4.0, and this is a follow up series for Boaz
to add comments w/o the original incorrect DMA_BIDIRECTIONAL usage in the v1 code.
So far this has been tested with the same custom XDWRITE_READ_10 BSG userspace
code as the v1 patch and things are functioning as expected so far. I will also
be testing with an BIDI capable sg_raw patch from Doug Gilbert. (Thanks Doug!)
Many thank go to Boaz for sharing his knowledge of BIDI for adding proper support
into TCM Core and TCM_Loop code!
Best,
Signed-off-by: Nicholas A. Bellinger <nab@linux-iscsi.org>
Nicholas Bellinger (2):
tcm: Add support for BIDI-COMMANDS and XDWRITE_READ_10 emulation
tcm_loop: Add BIDI-COMMAND CDB support
drivers/target/target_core_pr.c | 3 +-
drivers/target/target_core_transport.c | 278 ++++++++++++++++++++----
drivers/target/tcm_loop/tcm_loop_fabric_scsi.c | 47 +++-
include/target/target_core_base.h | 10 +-
include/target/target_core_transport.h | 10 +-
5 files changed, 288 insertions(+), 60 deletions(-)
reply other threads:[~2010-09-15 22:41 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=1284590503-6210-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).