STRUCT DEV_DAX(9)
π struct dev_dax β¨
okay so this is a page straight out of the Kernel API Manual, and it's all about struct dev_dax β no cap, it's a whole vibe. π¦
πΈ NAME πΈ
struct dev_dax β the instance data for a subdivision of a dax region, plus the data while the device is activated in the driver. literally the little glow-up corner of a dax region that keeps its own receipts π
β¨ SYNOPSIS β¨
struct dev_dax {
struct dax_region *region;
struct dax_device *dax_dev;
u64 cached_size;
unsigned int align;
int target_node;
bool dyn_id;
int id;
struct ida ida;
struct device dev;
struct dev_pagemap *pgmap;
bool memmap_on_memory;
int nr_range;
struct dev_dax_range *ranges;
};
π Members π
okay bestie, field-by-field, and yes we're doing all of them π
regionβ parent region, the main character it belongs to π«dax_devβ core dax functionalitycached_sizeβ size of daxdev cached by fsdev_daxalignβ alignment of this instancetarget_nodeβ effective numa node if dev_dax memory range is onlineddyn_idβ is this a dynamic or statically created instanceidβ ida allocated id when the dax_region is not staticidaβ mapping id allocatordevβ device corepgmapβ pgmap for memmap setup / lifetime (driver owned)memmap_on_memoryβ allow kmem to put the memmap in the memorynr_rangeβ size of rangesrangesβ range tuples of memory used
π¦ SEE ALSO π¦
go peek at these, iykyk π
- Kernel file
./drivers/dax/dax-private.hstruct dax_region(9),struct dax_mapping(9),struct dev_dax_range(9)
and that's the whole thing, bestie β periodt π β¨
source squad, say hi: this one lives in./drivers/dax, it's dated October 2026, and the page itself isstruct dev_dax(9). π«ΆπΈ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms