DAXCTL-ONLINE-MEMORY(1)

✨ DAXCTL-ONLINE-MEMORY ✨

okay so bestie, welcome to the daxctl-online-memory page from the daxctl manual 💖 this is the one that actually turns your device's memory ON, and honestly it's giving "flip the switch, light it up" energy 🔥

🌸 NAME 🌸

daxctl-online-memory — online the memory for a device that's chillin' in system-ram mode 🫶

🦋 SYNOPSIS 🦋

daxctl online-memory <dax0.0> [<dax1.0>...<daxY.Z>] [<options>]

💅 EXAMPLES 💅

• Reconfigure dax0.0 into system-ram mode, but like… don't online the memory yet (we're being patient, we're being mysterious ✨)

# daxctl reconfigure-device --mode=system-ram --no-online --human dax0.0
{
  "chardev":"dax0.0",
  "size":"7.87 GiB (8.45 GB)",
  "target_node":2,
  "mode":"system-ram"
}

• Now online that memory separately, main character style 👑

# daxctl online-memory dax0.0
dax0.0: 62 new sections onlined
onlined memory for 1 device

• And here's the vibe when some sections were already online (she's been here before, no biggie):

# daxctl online-memory dax0.0
dax0.0: 1 section already online
dax0.0: 61 new sections onlined
onlined memory for 1 device

---

🎀 DESCRIPTION 🎀

So what does it actually do? It onlines the memory sections tied to a device that's already been converted into system-ram mode 💖 If one or more blocks are already online, it prints a little message about them and then tries to online whatever blocks are left. No drama, no cap.

This command is the complement to daxctl-reconfigure-device — specifically when you ran that with the --no-online option to skip onlining memory sections right after reconfiguring. In those scenarios the memory can be onlined later on using daxctl-online-memory. Literally the "we'll do it later" bestie of the family 🫶

💜 OPTIONS 💜

• -r, --region= — restrict the operation to devices belonging to the specified region(s). A device-dax region is a contiguous range of memory that hosts one or more /dev/daxX.Y devices, where X is the region id and Y is the device instance id. (iykyk 🧚)
• --no-movable — --movable is the default. This can be overridden to online new memory such that it is not movable. That means any allocation can potentially be served from this memory — which, heads up, may preclude subsequent removal 😭⚠️ With the --movable behavior (which is default), kernel allocations will not consider this memory, and it will be reserved for application use. so yeah, pick your fighter 💅
• -u, --human — by default the command outputs machine-friendly raw-integer data. With this flag instead, numbers representing storage size get formatted as human readable strings with units, and other fields get converted to hexadecimal strings. much easier on the eyeballs, ngl 👀✨
• -v, --verbose — emit more debug messages 🐛🔍

🌈 COPYRIGHT 🌈

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. 🫶

⭐ SEE ALSO ⭐

daxctl-reconfigure-device(1),daxctl-offline-memory[1] 💖

---

okay that's the whole page, go online that memory bestie, you got this 🌸👑

sign-off szn: this page is from daxctl, dated 2026-06-30, and yeah — that's the DAXCTL-ONLINE-MEMORY(1) energy, periodt 💅🎀