IRQ is an asyncronous signal sent to microprocessor to advertise a requested work is completed [MDN Docs: JWT] .:: telegra.ph ::. [Hash function Repositories]
|<--> IRQ(0) [Timer]
|<--> IRQ(1) [Device 1]
| ..
|<--> IRQ(n) [Device n]
_____________________________|
/|\ /|\ /|\
| | |
\|/ \|/ \|/
Task(1) Task(2) .. Task(N)
IRQ - Tasks Interaction Schema
A typical O.S. uses many IRQ signals to interrupt normal process execution and does some housekeeping work. So: .:: podcasts.apple.com ::. .:: telegra.ph ::.
Under Linux, when an IRQ comes, first the IRQ wrapper routine (named "interrupt0x??") is called, then the "official" IRQ(i)_handler will be executed. This allows some duties like timeslice preemption. .:: www.slideshare.net ::. .:: www.noteflight.com ::. .:: bk88innet.netlify.app ::. .:: sunwinw.gitbook.io ::.