libnvme(9)
β¨ NAME β¨
okay so welcome to the libnvme(9) API Manual page for struct nvme_fdp_config_desc β aka the FDP Configuration Descriptor. That's the name, that's the vibe, and it's literally giving exactly what it says on the tin π
β¨
π¦ SYNOPSIS π¦
bestie, here's the shape of it β and yes, every single field is staying exactly where it belongs, no cap:
struct nvme_fdp_config_desc {
__le16 size;
__u8 fdpa;
__u8 vss;
__le32 nrg;
__le16 nruh;
__le16 maxpids;
__le32 nnss;
__le64 runs;
__le32 erutl;
__u8 rsvd28[36];
struct nvme_fdp_ruh_desc ruhs[];
};
π Members π
now for the member-by-member vibe check β every field, zero skips, fr fr π«Ά
sizeβ Descriptor size. iconic little size field behavior πfdpaβ FDP Attributes (enum nvme_fdp_config_fdpa). yes, the enum name stays, we don't play about it πvssβ Vendor Specific Size. vendor-specific and valid β¨nrgβ Number of Reclaim Groups. count 'em πΈnruhβ Number of Reclaim Unit Handles. more counting, we love to see it πmaxpidsβ Max Placement Identifiers. the max, literally πnnssβ Number of Namespaces Supported. namespaces got support π¦runsβ Reclaim Unit Nominal Size. nominal size era πerutlβ Estimated Reclaim Unit Time Limit. estimated, not guessed β okay maybe estimated πrsvd28β Reserved. it's reserved, bestie, leave it alone πruhsβ Reclaim Unit Handle descriptors (struct nvme_fdp_ruh_desc). descriptors within descriptors, we love a nested moment π§
lowkey this whole page is just the struct and its members, and that's the point. no extra lore, no invented behavior, just the facts in a cute little group chat format π
that's the whole page, bestie! this was struct nvme_fdp_config_desc from libnvme(9), dated October 2026 β mwah ππ
π¦ where this page comes from
- arch rolling: nvme-cli 3.2-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms