diff options
Diffstat (limited to 'doc/guides/sample_app_ug/vm_power_management.rst')
| -rw-r--r-- | doc/guides/sample_app_ug/vm_power_management.rst | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/doc/guides/sample_app_ug/vm_power_management.rst b/doc/guides/sample_app_ug/vm_power_management.rst index 5be9f24d..a7b7a2c7 100644 --- a/doc/guides/sample_app_ug/vm_power_management.rst +++ b/doc/guides/sample_app_ug/vm_power_management.rst @@ -339,7 +339,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. @@ -379,7 +379,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 @@ -592,7 +592,7 @@ Profile destroy example: .. code-block:: javascript - {"profile": { + {"policy": { "name": "ubuntu", "command": "destroy", }} @@ -601,8 +601,9 @@ Power command example: .. code-block:: javascript - {"command": { + {"instruction": { "name": "ubuntu", + "command": "power", "unit": "SCALE_MAX", "resource_id": 10 }} @@ -729,7 +730,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 @@ -737,7 +738,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 @@ -745,7 +746,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 |