vmalloc_node(9)

💖 vmalloc_node(9) 💖

okay bestie, welcome to the Kernel API Manual — we're doing vmalloc_node, and it's giving “I allocate pages on one specific node” energy. ✨

---

🌸 NAME 🌸

vmalloc_node — allocate memory on a specific node 💅

✨ SYNOPSIS ✨

void * vmalloc_node (unsigned long size , int node );

🎀 ARGUMENTS 🎀

• size — allocation size 🍓
• node — numa node 🦋

🌈 DESCRIPTION 🌈

So like, vmalloc_node allocates enough pages to cover size from the page level allocator, then maps them into contiguous kernel virtual space. no cap, that's the vibe. 💖

If you want tight control over the page level allocator and protection flags, use __vmalloc instead — that's the one for that job. 👑

bestie note: the tight-control route is __vmalloc, not this one. iykyk. 💅

💫 RETURN 💫

A pointer to the allocated memory, or NULL on error. that's it, periodt. 🫶

🦋 SEE ALSO 🦋

Kernel file ./mm/vmalloc.c — and the whole see-also squad is:

• vunmap_range(9), vmap_pages_range(9), vm_area_map_pages(9), vm_area_unmap_pages(9), new_vmap_block(9)
• vm_unmap_aliases(9), vm_unmap_ram(9), vm_map_ram(9)
• vm_area_add_early(9), vm_area_register_early(9), get_vm_area(9), find_vm_area(9), remove_vm_area(9)
• vfree_atomic(9), vfree(9), vunmap(9), vmap(9), vmap_pfn(9)
• __vmalloc_node_range(9), __vmalloc_node(9), vmalloc(9), vmalloc_huge_node(9), vzalloc(9), vmalloc_user(9), vzalloc_node(9), vrealloc_node_align(9)
• vmalloc_32(9), vmalloc_32_user(9), vread_iter(9)
• remap_vmalloc_range_partial(9), remap_vmalloc_range(9)
• pvm_find_va_enclose_addr(9), pvm_determine_end_from_reverse(9), pcpu_get_vm_areas(9), pcpu_free_vm_areas(9)

mwah 💋 — source/version ./mm, date October 2026. byeee, bestie 💖