Operating system (English Wikipedia)

Analysis of information sources in references of the Wikipedia article "Operating system" in English language version.

refsWebsite
Global rank English rank
6th place
6th place
1st place
1st place
3,942nd place
3,244th place
2nd place
2nd place
4,153rd place
2,291st place
879th place
3,323rd place
low place
low place
4,347th place
3,017th place
low place
low place
5th place
5th place
low place
low place
low place
low place
5,990th place
3,752nd place
1,045th place
746th place
low place
low place
1,118th place
825th place
low place
low place
786th place
558th place

archive.org

bitsavers.org

cairn.info

doi.org

intel.com

oreilly.com

osdev.org

wiki.osdev.org

  • Modern CPUs provide instructions (e.g. SYSENTER) to invoke selected kernel services without an interrupts. Visit https://wiki.osdev.org/SYSENTER for more information.

osnews.com

plantation-productions.com

  • Hyde, Randall (1996). "Chapter Seventeen: Interrupts, Traps and Exceptions (Part 1)". The Art Of Assembly Language Programming. No Starch Press. Archived from the original on 22 December 2021. Retrieved 22 December 2021. The concept of an interrupt is something that has expanded in scope over the years. The 80x86 family has only added to the confusion surrounding interrupts by introducing the int (software interrupt) instruction. Indeed, different manufacturers have used terms like exceptions, faults, aborts, traps and interrupts to describe the phenomena this chapter discusses. Unfortunately there is no clear consensus as to the exact meaning of these terms. Different authors adopt different terms to their own use.

rwth-aachen.de

acs.eonerc.rwth-aachen.de

sigarch.org

statcounter.com

gs.statcounter.com

unikraft.org

usenix.org

  • Soares, Livio Baldini; Stumm, Michael (4 October 2010). FlexSC: Flexible System Call Scheduling with Exception-Less System Calls. OSDI '10, 9th USENIX Symposium on Operating System Design and Implementation. USENIX. Retrieved 9 August 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.

web.archive.org

wisc.edu

pages.cs.wisc.edu

worldcat.org

search.worldcat.org

zdnet.com