inode_dio_end(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… inode_dio_end(9) β€” the kernel API manual, but make it make sense

okay so bestie, we're in the <hotpink>inode_dio_end(9)</hotpink> page of the Kernel API Manual β€” yes, the (9) means it's a kernel-internals situation, iykyk 🧚


✨ NAME ✨

inode_dio_end β€” the little signal that goes "we're DONE with the direct I/O request" πŸŽ€


🌸 SYNOPSIS 🌸

void inode_dio_end (struct inode *inode );

that's it. that's the whole vibe. one inode pointer and she's out ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • inode β€” the inode the direct I/O happens on πŸ’– like, the actual file-inode thingy this whole situation is about

πŸ‘‘ DESCRIPTION πŸ‘‘

so here's the tea πŸ“: you call this once we've finished processing a direct I/O request. that's it, that's her job.

and what does she do with that moment? she wakes up the callers that are waiting for direct I/O to be quiesced 😭 like, all the little threads sitting there going "is it quiet yet?? is it quiet yet??" β€” this is the call that finally tells them yeah bestie, it's quiesced, you may go 🌈

ngl this is the counterpart to inode_dio_begin(9) β€” one opens the door, this one closes it 🫢

πŸ”₯ SEE ALSO πŸ”₯

the whole friend group, fr fr β€” all from the kernel file ./include/linux/fs.h:


and that's the page!! πŸ’œ this one lives over in ./include/linux, dated October 2026 β€” so like, slightly future-coded of her, we respect it. now go call inode_dio_end and let those waiters rest, periodt πŸ’…βœ¨

πŸ“¦ where this page comes from