trace_blkdev_zone_mgmt(9)
π trace_blkdev_zone_mgmt(9) β a Kernel API Manual moment
okay so bestie, welcome to trace_blkdev_zone_mgmt(9) π we're hanging out in the Kernel API Manual today and honestly? this one is niche but iconic. it's the trace event that fires when somebody does a zone management operation across a whole range of zones. zoned storage girlies rise π¦
β¨ SYNOPSIS β¨
void trace_blkdev_zone_mgmt (struct bio *bio , sector_t nr_sectors );
like, that's the whole signature. two args. no notes. π
πΈ ARGUMENTS πΈ
bioβ the block IO operation that got sent down to the device. this is the actual request doing the thing, okurrr πnr_sectorsβ how many sectors this operation is affecting. it's not just a random number bestie, it's literally the size of the zone range (more on that in a sec π)
π₯ DESCRIPTION π₯
so what it does: it executes a zone management operation on a specified range of zones. that range is encoded in nr_sectors. and here's the part that will get you at the vibe check β nr_sectors has to be a multiple of the zone size. not "should be". has to be. periodt π
so yeah, no cap, that's the whole deal. the range lives in the sector count, and if it's not zone-size-aligned then you're not matching the contract, bestie. don't come for me, that's just what the page says π
π¦ SEE ALSO π¦
this section is a whole group chat of trace events lmaooo, but they all live in the kernel file ./include/trace/events/block.h β go say hi π«Ά
trace_block_touch_buffer(9)trace_block_dirty_buffer(9)trace_block_rq_requeue(9)trace_block_rq_complete(9)trace_block_rq_error(9)trace_block_rq_tag_wait(9)trace_block_rq_insert(9)trace_block_rq_issue(9)trace_block_rq_merge(9)trace_block_io_start(9)trace_block_io_done(9)trace_block_bio_complete(9)trace_block_bio_backmerge(9)trace_block_bio_frontmerge(9)trace_block_bio_queue(9)trace_block_getrq(9)trace_blk_zone_append_update_request_bio(9)trace_block_plug(9)trace_block_unplug(9)trace_block_split(9)trace_block_bio_remap(9)trace_block_rq_remap(9)
quick reminder: every single one of those has a (9) on it for a reason, they're all manpage girlies too. iykyk π
and that's the page bestie!! β¨ it's sourced from ./include/trace/events and the version/date stamp on the whole thing is October 2026, so likeβ¦ future-coded of it honestly π mwah, go read your tracepoints ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms