write_bin(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… write_bin(9) β€” the Kernel API Manual glow-up ✨

okay so bestie, welcome to the write_bin page, like the actual kernel API manual, and we're about to make it make sense fr fr 🫢


🌸 NAME 🌸

write_bin β€” literally just: write out a bin. that's the whole vibe πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

void write_bin (struct packer *packer , struct packer_bin *bin );

no cap, that's the signature. keep it exactly like that, don't you dare touch it 😭


πŸŽ€ ARGUMENTS πŸŽ€

  • packer β€” the packer. yes, the packer. the main character of this whole situation πŸ‘‘
  • bin β€” the bin you're writing out. the one getting sent, the one getting packed, the icon, the moment ✨

πŸ”₯ SEE ALSO πŸ”₯

okay this list is LONG but we do not skip, we do not summarise, we list every single one because that's the rule and honestly? iconic behaviour 🌈

Kernel file ./drivers/md/dm-vdo/packer.c

then the whole squad, in order, no cuts:

vdo_get_compressed_block_fragment(9), assert_on_packer_thread(9),
insert_in_sorted_list(9), make_bin(9), vdo_make_packer(9),
vdo_free_packer(9), get_packer_from_data_vio(9),
vdo_get_packer_statistics(9), abort_packing(9),
release_compressed_write_waiter(9), finish_compressed_write(9),
add_to_bin(9), remove_from_bin(9), initialize_compressed_block(9),
pack_fragment(9), compressed_write_end_io(9),
add_data_vio_to_packer_bin(9), select_bin(9), vdo_attempt_packing(9),
check_for_drain_complete(9), write_all_non_empty_bins(9),
vdo_flush_packer(9), vdo_remove_lock_holder_from_packer(9),
vdo_increment_packer_flush_generation(9), vdo_drain_packer(9),
vdo_resume_packer(9), vdo_dump_packer(9)

like, go read those too bestie, they're all connected, it's giving ecosystem πŸ’€πŸŒΈ


and that's the whole page!! short but slay, honestly. this came from ./drivers/md/dm-vdo, dated October 2026, and it's the write_bin(9) page β€” catch you on the next one, mwah πŸ’–πŸŽ€πŸ«Ά

πŸ“¦ where this page comes from