System Contention Scope

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)

The topic of this article may not meet Wikipedia's general notability guideline. Please help to demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted.
Find sources: "System Contention Scope" – news · newspapers · books · scholar · JSTOR (November 2010) (Learn how and when to remove this message)

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "System Contention Scope" – news · newspapers · books · scholar · JSTOR (March 2015) (Learn how and when to remove this message)

This article is an orphan, as no other articles link to it. Please introduce links to this page from related articles; try the Find link tool for suggestions. (June 2024)

(Learn how and when to remove this message)

In computer science, The System Contention Scope^[1] is one of two thread-scheduling schemes used in operating systems. This scheme is used by the kernel to decide which kernel-level thread to schedule onto a CPU, wherein all threads (as opposed to only user-level threads, as in the Process Contention Scope scheme) in the system compete for the CPU. Operating systems that use only the one-to-one model, such as Windows, Linux, and Solaris, schedule threads using only System Contention Scope.

References

edit

^ Silberschatz, Abraham, and Peter B. Galvin. "Thread Scheduling." Operating System Concepts. 8th ed. Hoboken, NJ: J. Wiley & Sons, 2005. 199. Print.

This operating-system-related article is a stub. You can help Wikipedia by expanding it.