summaryrefslogtreecommitdiff
path: root/kernel/latencytop.c
diff options
context:
space:
mode:
authorGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-10-06 01:39:38 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-10-06 01:39:38 +0300
commit8be673735e5144e13fe739fba5a0a33fc50f3a16 (patch)
tree66612de0994ff7ff115a5071903f2a1301f6d4b1 /kernel/latencytop.c
parent1df377db3d0131057fa33b4dcda05c3e341308ab (diff)
parent37355bdc5a129899f6b245900a8eb944a092f7fd (diff)
downloadlinux-8be673735e5144e13fe739fba5a0a33fc50f3a16.tar.xz
Merge branch 'sched-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Ingo writes: "scheduler fixes: These fixes address a rather involved performance regression between v4.17->v4.19 in the sched/numa auto-balancing code. Since distros really need this fix we accelerated it to sched/urgent for a faster upstream merge. NUMA scheduling and balancing performance is now largely back to v4.17 levels, without reintroducing the NUMA placement bugs that v4.18 and v4.19 fixed. Many thanks to Srikar Dronamraju, Mel Gorman and Jirka Hladky, for reporting, testing, re-testing and solving this rather complex set of bugs." * 'sched-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: sched/numa: Migrate pages to local nodes quicker early in the lifetime of a task mm, sched/numa: Remove rate-limiting of automatic NUMA balancing migration sched/numa: Avoid task migration for small NUMA improvement mm/migrate: Use spin_trylock() while resetting rate limit sched/numa: Limit the conditions where scan period is reset sched/numa: Reset scan rate whenever task moves across nodes sched/numa: Pass destination CPU as a parameter to migrate_task_rq sched/numa: Stop multiple tasks from moving to the CPU at the same time
Diffstat (limited to 'kernel/latencytop.c')
0 files changed, 0 insertions, 0 deletions