From 738d266ecb58a657887839e18708188d77bc1e2e Mon Sep 17 00:00:00 2001 From: Christoph Hellwig Date: Thu, 29 Sep 2022 08:45:48 +0200 Subject: [PATCH] nits From Sorin Faibish --- scsi_nvme_middle.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/scsi_nvme_middle.xml b/scsi_nvme_middle.xml index 0d41d91..8cb15f3 100644 --- a/scsi_nvme_middle.xml +++ b/scsi_nvme_middle.xml @@ -12,7 +12,7 @@ devices. - This documents explains how to access NVM Command set Namespaces + This document explains how to access NVM Command set Namespaces exported by NVMe Controllers implementing the NVMe Base specification () using the SCSI layout type. @@ -92,7 +92,7 @@ - Methods based on the Serial Number are not be suitable for unique + Methods based on the Serial Number are not suitable for unique addressing needs and thus MUST NOT be used. @@ -186,11 +186,11 @@ In case of a non-responding client, the MDS fences the client by executing a Reservation Acquire command (refer to section 7.2 of ), with the Reservation Acquire Action - (RACQA) field to 001b (i.e., Preempt) or 010b (i.e., Preempt and + (RACQA) field set to 001b (i.e., Preempt) or 010b (i.e., Preempt and Abort), the Current Reservation Key (CRKEY) field set to the server's reservation key, the Preempt Reservation Key (PRKEY) field set to the reservation key associated with the non-responding client - and the Reservation Type (RTYPE) field set to 4h (i.e., Exclusive + and the Reservation Type (RTYPE) field set to 010b (i.e., Exclusive Access - Registrants Only Reservation). The client can distinguish I/O errors due to fencing from other @@ -235,7 +235,7 @@ apply to a client's interactions with the metadata server. However, NFSv4 clients and servers access NVMe storage devices at a lower layer than NFSv4. NFSv4 and - RPC security is not directly applicable to I/O to data servers + RPC security are not directly applicable to the I/Os to data servers using NVMe. -- 2.50.1