vdo_get_flusher_thread_id(9)

💫 vdo_get_flusher_thread_id 💫

okay so you're reading the Kernel API Manual entry for vdo_get_flusher_thread_id(9) — yes, that's the whole manual name, we're fancy like that 💅 — and bestie, it's a tiny little page but it's lowkey iconic. Let's get into it.

---

✨ NAME ✨

vdo_get_flusher_thread_id — get the ID of the thread on which flusher functions should be called. that's it. that's the whole gig 🫶

---

🌸 SYNOPSIS 🌸

thread_id_t vdo_get_flusher_thread_id (struct flusher *flusher );

like, you hand it a flusher, it hands you a thread_id_t back. balanced. symbiotic. main character energy fr fr ✨

---

🎀 ARGUMENTS 🎀

• flusher — the flusher you're querying. that's the one. the flusher in question. you're asking this flusher about itself 🦋

---

🦋 RETURN 🦋

it returns the ID of the thread which handles the flusher. one thread ID, no drama, no surprises, we love a clean return value 😌💖

---

🌈 SEE ALSO 🌈

so this function lives in the kernel file ./drivers/md/dm-vdo/flush.c and it has so many neighbors, it's giving popular girl at the group chat 👑

• assert_on_flusher_thread(9)
• as_flusher(9)
• completion_as_vdo_flush(9)
• vdo_waiter_as_flush(9)
• vdo_make_flusher(9)
• vdo_free_flusher(9)
• finish_notification(9)
• flush_packer_callback(9)
• increment_generation(9)
• notify_flush(9)
• flush_vdo(9)
• check_for_drain_complete(9)
• vdo_complete_flushes(9)
• vdo_dump_flusher(9)
• initialize_flush(9)
• vdo_launch_flush(9)
• release_flush(9)
• vdo_complete_flush_callback(9)
• select_bio_queue(9)
• vdo_complete_flush(9)
• vdo_drain_flusher(9)
• vdo_resume_flusher(9)

that's the whole friend group, go say hi 🧚💜

---

ngl there's no DESCRIPTION section here and no warnings, no bugs, no exit statuses — this page is short and sweet and we respect that. no cap.

---

and that's a wrap, bestie!! this whole thing comes from the source ./drivers/md/dm-vdo, dated October 2026, and it's literally just vdo_get_flusher_thread_id(9) doing her little thing. slay, periodt, go read flush.c 💖🎀⭐