RFC sched: Reduce runqueue lock contention -v3
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest17 patches 31 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/17 | sched: Always provide p->on_cpuinclude/ kernel/ | +30 | 0 replies | |
| 2/17 | mutex: Use p->on_cpu for the adaptive spininclude/ include/ kernel/ +4 more | +39 | 0 replies | |
| 3/17 | sched: Change the ttwu success detailskernel/ | +8 | 0 replies | |
| 4/17 | sched: Clean up ttwu statskernel/ | +32 | 0 replies | |
| 5/17 | x86: Optimize arch_spin_unlock_wait()arch/ | +23 | 12 replies | |
| 6/17 | sched: Provide p->on_rqinclude/ kernel/ kernel/ +2 more | +26 | 1 reply | |
| 7/17 | sched: Serialize p->cpus_allowed and ttwu() using p->pi_lockkernel/ | +16 | 2 replies | |
| 8/17 | sched: Drop the rq argument to sched_class::select_task_rq()include/ kernel/ kernel/ +3 more | +27 | 13 replies | |
| 9/17 | sched: Remove rq argument to sched_class::task_waking()include/ kernel/ kernel/ | +11 | 0 replies | |
| 10/17 | sched: Add TASK_WAKING to task_rq_lockkernel/ | +7 | 0 replies | |
| 11/17 | sched: Delay task_contributes_to_load()include/ kernel/ | +5 | 0 replies | |
| 12/17 | sched: Also serialize ttwu_local() with p->pi_lockkernel/ | +17 | 2 replies | |
| 13/17 | sched: Remove rq->lock from the first half of ttwu()kernel/ kernel/ | +30 | 0 replies | |
| 14/17 | sched: Remove rq argument to ttwu_stat()kernel/ | +5 | 2 replies | |
| 15/17 | sched: Rename ttwu_post_activationkernel/ | +6 | 0 replies | |
| 16/17 | sched: Move the second half of ttwu() to the remote cpuarch/ include/ kernel/ +1 more | +114 | 6 replies | |
| 17/17 | sched: Sort hotplug vs ttwu queueingkernel/ | +18 | 2 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC][PATCH 00/17] sched: Reduce runqueue lock contention -v3
This is the latest incarnation of my scary ttwu patch, its split up into tiny little pieces because at some point while working on the feedback from the last posting it all stopped working and tiny changes was the only way to find out wth I done wrong (I never did find out though, when I completely rewrote everything in tiny chunks it all magically worked again -- so I guess tglx is chuckling now).
Anyway, it still need a few more loose ends fixed, esp on 32bit there is the whole unlocked remote min_vruntime access where we can read partial updates and screw the timeline like problem. And I suppose there's a few more XXXs in there where I know things are needing TLC.
Also, I bet the eagle eyed lot Cc'ed will spot more holes, as all this is scary stuff :-)
Anyway, lots of thanks to Frank, Oleg, Ingo and others who commented on the last posting.
I guess most everybody is out having x-mas celebrations (and I will too not too long from now), so I expect replies to this won't happen until the new year, but who knows, maybe in between eating and drinking too much we all get an urge to stare at code.
Happy Holidays!