From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] scheduler changes for v4.18
Date: Mon, 4 Jun 2018 14:12:20 +0200 [thread overview]
Message-ID: <20180604121220.GA31206@gmail.com> (raw)
Linus,
Please pull the latest sched-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched-core-for-linus
# HEAD: 2539fc82aa9b07d968cf9ba1ffeec3e0416ac721 sched/fair: Update util_est before updating schedutil
The main changes in this cycle were:
- power-aware scheduling improvements (Patrick Bellasi)
- NUMA balancing improvements (Mel Gorman)
- vCPU scheduling fixes (Rohit Jain)
Thanks,
Ingo
------------------>
Claudio Scordino (1):
sched/deadline/Documentation: Add overrun signal and GRUB-PA documentation
Mel Gorman (1):
sched/numa: Stagger NUMA balancing scan periods for new threads
Patrick Bellasi (2):
sched/cpufreq: Modify aggregate utilization to always include blocked FAIR utilization
sched/fair: Update util_est before updating schedutil
Rohit Jain (2):
sched/core: Don't schedule threads on pre-empted vCPUs
sched/core: Distinguish between idle_cpu() calls based on desired effect, introduce available_idle_cpu()
Sebastian Andrzej Siewior (1):
sched/wait: Include <linux/wait.h> in <linux/swait.h>
Viresh Kumar (2):
sched/fair: Rearrange select_task_rq_fair() to optimize it
sched/fair: Avoid calling sync_entity_load_avg() unnecessarily
Documentation/scheduler/sched-deadline.txt | 25 +++++-
include/linux/sched.h | 1 +
include/linux/swait.h | 1 +
kernel/sched/core.c | 39 +++++-----
kernel/sched/cpufreq_schedutil.c | 17 ++---
kernel/sched/fair.c | 117 +++++++++++++++++++----------
kernel/sched/sched.h | 6 ++
7 files changed, 137 insertions(+), 69 deletions(-)
reply other threads:[~2018-06-04 12:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180604121220.GA31206@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.