linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: stgt-devel <stgt@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	Mike Christie <michaelc@cs.wisc.edu>
Cc: James Bottomley <James.Bottomley@suse.de>,
	Douglas Gilbert <dgilbert@interlog.com>,
	Nicholas Bellinger <nab@linux-iscsi.org>
Subject: [PATCH 0/2] [tgt]: Add proper SG_IO struct cmd CDB passthrough
Date: Mon, 17 May 2010 22:12:54 -0700	[thread overview]
Message-ID: <1274159574-6053-1-git-send-email-nab@linux-iscsi.org> (raw)

From: Nicholas Bellinger <nab@linux-iscsi.org>

Greetings Tomo and Mike,

These are two patches to allow the STGT SG_IO backstore to function using a
new struct scsi_cmd->sg_iovec member with sg_io_hdr->iovec_count=1, and to update
usr/scsi.c:scsi_cmd_perform() to allow for a hand off incoming descriptors into the
struct device_type_template->cmd_passthrough() function pointer.

I initially updated usr/sbc.c to set sbc_rw() as it's CDB passthrough function for
TYPE_DISK, but the logic should apply to any device types *_rw() functions.  Please let
me know if this makes sense, and I will look at updating the other stgt device types.

So far with this patch, I am able to successfully mkfs new iSCSI TYPE_DISK LUNS with
Open-iSCSI to the userspace STGT iSCSI fabric module + SG_IO into kernel level TCM_Loop
virtual iSCSI target ports on a x86 HVM, and bulk 512KB DATA_SG_IO payloads between STGT
and TCM_Loop are now functioning as expected.

There is one unresolved issue that I ran into while running initially with TCM_Loop
and struct scsi_device->max_sectors=256.  SG_IO writes larger than the
struct scsi_device->max_sectors are being returned with -EINVAL, but it appears that
the CHECK_CONDITION is not actually being propigated back into STGT/iSCSI.

After increasing the TCM_Loop ports to struct scsi_device->max_sectors=1024 following
the Open-iSCSI Initiator default, the 512KB paylods begin work as expected.  I will need
to have a look at the case for CDB length > max_sectors, which means that bs_sg.c getting
the correct scsi_status and sense data out of the kernel might still need more work.

In the mean time, please have a look at applying these patches.

Best,

Signed-off-by: Nicholas A. Bellinger <nab@linux-iscsi.org>

Nicholas Bellinger (2):
  [tgt]: Add proper CDB passthrough for SG_IO backstores
  [tgt]: Add support for SG_IO CDB passthrough in scsi_cmd_perform()

 usr/bs_sg.c     |   31 ++++++++++++++++++++++++-------
 usr/sbc.c       |    1 +
 usr/scsi.c      |   11 +++++++++++
 usr/scsi_cmnd.h |    4 ++++
 usr/tgtd.h      |    2 ++
 5 files changed, 42 insertions(+), 7 deletions(-)


             reply	other threads:[~2010-05-18  2:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18  5:12 Nicholas A. Bellinger [this message]
2010-05-18  4:39 ` [PATCH 0/2] [tgt]: Add proper SG_IO struct cmd CDB passthrough FUJITA Tomonori
2010-05-18  8:01   ` Nicholas A. Bellinger
2010-05-27 15:59 ` Nicholas A. Bellinger

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=1274159574-6053-1-git-send-email-nab@linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=James.Bottomley@suse.de \
    --cc=dgilbert@interlog.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=stgt@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).