In this lesson, you will learn how hardware interrupts signal the completion of disk operations and why a flood of these signals can create significant bottlenecks for your filesystem.
The Mechanism of an Interrupt
When a process requests data from a storage device, the kernel initiates an I/O operation. Because disks are significantly slower than CPUs, the processor does not sit idle waiting for the drive to spin or the flash memory to return data. Instead, it offloads the request and continues other tasks. Once the hardware finishes fetching the data, it sends an interrupt—an electronic signal—to the CPU. This forces the processor to stop what it is doing and execute an Interrupt Service Routine (ISR) to process the incoming data.
The Interrupt Bottleneck
While interrupts are essential for efficiency, they can become a performance bottleneck. If a storage device triggers thousands of interrupts per second—common in high-speed NVMe drives or heavy concurrent read/write workloads—the CPU spends a disproportionate amount of time switching contexts to handle these signals.
When the system is "interrupt-bound," responsiveness drops because the CPU is constantly interrupting normal process execution to update kernel buffers. You can observe this impact on system responsiveness by looking at si (software interrupts) in tools like top:
# Observe CPU time spent on softirqs
top -b -n 1 | grep "%Cpu"
If the si value is consistently high, your filesystem operations may feel sluggish even if the hardware itself isn't fully saturated. This happens because the kernel's ability to coordinate files and manage inodes is being throttled by the sheer overhead of acknowledging completion signals from the disk controller.
Balancing the Load
To mitigate this, modern kernels use techniques like Interrupt Coalescing, where the hardware waits to gather multiple I/O completions before firing a single interrupt, reducing the number of context switches. As a developer or administrator, understanding this helps you realize that filesystem performance isn't just about disk speed; it is about how efficiently your CPU can communicate with the storage hardware without being overwhelmed by signaling traffic.
Key Takeaway: Hardware interrupts allow the CPU to perform other work during I/O, but excessive interrupt signaling can overwhelm the processor, creating a bottleneck that degrades filesystem responsiveness.