vdo_get_phy...ks_allocated(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– vdo_get_physical_blocks_allocated(9) β€” Kernel API Manual πŸ’–

okay so bestie, welcome to the Kernel API Manual page for vdo_get_physical_blocks_allocated(9). This one is a tiny little query function β€” it's giving "just tell me the count" energy, and honestly? iconic. 🫢

🌸 NAME 🌸

vdo_get_physical_blocks_allocated β€” grab the number of physical blocks currently in use by user data. πŸ’…

✨ SYNOPSIS ✨

block_count_t vdo_get_physical_blocks_allocated (const struct vdo *vdo
);

πŸŽ€ ARGUMENTS πŸŽ€

  • vdo β€” the vdo. That's it, that's the argument. No extra lore, no secret second arg. πŸ’–

πŸ”₯ RETURN πŸ”₯

It returns a block_count_t: the number of blocks allocated for user data. slay. ✨

πŸ‘‘ SEE ALSO πŸ‘‘

The kernel file to peek at is ./drivers/md/dm-vdo/vdo.c β€” and here's the full cross-ref fam, no cap:


xoxo, this page is from source/version ./drivers/md/dm-vdo, dated October 2026, and its page tag is vdo_get_phy...ks_allocated(9). πŸ’…πŸ«ΆπŸŽ€

πŸ“¦ where this page comes from