gen_pool_for_each_chunk(9)

📦 version 7.3.1, in nixpkgs unstable

💖 gen_pool_for_each_chunk(9) 💖

okay so bestie, we're in the Kernel API Manual (that's the manual name, iykyk) and today's main character is a function that just... loops over stuff for you. no cap. let's get into it 🦋

✨ NAME ✨

gen_pool_for_each_chunk — call func for every chunk of generic memory pool. that's it. that's the whole vibe. 💅

🎀 SYNOPSIS 🎀

void gen_pool_for_each_chunk (struct gen_pool *pool , void
(*func)(struct gen_pool *pool, struct gen_pool_chunk *chunk, void *data)
, void *data );

literally copy it exactly, don't @ me 🙈

💜 ARGUMENTS 💜

  • pool — the generic memory pool. the pool in question. the one we're strolling through 🌸
  • func — func to call. yes, that's the actual description. the callback. the thing that runs per chunk 🫶
  • data — additional data used by func. your little care package that gets handed off to func every time ✨

🔥 DESCRIPTION 🔥

Call func for every chunk of generic memory pool. that's the whole bit — no tricks, no secret sauce.

⚠️ okay but here's the important part, lowkey the most important part: the func is called with rcu_read_lock held. so if your callback was thinking about sleeping or doing something spicy, maybe don't 😭 treat that lock like it's holding your iced coffee and you can't spill it.

🌈 SEE ALSO 🌈

so the kernel file is ./lib/genalloc.c (go read it, it's giving source-of-truth 👑), and here's the whole friend group — every single one of them, no skips:

like, the whole fam fr fr 🧚

mwah — this page lives under ./lib, stamped October 2026, and yes it's signed gen_pool_for_each_chunk(9) on the way out. slay, go iterate some chunks 💖⭐

📦 where this page comes from