From: David Disseldorp <ddiss@suse.de>
To: Roman Bolshakov <r.bolshakov@yadro.com>
Cc: Dmitry Bogdanov <d.bogdanov@yadro.com>,
Martin Petersen <martin.petersen@oracle.com>,
<target-devel@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
<linux@yadro.com>
Subject: Re: [PATCH v2] scsi: target: core: check SR field in REPORT LUNS
Date: Thu, 28 Jan 2021 21:28:56 +0100 [thread overview]
Message-ID: <20210128212856.1f1117e6@suse.de> (raw)
In-Reply-To: <YA/dSDH2NYSRi9Bi@SPB-NB-133.local>
Hi Roman,
On Tue, 26 Jan 2021 12:13:44 +0300, Roman Bolshakov wrote:
> Hi David,
>
> SELECT REPORT field can be used for vVOL (LU conglomerate) discovery and
> for well-known lun listing.
>
> The field is used by VMware ESXi:
> https://support.purestorage.com/Solutions/VMware_Platform_Guide/User_Guides_for_VMware_Solutions/Virtual_Volumes_User_Guide/vVols_User_Guide%3A_Protocol_Endpoints
>
> "PEs greatly extend the number of vVols that can be connected to an ESXi
> cluster; each PE can have up to 16,383 vVols per host bound to it
> simultaneously. Moreover, a new binding does not require a complete I/O
> rescan. Instead, ESXi issues a REPORT_LUNS SCSI command with SELECT
> REPORT to the PE to which the sub-lun is bound. The PE returns a list of
> sub-lun IDs for the vVols bound to that host. In large clusters,
> REPORT_LUNS is significantly faster than a full I/O rescan because it is
> more precisely targeted."
Interesting, thanks.
...
> With regards to bumping TCM to SPC-4, are there any objections if we
> submit a separate patch for that? Or resubmit a series with the patch?
I don't object to that. FWIW, the following crude metrics could be seen
as an argument in favour of SPC-4 versioning:
linux> git grep -ic -e "SPC4" -e "SPC-4" -- drivers/target/
drivers/target/target_core_alua.c:7
drivers/target/target_core_alua.h:5
drivers/target/target_core_device.c:1
drivers/target/target_core_fabric_lib.c:5
drivers/target/target_core_pr.c:37
drivers/target/target_core_spc.c:19
drivers/target/target_core_tmr.c:3
drivers/target/target_core_transport.c:2
drivers/target/target_core_ua.c:1
drivers/target/target_core_ua.h:1
drivers/target/target_core_xcopy.c:3
drivers/target/target_core_xcopy.h:1
linux> git grep -ic -e "SPC3" -e "SPC-3" -- drivers/target/
drivers/target/target_core_alua.c:1
drivers/target/target_core_configfs.c:14
drivers/target/target_core_pr.c:75
drivers/target/target_core_spc.c:4
drivers/target/target_core_tmr.c:1
drivers/target/target_core_transport.c:4
drivers/target/target_core_ua.c:1
Most of the SPC3 target_core_pr and target_core_configfs matches above
are debug/error messages, rather than spec references.
Cheers, David
next prev parent reply other threads:[~2021-01-28 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 10:27 [PATCH v2] scsi: target: core: check SR field in REPORT LUNS Dmitry Bogdanov
2021-01-22 22:42 ` David Disseldorp
2021-01-26 9:13 ` Roman Bolshakov
2021-01-28 20:28 ` David Disseldorp [this message]
2021-01-27 4:36 ` Martin K. Petersen
2021-01-27 14:45 ` Dmitriy Bogdanov
2021-01-28 20:47 ` Bart Van Assche
2021-02-19 13:48 ` Dmitriy Bogdanov
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=20210128212856.1f1117e6@suse.de \
--to=ddiss@suse.de \
--cc=d.bogdanov@yadro.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@yadro.com \
--cc=martin.petersen@oracle.com \
--cc=r.bolshakov@yadro.com \
--cc=target-devel@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