queue_delayed_work(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… queue_delayed_work β€” the Kernel API Manual, bestie edition

okay so picture this: it's queue_delayed_work(9) from the Kernel API Manual, and it's here to let you queue up work on a workqueue… but like, later. Not now. After a delay. Main character scheduling behavior, honestly πŸŽ€


✨ NAME ✨

queue_delayed_work β€” queue work on a workqueue after delay

No cap, that's the whole vibe: work goes on a workqueue, but only after a delay. Delayed gratification but make it kernel ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

bool queue_delayed_work (struct workqueue_struct *wq , struct
       delayed_work *dwork , unsigned long delay );

Look at that signature, it ate πŸ’… returns a bool, takes three things, we love a tidy little function.


🌸 ARGUMENTS 🌸

  • wq β€” workqueue to use. this is the queue your work is gonna live on, so pick a good one bestie 🫢
  • dwork β€” delayable work to queue. literally the struct delayed_work that's getting queued up πŸ’–
  • delay β€” number of jiffies to wait before queueing. that's jiffies, not seconds, not milliseconds β€” jiffies, iykyk ⏳

πŸ”₯ DESCRIPTION πŸ”₯

Equivalent to queue_delayed_work_on but tries to use the local CPU.

That's it, that's the whole description β€” and honestly it's giving efficient. It does the same thing as queue_delayed_work_on, except it tries to use the local CPU instead of you naming a CPU yourself. Lowkey a little considerate of it, ngl πŸ˜­πŸ’œ

note the "tries" energy β€” it tries to use the local CPU, we're not out here making promises we can't keep.

🌈 SEE ALSO 🌈

go read these next, they're all iconic in their own way πŸ‘‘


okay that's the whole page, go queue something delayed and slay πŸ’…βœ¨

signing off from ./include/linux, dated October 2026 β€” this was queue_delayed_work(9), bestie, mwah πŸ«ΆπŸŽ€

πŸ“¦ where this page comes from