From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Vladislav Bolkhovitin <vst@vlnb.net>
Cc: Hannes Reinecke <hare@suse.de>,
lsf10-pc@lists.linuxfoundation.org,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [LSF/VM TOPIC] Handling of invalid requests in virtual HBAs
Date: Tue, 13 Apr 2010 13:45:20 -0700 [thread overview]
Message-ID: <1271191520.32337.77.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <4BC4C4C9.70103@vlnb.net>
On Tue, 2010-04-13 at 23:23 +0400, Vladislav Bolkhovitin wrote:
> Nicholas A. Bellinger, on 04/13/2010 10:37 PM wrote:
> > On Tue, 2010-04-13 at 21:09 +0400, Vladislav Bolkhovitin wrote:
> >> LIO doesn't support 1 to many pass-through devices sharing, so SCST in
> >> the only option.
> >
> > Sorry, but this statement about your perceived limitiations wrt TCM/LIO
> > is completely incorrect.
> >
> > Using a single passthrough backstore device (eg: plain /dev/sdX) with
> > TCM/pSCSI (or any TCM subsystem plugin) has been supported since the
> > dawn of time to allow for any number of TCM_Loop Virtual SAS Ports with
> > SG_IO going into KVM Guest. The same is also true for LIO-Target
> > (iSCSI) and TCM_FC (FCoE) ports as well regardless of TCM subsystem
> > backstore.
> >
> > Perhaps you would be so kind to provide a TCM/LIO source code reference
> > from where you came up with this make-believe notion..?
>
> I've just rechecked with the latest
> git://git.kernel.org/pub/scm/linux/kernel/git/nab/lio-core-2.6.git and
> still wasn't able to find in LIO required pieces of functionality to
> support 1 to many pass-through. I see only code for non-enforced 1 to 1
> pass-through (single initiator only). You can use with it more
> initiators only as the SCSI violation, from pointing on which I started
> my participation in this discussion.
>
Sorry, but listing the path to my git tree on k.o is not the same as
citing a actual TCM/LIO source+line reference.
> Particularly, I can't see the code, which in pass-through mode upon
> receive of RESERVE command sends it also to the backend device, if
> necessary (i.e. only the first time), and then sends RELEASE command to
> the device upon the reservation holder removal. Could you point me on
> the *exact* code which implements that?
>
Again, since *you* are the one making a claim, *you* are the one
expected to back it up with a concrete code reference and example
scenario. Please, do the leg-work yourself wrt TCM SPC-3 persisetent
reservations and legacy SPC-2 reservations instead of expecting me to do
the actual work for you to verify your own fanciful claims about target
mode, seriously..
So, short of you being able to produce a response that is concrete and
human-readable, your claim will once again be dismissed as generic
hand-waving.
--nab
next prev parent reply other threads:[~2010-04-13 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 8:15 [LSF/VM TOPIC] Handling of invalid requests in virtual HBAs Hannes Reinecke
2010-04-02 5:33 ` Nicholas A. Bellinger
2010-04-08 13:44 ` Hannes Reinecke
2010-04-10 23:50 ` Nicholas A. Bellinger
2010-04-10 15:31 ` Vladislav Bolkhovitin
2010-04-13 8:56 ` Hannes Reinecke
2010-04-13 17:09 ` Vladislav Bolkhovitin
2010-04-13 18:37 ` Nicholas A. Bellinger
2010-04-13 19:23 ` Vladislav Bolkhovitin
2010-04-13 20:45 ` Nicholas A. Bellinger [this message]
2010-04-14 12:59 ` Vladislav Bolkhovitin
2010-04-14 13:49 ` Nicholas A. Bellinger
2010-05-10 3:16 ` FUJITA Tomonori
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=1271191520.32337.77.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf10-pc@lists.linuxfoundation.org \
--cc=vst@vlnb.net \
/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