In the general case, each thread (there may be thousands globally) is either ready and waiting to be scheduled on a logical processor, or is waiting for a system call to complete (the time may be indeterminant, such as when a process sleeps while waiting for an interrupt). All modern consumer operating systems use some variant of a preemptive multi-level priority queue scheduling algorithm to perform thread scheduling.
Specifically, when it becomes desirable to either park or unpark a core. When it becomes desirable to do so, the operating system can then wake up the core(s) and speed step them to its heart's content.The devil, at least as far as real time gaming performance is concerned, is in the details. This means that cores that were as "idle" as design permitted still accessed L2/元 cache and still drew power.Ĭore parking allows an operating system to completely shut off a core such that it no longer performs any function and draws little to no power. Independent speed stepping allowed each core to operate at an independent clock multiplier and VID, allowing fairly effective power management, but execution was still a global binary. When multi-core CPUs were developed circa 2005, these low power states required each core to halt collectively.
For a while, these low power states required the entire CPU to halt execution other components could often be powered off as well.
First, a bit of history.Ĭonsumer CPUs have long had low-power sleep states. However, most are too proud to admit as much, and proceed to make up a bunch of mumbo jumbo.Core parking is, at its simplest, a power saving mechanism. Core parking is one of those things that enthusiasts consistently fail to understand.
0 kommentar(er)
