Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Commit

Permalink
docs: Fix capitalization
Browse files Browse the repository at this point in the history
Correct an incorrectly capitalized term.

Fixes: #576.

Signed-off-by: James O. D. Hunt <[email protected]>
  • Loading branch information
jodh-intel committed Jun 13, 2019
1 parent 4d55184 commit 0ead592
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions documentation/features/cpuset.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ The cpuset CPU cgroup will be applied on two events:
- container update

When the runtime requests to apply cpuset cgroup to the agent, the amount of
VCPUs available might not be the same to the required VCPUs in the request.
vCPUs available might not be the same to the required vCPUs in the request.

This is because the request from the agent client (i.e. the Kata runtime)
passes cpusets that are requested to be placed on the host. This isolates the
Expand Down Expand Up @@ -44,7 +44,7 @@ Here, the container is limited to 2 CPUs and can be scheduled on CPU 2, 3, and
4.

The Kata runtime only hotplugs 2 CPUs, making it impossible to request that the
guest kernel schedules the workload on vcpu 3 and 4.
guest kernel schedules the workload on vCPU 3 and 4.

## cpuset best effort application.

Expand Down

0 comments on commit 0ead592

Please sign in to comment.