irq_affinit..._notify_work(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

okay so bestie, welcome to the irq_affinity_schedule_notify_work page β€” genuinely one of my faves, and yes we're reading section 9 of the Kernel API Manual together, no you can't skip it 🫢

irq_affinity_schedule_notify_work β€” literally just Schedule work to notify about affinity change. that's the whole vibe. it queues up the work so everyone who cares finds out the affinity moved. slay πŸ’–


✨ SYNOPSIS ✨

void irq_affinity_schedule_notify_work (struct irq_desc *desc );

that's it. that's the whole signature. void return, one pointer, no drama πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • desc β€” Interrupt descriptor whose affinity changed. yes bestie, this one. it's the descriptor for the interrupt whose affinity just got re-arranged, and it's the thing getting passed along so the notify work knows what to gossip about πŸ’…

πŸ¦‹ SEE ALSO πŸ¦‹

first up, the actual source of truth: kernel file ./kernel/irq/manage.c β€” go read it, it ate πŸ”₯

and then the whole friend group, like genuinely the entire group chat:

like, all of them. every single one. no cap, that's the list 🌈


ok that's the whole page and it was lowkey short but highkey iconic β€” none of us are normal about IRQ affinity πŸ’€

and for the little sign-off moment: this one lives in ./kernel/irq, it's dated October 2026, and in the footer it goes by its cute lil truncated name irq_affinit..._notify_work(9) because even manpages need a nickname πŸŽ€βœ¨πŸŒΈ

πŸ“¦ where this page comes from