ccw_device_sched_todo(9)
π ccw_device_sched_todo(9) β like, the manual page, bestie
Okay so this is a Kernel API Manual entry for ccw_device_sched_todo(9) and it's honestly kind of a little scheduling baddie. Let's get into it β¨
πΈ NAME πΈ
ccw_device_sched_todo β schedule ccw device operation
π SYNOPSIS π
void ccw_device_sched_todo (struct ccw_device *cdev , enum cdev_todo
todo );
π¦ ARGUMENTS π¦
cdevβ the ccw device in question, your main character π«Άtodoβ the todo. yeah. that's the whole description. it's giving minimalism, it's giving mystery, we respect it π
π₯ DESCRIPTION π₯
So basically: you take the operation that todo identifies and you schedule it to be performed on the slow path workqueue. That's it. That's the vibe check β¨
But wait, there's a lil plot twist π β if another operation with higher priority is already scheduled, this function does nothing. Like, it literally just sits there and lets the more important one cook. Respect the hierarchy, periodt π
β οΈ And this is the important part bestie, do NOT skip it: this needs to be called with the ccwdev lock held. No lock, no service. Non-negotiable π
π SEE ALSO π
Kernel file ./drivers/s390/cio/device.c β and also these iconic little friends:
ccw_device_set_offline(9)ccw_device_set_online(9)get_ccwdev_by_dev_id(9)ccw_purge_blacklisted(9)io_subchannel_sch_event(9)ccw_device_wait_idle(9)get_ccwdev_by_busid(9)ccw_driver_register(9)ccw_driver_unregister(9)ccw_device_siosl(9)
And that's the whole page, no cap π§ This lil drop came from ./drivers/s390/cio and is dated October 2026 β so go schedule those operations, hold that lock, and slay ππβ
π¦ 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