cpusets,isolcpus: exclude isolcpus from load balancing in cpusets
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v4 Latest posting 2/24 patches 9 repliesIn review
- v4 posting 1/24 patches 1 replySuperseded
- v12 patches 9 repliesSuperseded
Patches in v4 posting 2/2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | sched,isolcpu: make cpu_isolated_map visible outside schedulerinclude/ kernel/ | +5 | 0 replies | |
| 2/4 | cpusets,isolcpus: exclude isolcpus from load balancing in cpusetskernel/ | +11 | 0 replies | |
| 3/4 | cpusets,isolcpus: add file to show isolated cpus in cpusetkernel/ | +22 | 7 replies | |
| 4/4 | cpuset,isolcpus: document relationship between cpusets & isolcpusDocumentation/ | +8 | 0 replies |
Reviews trailers per patch
1 of 4 patches has a Reviewed-by or Acked-by.
| Patch | David Rientjes |
|---|---|
| 1/4 | |
| 2/4 | T-b |
| 3/4 | A-b |
| 4/4 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v4 RESEND 0/4] cpusets,isolcpus: exclude isolcpus from load balancing in cpusets
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.
This version fixes the UP compilation issue, in the same way done for the other cpumasks.