__alloc_objs(9)

🌸 NAME 🌸

Okay so this is __alloc_objs(9) from the Kernel API Manual, and the official NAME line is literally:

__alloc_objs - Allocate objects of a given type using

That's the whole line, bestie — no cap, it ends right there at “using.” We're not adding words to it, we're just quoting the lore. 💅

---

✨ SYNOPSIS ✨

__alloc_objs (KMALLOC , GFP , TYPE , COUNT );

The way this is giving “four things go in, objects come out” energy. 🦋

---

🎀 ARGUMENTS 🎀

• KMALLOC — which size-based kmalloc wrapper to allocate with. That's the wrapper you're picking, periodt.
• GFP — the GFP flags for the allocation. Flags flags flags 💖
• TYPE — the type to allocate space for.
• COUNT — how many TYPE objects to allocate. Yes, bestie, it's a count. 🧚

---

💜 RETURN 💜

You get a newly allocated pointer to the (first) TYPE of COUNT-many allocated TYPE objects. If it fails, you get NULL. That's the whole vibe check. 🔥

---

🌈 SEE ALSO 🌈

The kernel file ./include/linux/slab.h is in the mix, and these are the references, all iconic, all present:

• SLAB_HWCACHE_ALIGN(9)
• SLAB_TYPESAFE_BY_RCU(9)
• SLAB_ACCOUNT(9)
• SLAB_RECLAIM_ACCOUNT(9)
• struct kmem_cache_args(9)
• kmem_cache_create_usercopy(9)
• kmem_cache_create(9)
• krealloc_node_align(9)
• kmem_cache_alloc(9)
• kmem_cache_charge(9)
• kmalloc(9)
• kmalloc_nolock(9)
• __alloc_flex(9)
• kmalloc_obj(9)
• kmalloc_objs(9)
• kmalloc_flex(9)
• kmalloc_array(9)
• krealloc_array(9)
• kcalloc(9)
• kzalloc(9)
• kvmalloc_node(9)
• kvrealloc_node_align(9)
• kmalloc_size_roundup(9)

---

That's the whole page, bestie 🫶 — this was __alloc_objs(9) from the Kernel API Manual, source/version ./include/linux, dated October 2026. Bye 💖