async_schedule_node(9)

📦 version 7.3.1, in nixpkgs unstable

✨ async_schedule_node(9) ✨

okay so bestie, welcome to the Kernel API Manual 💖 this one is literally the NUMA-specific glow-up of async_schedule, and it's giving "i have a favorite CPU and i'm not sorry." let's get into it 🦋

🌸 NAME 🌸

async_schedule_node — the NUMA specific version of async_schedule. yes she has a whole node preference, she's main character energy 👑

⭐ SYNOPSIS ⭐

async_cookie_t async_schedule_node (async_func_t func , void *data , int node );

like, three things in, one cookie out. slay 💅

🎀 ARGUMENTS 🎀

  • func — the function you want to run asynchronously, aka the actual work. she's the vibe, she's the moment ✨
  • data — the data pointer you're passing along to that function. think of it as the little gift bag you hand over 🫶
  • node — the NUMA node you want this scheduled on, or close to. she has a location preference and honestly? same 🌈

💜 DESCRIPTION 💜

Returns an async_cookie_t that may be used for checkpointing later. keep that cookie, bestie — it's literally your receipt for checking in on this work afterwards 🍓

🔥 NOTE 🔥

This function may be called from atomic or non-atomic contexts. yes, both. she's flexible like that 💅

The node you requested will be honored on a best effort basis — no cap, it's a request, not a demand 🙈. And if that node has no CPUs associated with it, then the work gets distributed among all available CPUs instead. so like, if your fave venue is closed, the party just moves somewhere else 🎉

🦋 SEE ALSO 🦋

go read the whole friend group, they're all iconic 👑

ngl this one's short but she ate. cookie in, best-effort node, all-CPU fallback, periodt 💀✨

and that's the whole page, bestie 🧚 this cutie lives in ./kernel and the date on it is October 2026 — catch you in the next manpage, mwah 💖🎀

📦 where this page comes from