From: Peter Zijlstra <peterz@infradead.org>
To: Mel Gorman <mgorman@suse.de>
Cc: Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, Aubrey Li <aubrey.li@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Juri Lelli <juri.lelli@redhat.com>
Subject: Re: [GIT PULL] scheduler changes for v5.7
Date: Tue, 31 Mar 2020 15:48:13 +0200 [thread overview]
Message-ID: <20200331134813.GQ20730@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200331103333.GM3772@suse.de>
On Tue, Mar 31, 2020 at 11:33:33AM +0100, Mel Gorman wrote:
> On Mon, Mar 30, 2020 at 07:31:59PM +0200, Ingo Molnar wrote:
> > 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: 313f16e2e35abb833eab5bdebc6ae30699adca18 Merge branch 'sched/rt' into sched/core, to pick up completed topic tree
> >
> > The main changes in this cycle are:
> >
> > - Various NUMA scheduling updates: harmonize the load-balancer and NUMA
> > placement logic to not work against each other. The intended result is
> > better locality, better utilization and fewer migrations.
> >
>
> Thanks Ingo.
>
> I noticed that the following patch did not make it to the list.
>
> sched/fair: Fix negative imbalance in imbalance calculation
> https://lore.kernel.org/lkml/1585201349-70192-1-git-send-email-aubrey.li@intel.com/
I have it, we'll get it in before the next release.
prev parent reply other threads:[~2020-03-31 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 17:31 [GIT PULL] scheduler changes for v5.7 Ingo Molnar
2020-03-31 0:25 ` pr-tracker-bot
2020-03-31 10:33 ` Mel Gorman
2020-03-31 13:48 ` Peter Zijlstra [this message]
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=20200331134813.GQ20730@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=aubrey.li@intel.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vincent.guittot@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).