STRUCT KHO_BLOCK_SET(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct kho_block_set(9) πŸ’–

okay so bestie, welcome to the Kernel API Manual ✨ β€” today we're learning about struct kho_block_set, and honestly? it's giving "organized friend group" 🫢


🌸 NAME 🌸

struct kho_block_set β€” a whole set of blocks that are each holding serialized entries, and every single entry in the set is the same type. no mixing, no chaos, just vibes πŸŽ€


✨ SYNOPSIS ✨

here's the whole look, literally copy it exactly:

struct kho_block_set {
    struct list_head blocks;
    long nblocks;
    u64 head_pa;
    size_t entry_size;
    u64 count_per_block;
    bool incoming;
 };

πŸ¦‹ Members πŸ¦‹

  • blocks β€” the list of serialization blocks (each one is a struct kho_block). it's the group chat member list fr fr πŸ’…
  • nblocks β€” how many serialization blocks have actually been allocated. like, headcount 🧚
  • head_pa β€” the physical address of the first block header. yes physical, not virtual, she's built different πŸ”₯
  • entry_size β€” the size of each entry inside the blocks. every entry, same size, no gatekeeping 🌈
  • count_per_block β€” the maximum number of entries that each block can hold. the capacity, the limit, the "no more room bestie" number πŸ‘‘
  • incoming β€” true if this block set was restored from the previous kernel. so it's basically a carry-over from the last era, main character energy ⭐

πŸ’œ Note πŸ’œ

ngl this part matters: synchronization and locking are the responsibility of the caller. the block set structure itself is not internally synchronized. so no, she will not lock herself for you β€” you gotta do it yourself, periodt πŸ˜­πŸ”’

πŸŽ€ SEE ALSO πŸŽ€

go read these next, they're all in the kernel file ./include/linux/kho_block.h:


and that's the whole page, bestie πŸ’– this icon lived in ./include/linux, dated October 2026, and she's signing off β€” ily, go lock your own structs πŸ«ΆπŸ’…βœ¨

πŸ“¦ where this page comes from