drain_data_vio_pool(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– drain_data_vio_pool β€” from the Kernel API Manual, bestie edition πŸŽ€

okay so this one's from the Kernel API Manual (section 9, the kernel-functions section, iykyk) and honestly the name says a lot already. Let's get into it ✨


🌸 NAME 🌸

drain_data_vio_pool β€” wait asynchronously for all data_vios to be returned to the pool.

that's it, that's the whole vibe. no blocking, no sitting around, just asynchronous waiting. main character energy fr πŸ’…


✨ SYNOPSIS ✨

void drain_data_vio_pool (struct data_vio_pool *pool , struct
vdo_completion *completion );

like, literally copy-paste that, do not retype it, my heart cannot take typos in a signature 😭


πŸ¦‹ ARGUMENTS πŸ¦‹

  • pool β€” the data_vio pool. this is the pool we're draining, the whole reason we're here 🫢
  • completion β€” the completion to notify when the pool has drained. your little notification bestie that gets pinged the moment the drain is done ⭐

πŸ‘‘ SEE ALSO πŸ‘‘

the kernel file this lives in: ./drivers/md/dm-vdo/data-vio.c 🌈

and now the friend group, in the exact order the page gives them (do NOT come for me about the ordering, I don't make the rules) πŸ’€

like a whole squad of (9) pages, obsessed πŸ§šπŸ’œ


quick vibe check: the only things to hand over are pool and completion, and the function returns void β€” no return value to check, the async notification is the whole point πŸ“

and that's the page!! brought to you by the source at ./drivers/md/dm-vdo, October 2026 vintage, drain_data_vio_pool(9) flavored β€” slay, go drain your pool responsibly πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from