gen_pool_add_owner(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to the Kernel API Manual β€” this is the gen_pool_add_owner(9) page, and it's literally about adding a new chunk of special memory to the pool. No cap, it's giving allocator-core energy πŸ’…βœ¨

🌸 NAME 🌸

gen_pool_add_owner β€” add a new chunk of special memory to the pool πŸ’–

πŸŽ€ SYNOPSIS πŸŽ€

int gen_pool_add_owner (struct gen_pool *pool , unsigned long virt ,
       phys_addr_t phys , size_t size , int nid , void *owner );

πŸ’œ ARGUMENTS πŸ’œ

  • pool β€” the pool you're adding this new memory chunk to 🫢
  • virt β€” virtual starting address of the memory chunk to add to the pool ✨
  • phys β€” physical starting address of the memory chunk to add to the pool 🌸
  • size β€” size in bytes of the memory chunk to add to the pool πŸŽ€
  • nid β€” node id of the node the chunk structure and bitmap should be allocated on, or -1 πŸ¦‹
  • owner β€” private data the publisher would like to recall at alloc time πŸ‘‘

🌼 DESCRIPTION 🌼

Add a new chunk of special memory to the specified pool. That's the whole assignment, bestie β€” iconic, focused, done. πŸ’…

Returns 0 on success or a -ve errno on failure. So yeah: success is the cute little zero, and failure is negative errno territory β€” note it and move on 😭

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./lib/genalloc.c is the source, and the whole friend group is:


made with πŸ’– from the ./lib source/version, dated October 2026 β€” gen_pool_add_owner(9) out, slay your memory pool bestie πŸŽ€βœ¨

πŸ“¦ where this page comes from