start_writing(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… start_writing β€” NAME

okay so this is start_writing(9), and yes bestie it does exactly what it says on the tin: Begin the non-duplicate write path. that's the whole vibe. short, sweet, iconic. ✨


πŸŽ€ SYNOPSIS

void start_writing (struct hash_lock *lock , struct data_vio *agent );

that's it. that's the function. two pointers and a dream. πŸ’–


🫢 ARGUMENTS

  • lock β€” the hash lock. and listen, it's currently gotta be QUERYING β€” like, that's the state it needs to be in when you call this, no cap. don't come at it in any other state. πŸ™ˆ
  • agent β€” the data_vio that's currently acting as the agent for the lock. it's the main character of this lock rn, literally. πŸ‘‘

🌈 DESCRIPTION

so here's the tea β˜•: this kicks off the non-duplicate write path for a hash lock that had no advice β€” yep, no advice, it's out here making its own decisions.

if it needs to, it picks a data_vio that has an allocation and makes it the shiny new agent. if necessary, okay? only if necessary. πŸ¦‹

then β€” and this is the slay part β€” it resumes the agent on the data_vio write path. periodt. that's the whole function. she's efficient. πŸ’…


⭐ SEE ALSO

okay this list is long long, but every single one of these is required reading, iykyk. also the kernel file lives at ./drivers/md/dm-vdo/dedupe.c β€” that's the home base, the mothership, the whole vibe. 🏠✨

fr fr, go read these. not me listing all 57 of them and you skipping to the bottom. πŸ”₯

and that's the page!! mwah πŸ’‹ this one's from the Kernel API Manual, lives in ./drivers/md/dm-vdo, and it's dated October 2026. see u in the group chat bestie πŸ«ΆπŸ“πŸ’œ

πŸ“¦ where this page comes from