I'm assuming it means over provisioning or something like that?
NVMe Reservations is functionally like SCSI-3 Persistent Reservations and may be used to provide capabilities utilized by two or more hosts to coordinate access to a shared namespace. An NVMe Reservation on a namespace restricts hosts access to that namespace. For example, VMware ESXi when supported by driver could use NVMe Reservations to support Microsoft Windows Server Failover Clustering with VMs.
An NVMe Reservation requires an association between a host and a namespace. Each controller in a multi-path I/O and namespace sharing environment is associated with exactly one host as shown in the example in Figure 6. A host may be associated with multiple...
I'm assuming it means over provisioning or something like that?
NVMe Reservations is functionally like SCSI-3 Persistent Reservations and may be used to provide capabilities utilized by two or more hosts to coordinate access to a shared namespace. An NVMe Reservation on a namespace restricts hosts access to that namespace. For example, VMware ESXi when supported by driver could use NVMe Reservations to support Microsoft Windows Server Failover Clustering with VMs.
An NVMe Reservation requires an association between a host and a namespace. Each controller in a multi-path I/O and namespace sharing environment is associated with exactly one host as shown in the example in Figure 6. A host may be associated with multiple controllers by registering the same Host ID with each controller it is associated with.