summaryrefslogtreecommitdiff
path: root/doc/guides/sample_app_ug/vm_power_management.rst
diff options
context:
space:
mode:
authorJohn McNamara <john.mcnamara@intel.com>2019-04-26 16:14:21 +0100
committerThomas Monjalon <thomas@monjalon.net>2019-05-03 00:37:13 +0200
commitd629b7b5fe812f0040b83d27d2ada33b003aa918 (patch)
tree6fd76c3a26a84f3af3355a280b5a30f7f49c8834 /doc/guides/sample_app_ug/vm_power_management.rst
parent194a83d837472a27030e55af95b1103c90c2c63a (diff)
downloaddpdk-d629b7b5fe812f0040b83d27d2ada33b003aa918.zip
dpdk-d629b7b5fe812f0040b83d27d2ada33b003aa918.tar.gz
dpdk-d629b7b5fe812f0040b83d27d2ada33b003aa918.tar.xz
doc: fix spelling reported by aspell in guides
Fix spelling errors in the guide docs. Signed-off-by: John McNamara <john.mcnamara@intel.com> Acked-by: Rami Rosen <ramirose@gmail.com>
Diffstat (limited to 'doc/guides/sample_app_ug/vm_power_management.rst')
-rw-r--r--doc/guides/sample_app_ug/vm_power_management.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/guides/sample_app_ug/vm_power_management.rst b/doc/guides/sample_app_ug/vm_power_management.rst
index 14d432e..109d109 100644
--- a/doc/guides/sample_app_ug/vm_power_management.rst
+++ b/doc/guides/sample_app_ug/vm_power_management.rst
@@ -344,7 +344,7 @@ monitoring of branch ratio on cores doing busy polling via PMDs.
When this parameter is used, the list of cores specified will monitor the ratio
between branch hits and branch misses. A tightly polling PMD thread will have a
- very low branch ratio, so the core frequency will be scaled down to the minimim
+ very low branch ratio, so the core frequency will be scaled down to the minimum
allowed value. When packets are received, the code path will alter, causing the
branch ratio to increase. When the ratio goes above the ratio threshold, the
core frequency will be scaled up to the maximum allowed value.
@@ -384,7 +384,7 @@ the file.
The fifo is at /tmp/powermonitor/fifo
-The jason string can be a policy or instruction, and takes the following
+The JSON string can be a policy or instruction, and takes the following
format:
.. code-block:: javascript
@@ -734,7 +734,7 @@ policy down to the host application. These parameters are as follows:
A comma-separated list of cores in the VM that the user wants the host application to
monitor. The list of cores in any vm starts at zero, and these are mapped to the
physical cores by the host application once the policy is passed down.
- Valid syntax includes individial cores '2,3,4', or a range of cores '2-4', or a
+ Valid syntax includes individual cores '2,3,4', or a range of cores '2-4', or a
combination of both '1,3,5-7'
.. code-block:: console
@@ -742,7 +742,7 @@ policy down to the host application. These parameters are as follows:
--busy-hours {list of busy hours}
A comma-separated list of hours within which to set the core frequency to maximum.
- Valid syntax includes individial hours '2,3,4', or a range of hours '2-4', or a
+ Valid syntax includes individual hours '2,3,4', or a range of hours '2-4', or a
combination of both '1,3,5-7'. Valid hours are 0 to 23.
.. code-block:: console
@@ -750,7 +750,7 @@ policy down to the host application. These parameters are as follows:
--quiet-hours {list of quiet hours}
A comma-separated list of hours within which to set the core frequency to minimum.
- Valid syntax includes individial hours '2,3,4', or a range of hours '2-4', or a
+ Valid syntax includes individual hours '2,3,4', or a range of hours '2-4', or a
combination of both '1,3,5-7'. Valid hours are 0 to 23.
.. code-block:: console