wq_worker_tick(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ wq_worker_tick(9) ✨

okay so bestie, welcome to the Kernel API Manual πŸŽ€ β€” this little cutie lives in section 9, and honestly? it's giving "tiny function, big responsibilities." let's get into it πŸ’…


🌸 NAME 🌸

wq_worker_tick β€” a scheduler tick occurred while a kworker is running ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

void wq_worker_tick (struct task_struct *task );

πŸ’– ARGUMENTS πŸ’–

  • task β€” the task currently running. that's the one, bestie πŸ‘‘

πŸ”₯ DESCRIPTION πŸ”₯

so here's the vibe: this gets called from sched_tick. we're in the IRQ context, and the current worker's fields β€” the ones that follow the 'K' locking rule β€” can be accessed safely. no cap, that's the whole situation 🫢

real talk: the 'K' locking rule part is load-bearing. it's why the access is safe in the first place, so don't go poking at fields that don't follow it πŸ’€

🌈 SEE ALSO 🌈

Kernel file ./kernel/workqueue.c β€” and like, a lot of friends. honestly iconic how many πŸ“


and that's the whole page, bestie πŸ§šπŸ’œ sourced from ./kernel, dated October 2026, and yes β€” the footer still says wq_worker_tick(9) because we keep it consistent around here. mwah πŸ’‹

πŸ“¦ where this page comes from