async_schedule_dev_nocall(9)

✨ async_schedule_dev_nocall(9) ✨

okay so bestie, welcome to the Kernel API Manual — this is the page for async_schedule_dev_nocall, and it is literally the low-drama cousin of async_schedule_dev(). no cap. let's get into it 💅

---

🎀 NAME 🎀

async_schedule_dev_nocall — a simplified variant of async_schedule_dev(). that's it, that's the vibe check 🌸

---

🦋 SYNOPSIS 🦋

bool async_schedule_dev_nocall (async_func_t func , struct device *dev );

like, it takes a func, it takes a dev, and it returns a bool. clean. iconic. no notes ✨

---

💖 ARGUMENTS 💖

• func — the function to execute asynchronously. the main character of this whole operation, fr fr 👑
• dev — the device argument that gets passed to the function. yes, it's doing double duty, keep reading 🫶

---

🔥 DESCRIPTION 🔥

so here's the tea: dev is used as both the argument for the function and to provide the NUMA context for where to run the function. one struct, two jobs, she's multitasking 💅✨

if the asynchronous execution of func is scheduled successfully, you get true back. slay. otherwise it does nothing and returns false — and this is the whole point, okay? unlike async_schedule_dev, which will run the function synchronously then, this one just... doesn't. no fallback, no backup plan, no plan B. it's giving "if it doesn't work out, I'm not doing it at all" energy 💀

ngl, if you were expecting a synchronous fallback, you're on the wrong page bestie — that's the other function 🙈

---

🌈 SEE ALSO 🌈

go be nosy in the kernel file ./kernel/async.c, and also check out these besties:

• async_schedule_node_domain(9)
• async_schedule_node(9)
• async_synchronize_full(9)
• async_synchronize_full_domain(9)
• async_synchronize_cookie_domain(9)
• async_synchronize_cookie(9)
• current_is_async(9)

---

and that's the whole page, bestie 🍓 this lil gem lives in ./kernel, from October 2026, and it's filed under async_schedule_dev_nocall(9) — go forth and schedule async, but like, only if it works the first time 💜🧚⭐