Documentation: intel_pstate: Clarify coordination of P-State limits
Explain influence of per-core P-states and hyper threading on the effective performance. Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
This commit is contained in:
parent
af3b7379e2
commit
60935c17e2
@ -495,7 +495,15 @@ on the following rules, regardless of the current operation mode of the driver:
|
||||
|
||||
2. Each individual CPU is affected by its own per-policy limits (that is, it
|
||||
cannot be requested to run faster than its own per-policy maximum and it
|
||||
cannot be requested to run slower than its own per-policy minimum).
|
||||
cannot be requested to run slower than its own per-policy minimum). The
|
||||
effective performance depends on whether the platform supports per core
|
||||
P-states, hyper-threading is enabled and on current performance requests
|
||||
from other CPUs. When platform doesn't support per core P-states, the
|
||||
effective performance can be more than the policy limits set on a CPU, if
|
||||
other CPUs are requesting higher performance at that moment. Even with per
|
||||
core P-states support, when hyper-threading is enabled, if the sibling CPU
|
||||
is requesting higher performance, the other siblings will get higher
|
||||
performance than their policy limits.
|
||||
|
||||
3. The global and per-policy limits can be set independently.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user