memblock_find_in_range_node(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– memblock_find_in_range_node(9) πŸ’–

okay bestie, welcome to the Kernel API Manual page for memblock_find_in_range_node(9) β€” it's lowkey the friend who finds you a free spot in the group chat, except the group chat is memory. πŸ’…βœ¨

🌸 NAME 🌸

memblock_find_in_range_node β€” find free area in given range and node πŸ¦‹

✨ SYNOPSIS ✨

the signature is right here, bestie β€” copy it exactly, no autocorrect:

phys_addr_t __init_memblock memblock_find_in_range_node (phys_addr_t
size , phys_addr_t align , phys_addr_t start , phys_addr_t end , int nid
, enum memblock_flags flags );

πŸŽ€ ARGUMENTS πŸŽ€

  • size β€” size of free area to find. that's the amount you're hunting for, periodt. πŸ’–
  • align β€” alignment of free area to find. it's gotta line up cute. ✨
  • start β€” start of candidate range.
  • end β€” end of candidate range, can be MEMBLOCK_ALLOC_ANYWHERE or MEMBLOCK_ALLOC_ACCESSIBLE. yes those are the named options, don't improvise. πŸŽ€
  • nid β€” nid of the free area to find, NUMA_NO_NODE for any node. so if you don't care which node, that's the vibe. πŸ¦‹
  • flags β€” pick from blocks based on memory attributes. iykyk. πŸ’…

πŸ’… DESCRIPTION πŸ’…

Find size free area aligned to align in the specified range and node. that's literally the whole description, and honestly? iconic. πŸŽ€

🫢 RETURN 🫢

Found address on success, 0 on failure. so 0 means it didn't find one, bestie β€” don't celebrate a zero. 😭

πŸ¦‹ SEE ALSO πŸ¦‹

these are the linked manual besties, all of them, no skipping:

xoxo, your Unix bestie πŸ’– β€” source ./mm, dated October 2026, mwah 🫢

πŸ“¦ where this page comes from