for_each_memory_block(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

for_each_memory_block β€” walk through all present memory blocks πŸšΆβ€β™€οΈπŸ’–

Okay so this is for_each_memory_block(9) from the Kernel API Manual, bestie. Group chat is open, let's go. πŸ’…

🌸 SYNOPSIS 🌸

int for_each_memory_block (void *arg , walk_memory_blocks_func_t func );

πŸŽ€ ARGUMENTS πŸŽ€

  • arg β€” the argument that gets passed to func 🫢
  • func β€” the callback for each memory block walked ✨

πŸ¦‹ DESCRIPTION πŸ¦‹

So like, for_each_memory_block literally walks through all present memory blocks and calls func on each memory block. It's giving β€œone by one, no block left behind.” πŸ’…

And if func returns an error, walking is aborted and the error is returned. Not me getting emotionally invested in the walk only for it to stop early 😭 but yes, that's the deal.

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/base/memory.c and these other pages, bestie:


Sign-off time πŸŽ€: source/version is ./drivers/base, date is October 2026, and the page is for_each_memory_block(9) πŸ’–βœ¨

πŸ“¦ where this page comes from