Tanenbaum, Andrew S.. (1990) Structured Computer Organization, Third Edition. Prentice Hall. ISBN 978-0-13-854662-5. “Like the trap, the interrupt stops the running program and transfers control to an interrupt handler, which performs some appropriate action. When finished, the interrupt handler returns control to the interrupted program.”.
Soares, Livio Baldini; Stumm, Michael (4a de Oktobro 2010). FlexSC: Flexible System Call Scheduling with Exception-Less System Calls.OSDI '10, 9th USENIX Symposium on Operating System Design and Implementation. USENIX. Alirita la 9an de Aŭgusto 2024. p. 2: "Synchronous implementation of system calls negatively impacts the performance of system intensive workloads, both in terms of the direct costs of mode switching and, more interestingly, in terms of the indirect pollution of important processor structures which affects both user-mode and kernel-mode performance. A motivating example that quantifies the impact of system call pollution on application performance can be seen in Figure 1. It depicts the user-mode instructions per cycles (kernel cycles and instructions are ignored) of one of the SPEC CPU 2006 benchmarks (Xalan) immediately before and after a pwrite system call. There is a significant drop in instructions per cycle (IPC) due to the system call, and it takes up to 14,000 cycles of execution before the IPC of this application returns to its previous level. As we will show, this performance degradation is mainly due to interference caused by the kernel on key processor structures."
