The patch titled
sched: increase ksoftirqd priority
has been removed from the -mm tree. Its filename was
sched-increase-ksoftirqd-priority.patch
This patch was dropped because I need to clear the decks
------------------------------------------------------
Subject: sched: increase ksoftirqd priority
From: Con Kolivas <kernel@xxxxxxxxxxx>
More aggressive nice discrimination by the Staircase-Deadline cpu scheduler
means ksoftirqd is getting significantly less cpu than previously. Adjust
nice value accordingly for similar cpu distribution.
Signed-off-by: Con Kolivas <kernel@xxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
kernel/softirq.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -puN kernel/softirq.c~sched-increase-ksoftirqd-priority kernel/softirq.c
--- a/kernel/softirq.c~sched-increase-ksoftirqd-priority
+++ a/kernel/softirq.c
@@ -489,7 +489,7 @@ void __init softirq_init(void)
static int ksoftirqd(void * __bind_cpu)
{
- set_user_nice(current, 19);
+ set_user_nice(current, 15);
current->flags |= PF_NOFREEZE;
set_current_state(TASK_INTERRUPTIBLE);
_
Patches currently in -mm which might be from kernel@xxxxxxxxxxx are
sched-fix-idle-load-balancing-in-softirqd-context-fix.patch
sched-redundant-reschedule-when-set_user_nice-boosts-a-prio-of-a-task-from-the-expired-array.patch
sched-redundant-reschedule-when-set_user_nice-boosts-a-prio-of-a-task-from-the-expired-array-update.patch
sched-increase-ksoftirqd-priority.patch
sched-remove-noninteractive-flag.patch
sched-document-sd-cpu-scheduler.patch
sched-implement-staircase-deadline-scheduler-rework-priomatrix-doc.patch
sched-consolidate-sched_clock-drift-adjustments.patch
sched-consolidate-sched_clock-drift-adjustments-fix.patch
sched-implement-staircase-deadline-scheduler-docupdate.patch
sched-add-above-background-load-function.patch
mm-implement-swap-prefetching.patch
swap-prefetch-avoid-repeating-entry.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
