cpusets,isolcpus: resolve conflict between cpusets and isolcpus
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 7 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | cpusets,isolcpus: exclude isolcpus from load balancing in cpusetsinclude/ kernel/ kernel/ | +14 | 1 reply | |
| 2/2 | cpusets,isolcpus: add file to show isolated cpus in cpusetkernel/ | +27 | 2 replies |
Reviews trailers per patch
None of the 2 patches has a Reviewed-by or Acked-by.
| Patch | David Rientjes |
|---|---|
| 1/2 | T-b |
| 2/2 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] cpusets,isolcpus: resolve conflict between cpusets and isolcpus
Ensure that cpus specified with the isolcpus= boot commandline option stay outside of the load balancing in the kernel scheduler.
Operations like load balancing can introduce unwanted latencies, which is exactly what the isolcpus= commandline is there to prevent.
Previously, simply creating a new cpuset, without even touching the cpuset.cpus field inside the new cpuset, would undo the effects of isolcpus=, by creating a scheduler domain spanning the whole system, and setting up load balancing inside that domain. The cpuset root cpuset.cpus file is read-only, so there was not even a way to undo that effect.
This does not impact the majority of cpusets users, since isolcpus= is a fairly specialized feature used for realtime purposes.