diff options
| author | djbw <dokuwiki@localhost> | 2020-05-02 00:32:56 +0000 |
|---|---|---|
| committer | Konstantin Ryabitsev <konstantin@linuxfoundation.org> | 2024-09-26 14:36:55 -0400 |
| commit | 7ef00666e198de3805527a6e95483d921b355566 (patch) | |
| tree | c5b6523a79f82a465fc2f9e888fce785c73dd1f4 | |
| parent | 30f5b9014187068f7d0b332f65b1c91995607f1a (diff) | |
| download | nvdimm-7ef00666e198de3805527a6e95483d921b355566.tar.gz | |
2mib_fs_dax:
| -rw-r--r-- | source/2mib_fs_dax.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/source/2mib_fs_dax.txt b/source/2mib_fs_dax.txt index e64ce41..3e25e37 100644 --- a/source/2mib_fs_dax.txt +++ b/source/2mib_fs_dax.txt @@ -41,7 +41,7 @@ We can find the alignment of the persistent memory namespaces by looking at /pro Our namespace in this case begins at 5 GiB (0x1 4000 0000), which is 2 MiB (0x20 0000) aligned. -It is recommend to use raw devices and create multiple namespaces if the system configuration calls for persistent memory to be provisioned into smaller volumes. This is because namespace alignment is enforced at namespace creation time whereas partitions need to be created by tooling that is careful to align both the start of the namespace and the start of partitions. +It is recommend to use raw devices and create multiple namespaces if the system configuration calls for persistent memory to be provisioned into smaller volumes. This is because namespace alignment is enforced at namespace creation time whereas partitions need to be created by tooling that is careful to align both the start of the namespace and the start of partitions. Long term the pmem device partition is scheduled for deprecation in favor of requiring namespaces for all provisioning. Instead, if we create any partitions on top of our PMEM namespace, we must ensure that those partitions are likewise 2 MiB aligned. By default fdisk will create partitions that are 1 MiB (2048 sector) aligned from the start of the parent block device: |