NDCTL-ENABLE-REGION(1)

✨ NAME ✨

ndctl-enable-region β€” bestie, this turns on the region(s) you point at and every single descendant namespace that comes with them πŸ’–


🌸 SYNOPSIS 🌸

ndctl enable-region <region> [<options>]

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so picture this: for every PMEM range / interleave-set out there, a generic REGION device gets registered, right? and LIBNVDIMM ships a built-in driver specifically for those REGION devices πŸ‘‘

and what does that driver actually do, you ask? it's the one in charge of parsing the namespace labels, and then instantiating PMEM namespaces for each coherent set of labels. that's the whole job. it's giving label-parser main character energy and honestly? we love that for it πŸ’…


πŸŽ€ OPTIONS πŸŽ€

  • <region> β€” a regionX device name, or a region id number. use it to restrict the operation to the specified region(s). you can pass the keyword all to say "no restrictions, idc", but heads up: that's literally the same as just not passing a --region option at all πŸ™ˆ
  • -b, --bus= β€” a bus id number, or a provider string (like "ACPI.NFIT"). use it to restrict the operation to the specified bus(es). and yeah, you can pass the keyword all here to indicate the lack of any restriction, but ngl that's the exact same thing as not supplying a --bus option at all πŸ’€

Copyright Β© 2016 - 2022, Intel Corporation. License GPLv2: GNU GPL version 2 http://gnu.org/licenses/gpl.html. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.

fr fr on the NO WARRANTY thing, it's not a vibe, it's the actual legal text πŸ’œ

🌈 SEE ALSO 🌈


ndctl Β· 2026-07-07 Β· NDCTL-ENABLE-REGION(1)

and that's the whole page bestie, ily, go enable some regions πŸ’…πŸ«ΆπŸŽ€

πŸ“¦ where this page comes from