async_schedule_dev(9)

✨ async_schedule_dev(9) ✨

okay so bestie, we're in the Kernel API Manual today and this little function is genuinely kind of iconic 💅 it's the device-specific glow-up of async_schedule, and it's here to make your async work land on the right CPU. buckle up 🎀

---

🌸 NAME 🌸

async_schedule_dev — a device specific version of async_schedule 🦋

---

⭐ SYNOPSIS ⭐

async_cookie_t async_schedule_dev (async_func_t func , struct device
*dev );

---

🧚 ARGUMENTS 🧚

• func — the function to execute asynchronously, like literally the whole point of this thing ✨
• dev — the device argument to be passed to the function, and also the vibe-check reference for where it runs 📍

---

💅 DESCRIPTION 💅

So what you get back is an async_cookie_t, and no cap, you're gonna want to hold onto it — it may be used for checkpointing later 🍪✨

Here's the slay part: dev is used as both the argument for the function and to provide NUMA context for where to run the function. the way that works is we can try to provide for the best possible outcome by operating on the device on the CPUs closest to the device 👑

like… efficiency? we invented it. periodt. 🔥

---

💀 NOTE 💀

this function may be called from atomic or non-atomic contexts 🙈 so you're covered either way, bestie. no gatekeeping here 💖

just clocking it so you know: atomic and non-atomic are both on the menu. that's the whole note. don't overthink it 🫶

---

🔮 SEE ALSO 🔮

• Kernel file ./include/linux/async.h
• async_schedule(9)
• async_schedule_domain(9)
• async_schedule_dev_domain(9)

go read the whole async family, they're all main character energy in their own way 🌈⭐

---

okay that's the page!! 🎀 this fab little page lives in ./include/linux and it's dated October 2026, and obviously it's the async_schedule_dev(9) manual page — mwah, go forth and schedule asynchronously 💜🧚‍♀️