trace_block_split(9)

📦 version 7.3.1, in nixpkgs unstable

💅 trace_block_split(9) — a Kernel API Manual moment

okay so bestie, welcome to the Kernel API Manual page for trace_block_split(9) — this is the group chat where we talk about splitting one bio struct into two bio structs. no cap, that's literally the whole vibe. 🦋

✨ NAME ✨

trace_block_split — split a single bio struct into two bio structs 💫

🌸 SYNOPSIS 🌸

void trace_block_split (struct bio *bio , unsigned int new_sector );

that's it. that's the whole signature. iconic. 🎀

🫶 ARGUMENTS 🫶

  • bio — the block operation that's getting split. it's the main character here, lowkey the one going through it 😭
  • new_sector — the starting sector for the new bio. like, where the freshly-made baby bio begins its life ✨

💜 DESCRIPTION 💜

so here's the tea: the bio request bio needs to be split into two bio requests. the way that this works is the newly created bio request starts at new_sector — that's its whole starting point, fr fr.

and why would anyone even do this, you ask? because sometimes hardware is dramatic and has limitations, bestie. like, an operation might be crossing device boundaries in a RAID system 🙈 and the hardware's just not gonna deal with that. so we split. and that's valid. the split may be required due to exactly that kind of hardware limitation, no more, no less. 💅

⚠️ quick vibe check: this is a tracing hook — the split being described is about the operation crossing device boundaries in a RAID system and other hardware limits, so don't go inventing new reasons, iykyk.

🔥 SEE ALSO 🔥

kernel file ./include/trace/events/block.h and honestly the whole friend group:

okay that's the whole page, you ate that 🍓 go forth and split ur bios responsibly, bestie 🌈💖

— signed off with love from the <rainbow>./include/trace/events</rainbow> corner of the kernel tree, dated October 2026 🧚‍♀️⭐ (that's the source and the date, so you know it's legit 👑)

📦 where this page comes from