Content deleted Content added
Achaemenes (usurped) (talk | contribs) No edit summary |
Achaemenes (usurped) (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
Ultimately a user-level [[thread (computer science)]] is mapped to a kernel-level one via a scheme called [[Process Contention Scope (PCS)]]. The name is derived from the fact that the processes and threads are contending for a kernel process. |
Ultimately a user-level [[thread (computer science)|thread]] is mapped to a kernel-level one via a scheme called [[Process Contention Scope (PCS)|process contention scope]]. The name is derived from the fact that the processes and threads are contending for a kernel process. |
||
The Operating System decides which kernel-thread to run based on a scheme called [[System Contention Scope (SCS)]] since the threads are contending for the system/processor. |
The Operating System decides which kernel-thread to run based on a scheme called [[System Contention Scope (SCS)|system contention scope (SCS)]] since the threads are contending for the system/processor. |
||
{{computer-stub}} |
{{computer-stub}} |
||
Revision as of 09:20, 15 February 2006
Ultimately a user-level thread is mapped to a kernel-level one via a scheme called process contention scope. The name is derived from the fact that the processes and threads are contending for a kernel process.
The Operating System decides which kernel-thread to run based on a scheme called system contention scope (SCS) since the threads are contending for the system/processor.