zs_malloc(9)

💖 zs_malloc(9) 💖

okay bestie, welcome to the Kernel API Manual entry for zs_malloc — yes, we're literally allocating a block of a given size from a pool, and it's giving kernel-core main character energy 💅✨

---

🌸 NAME 🌸

zs_malloc — allocate a block of the given size from a pool. that's the whole vibe 🫶

---

✨ SYNOPSIS ✨

unsigned long zs_malloc (struct zs_pool *pool , size_t size , gfp_t gfp
, const int nid );

---

🎀 ARGUMENTS 🎀

• pool — the pool you're allocating from, bestie. that's the source 🏊‍♀️
• size — the size of the block to allocate. yes, size matters 💅
• gfp — the gfp flags used when allocating the object 🌱
• nid — the preferred node id for allocating a new zspage (if needed). key phrase: if needed 👀

---

🦋 DESCRIPTION 🦋

so here's the tea: on success, zs_malloc returns a handle to the allocated object. slay. 🎉

otherwise? you get an ERR_PTR. not the cute kind of surprise 😭

⚠️ heads up: allocation requests with size > ZS_MAX_ALLOC_SIZE will fail. no cap, that's the limit. 💀

---

🌈 SEE ALSO 🌈

• Kernel file ./mm/zsmalloc.c
• obj_to_location(9)
• location_to_obj(9)
• zs_lookup_class_index(9)
• zs_huge_class_size(9)
• zs_create_pool(9)

---

and that's the page, bestie 💖 source/version: ./mm — dated October 2026 🎀✨ go forth and allocate responsibly, mwah 🫶👑