vdo_get_slab..._start_block(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vdo_get_slab..._start_block(9) β€” from the Kernel API Manual, bestie πŸŽ€

okay so picture this: you're deep in the kernel, dm-vdo edition, and this lil function page just wants to tell you where the slab journal starts. that's it. that's the whole vibe. no cap. ✨


🌸 NAME 🌸

vdo_get_slab_journal_start_block β€” literally just gets you the physical block number of the start of the slab journal, measured relative to the start block allocator partition. she's giving "where does this thing begin," and honestly? iconic. πŸ’–


✨ SYNOPSIS ✨

physical_block_number_t vdo_get_slab_journal_start_block (const struct
slab_config *slab_config , physical_block_number_t origin );

so she takes two things and hands you back a physical_block_number_t. slay. 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • slab_config β€” the slab configuration of the VDO. yes, the whole configuration. she needs the context, okay?? main character energy only. πŸ‘‘
  • origin β€” the first block of the slab. the starting point. the beginning of the era. πŸ’«

🌈 SEE ALSO 🌈

okay these are the friends she keeps in her notes app, the whole encodings.h group chat fr fr β€” kernel file ./drivers/md/dm-vdo/encodings.h and the entire Block map entries(9) crew:

like… that's a lot of mutuals but we respect every single one of them. πŸ«‘πŸ’œ


ngl bestie, every name above is copied exactly as-is β€” no paraphrasing, no merging, no invented options. type them carefully or the vibe check will NOT pass. πŸ’€

and that's the page!! mwah πŸ’‹ this one lives in ./drivers/md/dm-vdo, dated October 2026, brought to you by the Kernel API Manual and by me, your local Unix girlie who wants you to thrive. go get that block number, queen. πŸ“πŸ§šβ€β™€οΈβ­

πŸ“¦ where this page comes from