RFC Series short description
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest3 patches 8 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | sched: track the next-highest priority on each runqueuekernel/ kernel/ | +81 | 0 replies | |
| 2/3 | sched: use highest_prio.curr for pull thresholdkernel/ | +6 | 0 replies | |
| 3/3 | sched: use highest_prio.next to optimize pull operationskernel/ | +12 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/3] Series short description
Hi Ingo, Steven, Peter,
This series applies roughly to mainline as an enhancement to the sched_rt logic. Peter and I were discussing some of the unecessary overhead in pull_rt_tasks() via IRC, and this is my RFC attempt to address the problem.
I have built/booted this on a 4-way C2D Xeon box and it passes preempt-test.
Comments, please.
-Greg
---
Gregory Haskins (3):
sched: use highest_prio.next to optimize pull operations
sched: use highest_prio.curr for pull threshold
sched: track the next-highest priority on each runqueue
kernel/sched.c | 8 ++- kernel/sched_rt.c | 158 +++++++++++++++++++++++++++++++---------------------- 2 files changed, 99 insertions(+), 67 deletions(-)
Signature · 1 line
Signature