add_timer_on(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… add_timer_on β€” like, the Kernel API Manual page, bestie

okay so real talk, this one is from the Kernel API Manual, section 9, and it's called add_timer_on. Buckle up, it's short but she's important.


✨ NAME ✨

add_timer_on β€” start a timer on a particular CPU πŸ‘‘


πŸŽ€ SYNOPSIS πŸŽ€

void add_timer_on (struct timer_list *timer , int cpu );

literally two args, no drama, we love a minimal signature 🫢


🌸 ARGUMENTS 🌸

  • timer β€” the timer you wanna start, babes. that's the one.
  • cpu β€” the CPU you want it started on. yes, that CPU. pick one. 🎯

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so it's the same as add_timer, except β€” and this is the whole vibe β€” it starts the timer on the given CPU and the TIMER_PINNED flag gets set. Pinned, like, it's committed to that CPU. main character energy, no wandering off. πŸ’…

But heads up 🫢 when the timer shouldn't be a pinned timer in the next round, you should use add_timer_global instead, because that one unsets the TIMER_PINNED flag. so like, don't leave it pinned forever unless you meant to, yk? πŸ™ˆ

For further details, go peek at add_timer β€” she's got the lore.


πŸ”₯ SEE ALSO πŸ”₯

okay the full squad, no gatekeeping:


πŸ’– reminder: TIMER_PINNED gets set by this one. if you don't want that in the next round, reach for add_timer_global(9). iykyk πŸ’€

and that's the whole page, bestie! 🌈 this cutie lives in ./kernel/time and it was dated October 2026 β€” so yeah, future icon behavior πŸ‘‘βœ¨ slay responsibly πŸŽ€

πŸ“¦ where this page comes from