From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
To: nab@linux-iscsi.org
Cc: fujita.tomonori@lab.ntt.co.jp, linux-scsi@vger.kernel.org,
brking@linux.vnet.ibm.com, lxie@us.ibm.com, rcjenn@us.ibm.com,
michaelc@cs.wisc.edu, James.Bottomley@HansenPartnership.com,
joel.becker@oracle.com
Subject: Re: tcm IBMVSCSIS driver
Date: Tue, 2 Nov 2010 07:20:29 +0900 [thread overview]
Message-ID: <20101102071513A.fujita.tomonori@lab.ntt.co.jp> (raw)
In-Reply-To: <1288648016.7708.42.camel@haakon2.linux-iscsi.org>
On Mon, 01 Nov 2010 14:46:56 -0700
"Nicholas A. Bellinger" <nab@linux-iscsi.org> wrote:
> On Mon, 2010-11-01 at 21:56 +0900, FUJITA Tomonori wrote:
> > On Sat, 30 Oct 2010 16:05:43 -0700
> > "Nicholas A. Bellinger" <nab@linux-iscsi.org> wrote:
> >
> > > One final question in that regard is in your ibmvscsis_queuecommand()
> > > code, only INQUIRY, REPORT_LUNS, and MODE_SENSE need to be handled
> > > specially for other non Linux VIO SRP Initiator guests on the other
> > > end..
> >
> > INQUIRY and REPORT_LUNS need the special responses. Otherwise the
> > initiators can't see the logical units.
> >
>
> There also appears to be a bunch of magic bits set for MODE_SENSE as
> well and seems to indicate a hard requirement for legacy non linux
> guests, yes..?
No, see ibmvio.c in tgt's user space code.
> Also wrt to the internal REPORT_LUNs emuation, is it just the LUN
> encoding that is specific to ibmvscsis..? I am wondering if can just
> add a operation TCM fabric module TFO op for individual struct
> se_lun->unmapped_lun -> REPORT_LUN payload encode, and drop this
> internal emulation code.
Yeah.
next prev parent reply other threads:[~2010-11-01 22:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 5:43 tcm IBMVSCSIS driver FUJITA Tomonori
2010-10-30 23:05 ` Nicholas A. Bellinger
2010-11-01 12:56 ` FUJITA Tomonori
2010-11-01 21:46 ` Nicholas A. Bellinger
2010-11-01 22:20 ` FUJITA Tomonori [this message]
2010-11-01 22:37 ` 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=20101102071513A.fujita.tomonori@lab.ntt.co.jp \
--to=fujita.tomonori@lab.ntt.co.jp \
--cc=James.Bottomley@HansenPartnership.com \
--cc=brking@linux.vnet.ibm.com \
--cc=joel.becker@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=lxie@us.ibm.com \
--cc=michaelc@cs.wisc.edu \
--cc=nab@linux-iscsi.org \
--cc=rcjenn@us.ibm.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.