wait_for_com...n_io_timeout(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… wait_for_completion_io_timeout(9) β€” Kernel API Manual πŸ’…

okay bestie, this is the Kernel API Manual page for wait_for_completion_io_timeout. The header keeps it abbreviated as wait_for_com...n_io_timeout(9) β€” iconic truncation, honestly πŸ’–

🌸 NAME 🌸

wait_for_completion_io_timeout β€” the NAME line says wait_for_completion_io_timeout - - waits for completion of a task (w/timeout) πŸ’…

✨ SYNOPSIS ✨

unsigned long wait_for_completion_io_timeout (struct completion *x ,
unsigned long timeout );

🫢 ARGUMENTS 🫢

  • x β€” holds the state of this particular completion πŸŽ€
  • timeout β€” timeout value in jiffies ⏰

πŸ’– DESCRIPTION πŸ’–

So here’s the vibe: this waits for either a completion of a specific task to be signaled or for a specified timeout to expire. The timeout is in jiffies β€” that’s the unit, bestie ✨

It is not interruptible β€” no tap-outs, periodt πŸ’€

The caller is accounted as waiting for IO (which traditionally means blkio only). That’s the accounting detail, iykyk πŸ¦‹

πŸŽ€ RETURN πŸŽ€

  • 0 β€” if timed out 😭
  • positive (at least 1, or number of jiffies left till timeout) β€” if completed πŸŽ‰πŸ‘‘

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./kernel/sched/completion.c β€” go peek, bestie:


πŸ’œ that’s the whole page, bestie β€” source/version spot is ./kernel/sched, dated October 2026, and the footer page tag is wait_for_com...n_io_timeout(9). mwah πŸ’‹

πŸ“¦ where this page comes from