memblock_find_in_range(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

memblock_find_in_range β€” bestie, this is the one that finds free area in given range, no cap 🎯✨


🌸 SYNOPSIS 🌸

phys_addr_t __init_memblock memblock_find_in_range (phys_addr_t start ,
phys_addr_t end , phys_addr_t size , phys_addr_t align );

(it lives in the Kernel API Manual, if you were wondering where this Queen resides πŸ‘‘)


πŸŽ€ ARGUMENTS πŸŽ€

  • start β€” where the candidate range begins, the starting line of the whole search, okurrr 🌱
  • end β€” where the candidate range stops. And listen: this one can legitimately be MEMBLOCK_ALLOC_ANYWHERE or MEMBLOCK_ALLOC_ACCESSIBLE, so it's not always a plain ol' number, she has ✨options✨
  • size β€” how big a free area you're trying to find. That's the bag you're looking for πŸ’…
  • align β€” the alignment the free area you find needs to have. yes alignment matters, it always matters πŸ”₯

πŸ¦‹ DESCRIPTION πŸ¦‹

So what it does: it finds a free area of size, aligned to align, inside the range you specified. That's it. That's the whole vibe. It's giving "search party, but for memory" 🧚✨


⭐ RETURN ⭐

  • Found address on success πŸŽ‰
  • 0 on failure 😭 (yeah, zero. rough. we've all been there)

πŸ‘‘ SEE ALSO πŸ‘‘

The whole memblock friend group showed up, and honestly? iconic 🫢 Go read up on these:


πŸ’€ fr fr, that's the whole list. iykyk. go touch some memblock 🌈

okay bye bestie, mwah πŸ’‹ this lil page came from the ./mm corner of the world and it's dated October 2026 β€” memblock_find_in_range(9), signing off πŸŽ€βœ¨πŸ’œ

πŸ“¦ where this page comes from