STRUCT DAX_DEVICE(9)

✨ struct dax_device(9) ✨

okay so we're deep in the Kernel API Manual bestie, and today's main character is struct dax_device — the anchor object for dax services 🫶 no cap, it's literally the thing everything else hangs off of.

---

💖 NAME 💖

struct dax_device — anchor object for dax services. that's it. that's the vibe. it holds shit together 💅

---

🌸 SYNOPSIS 🌸

struct dax_device {
    struct inode inode;
    struct cdev cdev;
    void *private;
    unsigned long flags;
    const struct dax_operations *ops;
    void *holder_data;
    const struct dax_holder_operations *holder_ops;
 };

like, look at it. seven fields. absolutely iconic layout, not a single wasted line 🔥

---

🎀 Members 🎀

each one gets its own little moment, as it deserves:

• inode — the core vfs inode, lowkey the foundation of the whole thing 💜
• cdev — the optional character interface for "device dax" — optional!! it's giving work-life balance ✨
• private — the dax driver's own private data, i.e. the driver's diary, hands off 🙈
• flags — state and boolean properties. yes bestie, all the little yes/no vibes live here 🦋
• ops — operations for this device. this is the actual to-do list 👑
• holder_data — holder of a dax_device: could be a filesystem or a mapped device, so it's flexible fr fr 🌈
• holder_ops — operations for the inner holder. inner. holder. it's nested, it's layered, it's highkey cute 🎀

---

🌟 SEE ALSO 🌟

go touch grass in the kernel source, here's your reading list:

• Kernel file ./drivers/dax/super.c
• fs_dax_get_by_bdev(9)
• fs_put_dax(9)
• fs_dax_get(9)
• dax_direct_access(9)
• dax_set_ops(9)
• dax_holder(9)
• inode_dax(9)

all of them are a slay, read them all, iykyk 💀✨

---

and that's the page!! sourced from ./drivers/dax, dated October 2026, sitting pretty in the Kernel API Manual — mwah, go forth and anchor your dax services, bestie 💖🎀🦋