From 9248520f22703a03695ab752228b02c1ae5acb8e Mon Sep 17 00:00:00 2001 From: Christoph Hellwig Date: Tue, 7 Jun 2022 10:05:47 +0200 Subject: [PATCH] =?utf8?q?rewrite=20the=20"Volume=20Identification"=20?= =?utf8?q?=D1=95ection?= MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Pull in the few bits of information that we actually need instead of relying on the STLR whitepaper. Signed-off-by: Christoph Hellwig --- scsi_nvme_middle.xml | 29 +++++++++++++++++++++++------ 1 file changed, 23 insertions(+), 6 deletions(-) diff --git a/scsi_nvme_middle.xml b/scsi_nvme_middle.xml index cd9b5bc..a4f078f 100644 --- a/scsi_nvme_middle.xml +++ b/scsi_nvme_middle.xml @@ -75,17 +75,34 @@ The pNFS SCSI layout uses the Device Identification VPD page (page code 0x83) from to identify the devices used by - a layout. Section 6.1.4 of lists ways - to build SCSI Device Identification descriptors from NVMe Identify - data. + a layout. Implementation using NVMe device shall use a mapping from + NVMe identifier to the SPC Device Identification VPD page that is + compatible to that defined in Section 6.1.4 of + . + + To be used as storage devices for the pNFS SCSI layout, NVMe devices MUST support either the EUI64 or NGUID value in the Identify Namespace data, as the methods based on the Serial Number for legacy devices might not be suitable for unique addressing needs and - thus MUST NOT be used. If possible NVMe devices uses as storage - devices for the pNFS SCSI layout SHOULD support the NGUID value as - it is the larger identifier. + thus MUST NOT be used. If available, the NGUID value SHOULD be used + as the larger identifier. + + + + + The pnfs_scsi_base_volume_info4 structure shall be constructed as + following: + + The "sbv_code_set" field SHALL be set to PS_CODE_SET_BINARY. + The "pnfs_scsi_designator_type" field SHALL be set to + PS_DESIGNATOR_EUI64. + The "sbv_designator" field shall contain either the NGUID or EUI64 + fields from the Identify Namespace data. + + -- 2.49.0