Lines Matching refs:performance
17 :doc:`CPU performance scaling subsystem <cpufreq>` in the Linux kernel
25 than just an operating frequency or an operating performance point (see the
30 uses frequencies for identifying operating performance points of CPUs and
84 active mode: ``powersave`` and ``performance``. The way they both operate
90 Namely, if that option is set, the ``performance`` algorithm will be used by
113 HWP + ``performance``
119 internal P-state selection logic is expected to focus entirely on performance.
136 internal P-state selection logic to be less performance-focused.
150 ``powersave`` or ``performance``, depending on the ``scaling_governor`` policy
155 ``performance``
180 every 10 ms. Like in the ``performance`` case, the hardware configuration
237 performance scaling control for that core and put it into turbo P-states of its
280 used relative to ACPI-based CPU performance scaling (see `below <acpi-cpufreq_>`_
336 maximum supported performance level (the highest supported `turbo
345 maximum supported performance level (the highest supported `turbo
389 of this mechanism is to improve performance).
501 effective performance depends on whether the platform supports per core
502 P-states, hyper-threading is enabled and on current performance requests
504 effective performance can be more than the policy limits set on a CPU, if
505 other CPUs are requesting higher performance at that moment. Even with per
507 is requesting higher performance, the other siblings will get higher
508 performance than their policy limits.
531 selection logic by focusing it on performance or on energy-efficiency, or
535 Current value of the energy vs performance hint for the given policy
544 They represent different energy vs performance hints and should be
554 load-balancing algorithm and if different energy vs performance hints are
556 issues it is better to set the same energy vs performance hint for all CPUs
566 that can be used for CPU performance scaling (refer to the ACPI specification
572 the ``acpi-cpufreq`` driver uses the same hardware CPU performance scaling
594 ``performance``.
661 Take ACPI ``_PPC`` performance limits into account.