nvdimm.rst (0f69403d2535ffc7200a8414cf3ca66a49b0d741) | nvdimm.rst (d3603f4c30c24b43f49bf9c1dbc93b06f7a7775d) |
---|---|
1=============================== 2LIBNVDIMM: Non-Volatile Devices 3=============================== 4 5libnvdimm - kernel / libndctl - userspace helper library 6 7linux-nvdimm@lists.01.org 8 --- 99 unchanged lines hidden (view full) --- 108to handle the case where DPA accessible via PMEM is aliased with DPA 109accessible via BLK. When that occurs a LABEL is needed to reserve DPA 110for exclusive access via one mode a time. 111 112Supporting Documents 113-------------------- 114 115ACPI 6: | 1=============================== 2LIBNVDIMM: Non-Volatile Devices 3=============================== 4 5libnvdimm - kernel / libndctl - userspace helper library 6 7linux-nvdimm@lists.01.org 8 --- 99 unchanged lines hidden (view full) --- 108to handle the case where DPA accessible via PMEM is aliased with DPA 109accessible via BLK. When that occurs a LABEL is needed to reserve DPA 110for exclusive access via one mode a time. 111 112Supporting Documents 113-------------------- 114 115ACPI 6: |
116 http://www.uefi.org/sites/default/files/resources/ACPI_6.0.pdf | 116 https://www.uefi.org/sites/default/files/resources/ACPI_6.0.pdf |
117NVDIMM Namespace: | 117NVDIMM Namespace: |
118 http://pmem.io/documents/NVDIMM_Namespace_Spec.pdf | 118 https://pmem.io/documents/NVDIMM_Namespace_Spec.pdf |
119DSM Interface Example: | 119DSM Interface Example: |
120 http://pmem.io/documents/NVDIMM_DSM_Interface_Example.pdf | 120 https://pmem.io/documents/NVDIMM_DSM_Interface_Example.pdf |
121Driver Writer's Guide: | 121Driver Writer's Guide: |
122 http://pmem.io/documents/NVDIMM_Driver_Writers_Guide.pdf | 122 https://pmem.io/documents/NVDIMM_Driver_Writers_Guide.pdf |
123 124Git Trees 125--------- 126 127LIBNVDIMM: 128 https://git.kernel.org/cgit/linux/kernel/git/djbw/nvdimm.git 129LIBNDCTL: 130 https://github.com/pmem/ndctl.git --- 642 unchanged lines hidden (view full) --- 773Why the Term "namespace"? 774^^^^^^^^^^^^^^^^^^^^^^^^^ 775 776 1. Why not "volume" for instance? "volume" ran the risk of confusing 777 ND (libnvdimm subsystem) to a volume manager like device-mapper. 778 779 2. The term originated to describe the sub-devices that can be created 780 within a NVME controller (see the nvme specification: | 123 124Git Trees 125--------- 126 127LIBNVDIMM: 128 https://git.kernel.org/cgit/linux/kernel/git/djbw/nvdimm.git 129LIBNDCTL: 130 https://github.com/pmem/ndctl.git --- 642 unchanged lines hidden (view full) --- 773Why the Term "namespace"? 774^^^^^^^^^^^^^^^^^^^^^^^^^ 775 776 1. Why not "volume" for instance? "volume" ran the risk of confusing 777 ND (libnvdimm subsystem) to a volume manager like device-mapper. 778 779 2. The term originated to describe the sub-devices that can be created 780 within a NVME controller (see the nvme specification: |
781 http://www.nvmexpress.org/specifications/), and NFIT namespaces are | 781 https://www.nvmexpress.org/specifications/), and NFIT namespaces are |
782 meant to parallel the capabilities and configurability of 783 NVME-namespaces. 784 785 786LIBNVDIMM/LIBNDCTL: Block Translation Table "btt" 787------------------------------------------------- 788 | 782 meant to parallel the capabilities and configurability of 783 NVME-namespaces. 784 785 786LIBNVDIMM/LIBNDCTL: Block Translation Table "btt" 787------------------------------------------------- 788 |
789A BTT (design document: http://pmem.io/2014/09/23/btt.html) is a stacked | 789A BTT (design document: https://pmem.io/2014/09/23/btt.html) is a stacked |
790block device driver that fronts either the whole block device or a 791partition of a block device emitted by either a PMEM or BLK NAMESPACE. 792 793LIBNVDIMM: btt layout 794^^^^^^^^^^^^^^^^^^^^^ 795 796Every region will start out with at least one BTT device which is the 797seed device. To activate it set the "namespace", "uuid", and --- 90 unchanged lines hidden --- | 790block device driver that fronts either the whole block device or a 791partition of a block device emitted by either a PMEM or BLK NAMESPACE. 792 793LIBNVDIMM: btt layout 794^^^^^^^^^^^^^^^^^^^^^ 795 796Every region will start out with at least one BTT device which is the 797seed device. To activate it set the "namespace", "uuid", and --- 90 unchanged lines hidden --- |