async_schedule_dev_domain(9)
π async_schedule_dev_domain(9) π
okay bestie, this is a page from the Kernel API Manual and it's genuinely one of the cuter ones β it's the device-specific version of async_schedule_domain, and it's lowkey iconic for anyone who cares about NUMA vibes. let's get into it π«Ά
β¨ NAME β¨
async_schedule_dev_domain β a device specific version of async_schedule_domain. that's it, that's the whole name section, and honestly? slay for being concise π
π¦ SYNOPSIS π¦
async_cookie_t async_schedule_dev_domain (async_func_t func , struct
device *dev , struct async_domain *domain );
yes it's a mouthful, no we are not scared of it. three args, one cookie, let's go β¨
π ARGUMENTS π
funcβ the function to execute asynchronously. this is the main character of the operation, the thing that actually gets run in the background π«devβ the device argument to be passed to function. it's doing double duty here (more on that in a sec, iykyk) π§domainβ the domain. literally just the domain. that's the whole explanation and honestly? respect for not over-explaining π
πΈ DESCRIPTION πΈ
okay so here's the tea β β this function returns an async_cookie_t that may be used for checkpointing later. keep that cookie, it's your little receipt for later, bestie πͺ
now the fun part: dev is used as both the argument for the function and to provide NUMA context for where to run the function. the way this works is genuinely smart β by doing this, we can try to provide for the best possible outcome by operating on the device on the CPUs closest to the device. highkey obsessed with the efficiency of it all π₯
and domain may be used in the async_synchronize_*_domain functions to wait within a certain synchronization domain rather than globally. so like, you can scope your waiting instead of making everything wait. periodt π
π NOTE π
this function may be called from atomic or non-atomic contexts. no cap, both are fine β she's flexible like that π§
π SEE ALSO π
- Kernel file
./include/linux/async.hasync_schedule(9) async_schedule_domain(9)async_schedule_dev(9)
go read those too, they're the whole friend group and they all ate π
and that's the page!! π this one came from ./include/linux, dated October 2026 β so like, future girlie energy fr fr. bye bestie, go schedule some async work on the closest CPU and think of me πβ¨π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms