With the addition of the patchset to allow auto-detection and use
of the intel_pstate kernel driver instead of the acpi-cpufreq kernel
driver, we need to reflect this in the documentation.
Now, instead of telling the user to disable intel_pstate in all cases,
it is now an optional step, should the user want to use acpi-cpufreq.
Signed-off-by: David Hunt <david.hunt@intel.com>
Acked-by: Marko Kovacevic <marko.kovacevic@intel.com>
Added a new performance test tool to test the compressdev PMD. The tool tests
compression ratio and compression throughput.
+* **Added intel_pstate support to Power Management library.**
+
+ Previously, using the power management library required the
+ disabling of the intel_pstate kernel driver, and the enabling of the
+ acpi_cpufreq kernel driver. This is no longer the case, as the use of
+ the intel_pstate kernel driver is now supported, and automatically
+ detected by the library.
+
Removed Items
-------------
Host Operating System
~~~~~~~~~~~~~~~~~~~~~
-The Host OS must also have the *apci_cpufreq* module installed, in some cases
-the *intel_pstate* driver may be the default Power Management environment.
-To enable *acpi_cpufreq* and disable *intel_pstate*, add the following
-to the grub Linux command line:
+The DPDK Power Library can use either the *acpi_cpufreq* or *intel_pstate*
+kernel driver for the management of core frequencies. In many cases
+the *intel_pstate* driver is the default Power Management environment.
+
+Should the *acpi-cpufreq* driver be required, the *intel_pstate* module must
+be disabled, and *apci_cpufreq* module loaded in its place.
+
+To disable *intel_pstate* driver, add the following to the grub Linux
+command line:
.. code-block:: console