From: Christoph Hellwig Date: Thu, 7 Jul 2022 16:04:48 +0000 (+0200) Subject: clean up "actually guaranteed" wording X-Git-Tag: draft-hellwig-nfsv4-scsi-layout-nvme-03~3 X-Git-Url: https://www.infradead.org/git/?a=commitdiff_plain;h=cdf239308ea6f88966a33d260b8284dadffd8b26;p=users%2Fhch%2Fscsi-layout-nvme.git clean up "actually guaranteed" wording From David Black --- diff --git a/scsi_nvme_middle.xml b/scsi_nvme_middle.xml index 6a90416..82b9fc7 100644 --- a/scsi_nvme_middle.xml +++ b/scsi_nvme_middle.xml @@ -153,9 +153,11 @@ One important difference between SCSI Persistent Reservations and NVMe Reservations is that NVMe reservation keys always apply to all controllers used by a host (as indicated by the NVMe Host - Identifier) This behavior is similar to setting the ALL_TG_PT bit - when registering a SCSI Reservation key, but actually guaranteed - to work reliably. + Identifier). This behavior is analogous to setting the ALL_TG_PT + bit when registering a SCSI Reservation key, and is always supported + by NVMe Reservations, unlike the ALL_TG_PT for which SCSI support is + inconsistent and cannot be relied upon. + Registering a reservation key with a namespace creates an association between a host and a namespace. A host that is a registrant of a namespace may use any controller with which that