[nvmewin] Create Namespace with full NVM capacity
Patodiya, Ankit
Ankit.Patodiya at dell.com
Tue Mar 21 03:29:45 PDT 2017
As per 1.2.1 spec,
"NVM Capacity (NVMCAP): This field indicates the total size of the NVM allocated to this namespace. The value is in bytes. This field shall be supported if Namespace Management and Namespace Attachment commands are supported.
Note: This field may not correspond to the logical block size multiplied by the Namespace Size field. Due to thin provisioning or other settings (e.g., endurance), this field may be larger or smaller than the Namespace Size reported.
Namespace Size (NSZE): This field indicates the total size of the namespace in logical blocks. A namespace of size n consists of LBA 0 through (n - 1). The number of logical blocks is based on the formatted LBA size. This field is undefined prior to the namespace being formatted.
The size of a namespace is based on the number of logical blocks requested in a create operation, the format of the namespace, and any characteristics (e.g., endurance). The controller determines the NVM capacity allocated for that namespace. Namespaces may be created with different usage characteristics (e.g., endurance) that utilize differing amounts of NVM capacity. Namespace characteristics and the mapping of these characteristics to NVM capacity usage are outside the scope of this specification."
I am interested in creating a single namespace that uses up the entire NVM capacity so that I am not left with any unallocated NVM capacity.
However, namespace creation command takes in the number of logical blocks and not the size in bytes. What is the exact relation between NVM capacity in bytes and Namespace Size in blocks. How to incorporate the factors like endurance to get the number of blocks that such entire NVM capacity is used?
Thanks,
Ankit
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20170321/5aa0d6a9/attachment.html>
More information about the nvmewin
mailing list