vdo_waitq_no..._all_waiters(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

Okay so this is the vdo_waitq_no..._all_waiters(9) page from the Kernel API Manual, and the main character is vdo_waitq_notify_all_waiters. Bestie, it does exactly what it says: it notifies all the entries waiting in a waitq. Like, all of them. No cap. πŸ’…

🌸 SYNOPSIS 🌸

void vdo_waitq_notify_all_waiters (struct vdo_wait_queue *waitq ,
       vdo_waiter_callback_fn callback , void *context );

πŸŽ€ ARGUMENTS πŸŽ€

  • waitq β€” the vdo_wait_queue that’s holding the waiters you wanna notify. She’s the main character here.
  • callback β€” the function you call to notify each waiter, or NULL if you want to invoke the callback field that’s registered in each waiter instead.
  • context β€” the context you pass along to the callback function. It’s giving β€œplus-one to the callback party.” ✨

πŸ’… DESCRIPTION πŸ’…

So the vibe is: this function notifies all the entries waiting in a waitq to continue execution by invoking a callback function on each of them in turn. One by one, bestie. 🫢

And here’s the important little detail: the waitq is copied and emptied before invoking any callbacks. So only the waiters that were in the waitq at the start of the call will be notified. That’s the rule, periodt. πŸ”₯

πŸ”₯ SEE ALSO πŸ”₯


🫢 cute little sign-off: source/version is ./drivers/md/dm-vdo, date is October 2026, and the page is vdo_waitq_no..._all_waiters(9). Bye bestie, go notify those waiters πŸ’–
πŸ“¦ where this page comes from