__next_mem_range_rev(9)

💅 __next_mem_range_rev(9) — a Kernel API Manual moment

okay so bestie, welcome to the Kernel API Manual page for __next_mem_range_rev — yes it's a mouthful, no we're not renaming it, it's iconic as-is 🎀

---

✨ NAME ✨

__next_mem_range_rev — the generic next function for for_each_*_range_rev(). that's it, that's the whole vibe. she's a helper. she helps. 💖

---

🦋 SYNOPSIS 🦋

void __init_memblock __next_mem_range_rev (u64 *idx , int nid , enum
memblock_flags flags , struct memblock_type *type_a , struct
memblock_type *type_b , phys_addr_t *out_start , phys_addr_t *out_end ,
int *out_nid );

literally just look at her. seven whole parameters. main character energy, no cap 👑

---

🌸 ARGUMENTS 🌸

• idx — pointer to a u64 loop variable. she keeps track of where we're at, bestie 🌀
• nid — the node selector. pass NUMA_NO_NODE if you want all the nodes, you greedy little thing 😌
• flags — how we pick blocks, based on memory attributes ✨
• type_a — pointer to the memblock_type we're taking the range from (the source, the origin, the it-girl) 🫶
• type_b — pointer to the memblock_type that excludes memory from being taken (the bouncer at the door 💅)
• out_start — ptr to a phys_addr_t for the start address of the range. can be NULL 🙈
• out_end — ptr to a phys_addr_t for the end address of the range. can be NULL too 🙈
• out_nid — ptr to an int for the nid of the range. also can be NULL. so many optional outputs, honestly slay 🌈

---

💜 DESCRIPTION 💜

so what does she actually do? she finds the next range from type_a that is not marked as unsuitable in type_b. that's the whole job. that's the assignment. she ate and left no crumbs 🔥

and the plot twist: she's the reverse of __next_mem_range. yeah. the backwards one. the remix. ⭐

---

🧚 SEE ALSO 🧚

go drink some water and then go read these, i'm serious:

• Kernel file ./mm/memblock.c, memblock overview(9)
• __memblock_find_range_bottom_up(9)
• __memblock_find_range_top_down(9)
• memblock_find_in_range_node(9)
• memblock_find_in_range(9)
• memblock_discard(9)
• memblock_double_array(9)
• memblock_merge_regions(9)
• memblock_insert_region(9)
• memblock_add_range(9)
• memblock_add_node(9)
• memblock_add(9)
• memblock_validate_numa_coverage(9)
• memblock_isolate_range(9)
• memblock_free(9)
• memblock_phys_free(9)
• memblock_setclr_flag(9)
• memblock_mark_hotplug(9)
• memblock_clear_hotplug(9)
• memblock_mark_mirror(9)
• memblock_mark_nomap(9)
• memblock_clear_nomap(9)
• memblock_reserved_mark_noinit(9)
• memblock_reserved_mark_kern(9)
• memblock_mark_kho_scratch(9)
• memblock_clear_kho_scratch(9)
• __next_mem_range(9)
• memblock_set_node(9)
• memblock_alloc_range_nid(9)
• memblock_phys_alloc_range(9)
• memblock_phys_alloc_try_nid(9)
• memblock_alloc_internal(9)
• memblock_alloc_exact_nid_raw(9)
• memblock_alloc_try_nid_raw(9)
• memblock_alloc_hugetlb(9)
• memblock_alloc_try_nid(9)
• __memblock_alloc_or_panic(9)
• memblock_estimated_nr_free_pages(9)
• memblock_is_region_memory(9)
• memblock_is_region_reserved(9)
• memblock_free_all(9)
• reserve_mem_find_by_name(9)
• reserve_mem_release_by_name(9)

---

and that's the page!! 🎀 she's from ./mm, dated October 2026, and she lives in the Kernel API Manual forever and ever. bye bestie, ily, go iterate some ranges (in reverse) 💖✨🦋