Interrupt is the mechanism by which modules like I/O or memory may interrupt the normal processing by CPU. It may be either clicking a mouse, dragging a cursor, printing a document etc the case where interrupt is getting generated.
Why we require Interrupt?
External devices are comparatively slower than CPU. So if there is no interrupt CPU would waste a lot of time waiting for external devices to match its speed with that of CPU. This decreases the efficiency of CPU. Hence, interrupt is required to eliminate these limitations.
- Suppose CPU instructs printer to print a certain document.
- While printer does its task, CPU engaged in executing other tasks.
- When printer is done with its given work, it tells CPU that it has done with its work.
(The word ‘tells’ here is interrupt which sends one message that printer has done its work successfully.).
- It increases the efficiency of CPU.
- It decreases the waiting time of CPU.
- Stops the wastage of instruction cycle.
- CPU has to do a lot of work to handle interrupts, resume its previous execution of programs (in short, overhead required to handle the interrupt request.).
Attention reader! Don’t stop learning now. Get hold of all the important CS Theory concepts for SDE interviews with the CS Theory Course at a student-friendly price and become industry ready.
- Difference between Hardware Interrupt and Software Interrupt
- Special Purpose Computer Systems
- Computer Organization | Basic Computer Instructions
- Computer Organization | Performance of Computer
- Differences between Computer Architecture and Computer Organization
- I/O Interface (Interrupt and DMA Mode)
- Difference between Interrupt and Polling
- Difference between Maskable and Non Maskable Interrupt
- Difference between Programmed and Interrupt Initiated I/O
- Difference between Interrupt and Exception
- General purpose registers in 8086 microprocessor
- Device Driver and It's Purpose
- Cache Memory in Computer Organization
- Computer Organization and Architecture | Pipelining | Set 1 (Execution, Stages and Throughput)
- Computer Organization and Architecture | Pipelining | Set 3 (Types and Stalling)
- Computer Organization and Architecture | Pipelining | Set 2 (Dependencies and Data Hazard)
- Computer Organization | Amdahl's law and its proof
- Computer Organization | Hardwired v/s Micro-programmed Control Unit
- Computer Organization | Micro-Operation
- Computer Organization | Different Instruction Cycles
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to email@example.com. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.