The NDD_ALIASING flag is used to indicate where pmem capacity might alias with blk capacity and require labeling. It is also used to indicate whether the DIMM supports labeling. Separate this latter capability into its own flag so that the NDD_ALIASING flag is scoped to true aliased configurations. To my knowledge aliased configurations only exist in the ACPI spec, there are no known platforms that ship this support in production. This clarity allows namespace-capacity alignment constraints around interleave-ways to be relaxed.
Showing the changes to include/linux (1 of 8 files). Show all
Unified · Split
| @@ -37,6 +37,8 @@ enum { · 36 unmodified lines | |||
| 37 | NDD_WORK_PENDING = 4, | 37 | NDD_WORK_PENDING = 4, |
| 38 | /* ignore / filter NSLABEL_FLAG_LOCAL for this DIMM, i.e. no aliasing */ | 38 | /* ignore / filter NSLABEL_FLAG_LOCAL for this DIMM, i.e. no aliasing */ |
| 39 | NDD_NOBLK = 5, | 39 | NDD_NOBLK = 5, |
| 40 | /* dimm supports namespace labels */ | ||
| 41 | NDD_LABELING = 6, | ||
| 40 | 42 | ||
| 41 | /* need to set a limit somewhere, but yes, this is likely overkill */ | 43 | /* need to set a limit somewhere, but yes, this is likely overkill */ |
| 42 | ND_IOCTL_MAX_BUFLEN = SZ_4M, | 44 | ND_IOCTL_MAX_BUFLEN = SZ_4M, |