RFC sched, hotplug: cpu-hotplug vs. sched synchronization
Get series with b4
b4 am 1216937156.5368.5.camel@earthVersions newest first
- v1 RFC Latest2 patches 9 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | sched, hotplug: safe use of rq->migration_thread and find_busiest_queue()kernel/ | +23 | 4 replies | |
| 2/2 | sched, hotplug: ensure a task is on the valid cpu after set_cpus_allowed_ptr()kernel/ | +14 | 5 replies |
Reviews trailers per patch
1 of 2 patches has a Reviewed-by or Acked-by.
| Patch | Peter Zijlstra |
|---|---|
| 1/2 | A-b |
| 2/2 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [patch, rfc: 0/2] sched, hotplug: cpu-hotplug vs. sched synchronization
Hi,
RFC, because I obviously might have missed something important and if not, there can be better ways to address the issues (a few alternatives included).
[1/2] safe use of rq->migration_thread and find_busiest_queue()
[2/2] ensure a task is on the valid cpu after set_cpus_allowed_ptr()
--Dmitry