From: Mel Gorman <mgorman@techsingularity.net>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Jirka Hladky <jhladky@redhat.com>,
Rik van Riel <riel@surriel.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
Mel Gorman <mgorman@techsingularity.net>
Subject: [PATCH 0/2] Faster migration for automatic NUMA balancing
Date: Mon, 1 Oct 2018 11:05:23 +0100 [thread overview]
Message-ID: <20181001100525.29789-1-mgorman@techsingularity.net> (raw)
These two patches are based on top of Srikar Dronamraju's recent work
on automatic NUMA balancing and are motivated by a bug report from Jirka
Hladky that STREAM performance has regressed.
The STREAM workload is mildly interesting in that it only works as a valid
benchmark if tasks are pinned to memory channels. Otherwise it is very
sensitive to the starting conditions of the benchmark. Recent scheduler
changes prevent prematurely spreading a workload across multiple sockets
which benefits many workloads but not STREAM. This series restores STREAM
performance without reintroducing other regressions.
The first patch removes migration rate limiting as it's expected that
automatic NUMA balancing decisions are mature enough that we do not
need the safety net. The second patch migrates pages faster early in the
lifetime of the process which has an impact if the load balancer spreads
a workload to remote nodes.
include/linux/mmzone.h | 6 ----
include/trace/events/migrate.h | 27 ------------------
kernel/sched/fair.c | 12 +++++++-
mm/migrate.c | 65 ------------------------------------------
mm/page_alloc.c | 2 --
5 files changed, 11 insertions(+), 101 deletions(-)
--
2.16.4
next reply other threads:[~2018-10-01 10:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 10:05 Mel Gorman [this message]
2018-10-01 10:05 ` [PATCH 1/2] mm, numa: Remove rate-limiting of automatic numa balancing migration Mel Gorman
2018-10-01 15:39 ` Rik van Riel
2018-10-02 10:17 ` [tip:sched/urgent] mm, sched/numa: Remove rate-limiting of automatic NUMA " tip-bot for Mel Gorman
2018-10-02 11:54 ` [PATCH 1/2] mm, numa: Remove rate-limiting of automatic numa " Srikar Dronamraju
2018-10-01 10:05 ` [PATCH 2/2] mm, numa: Migrate pages to local nodes quicker early in the lifetime of a task Mel Gorman
2018-10-01 15:41 ` Rik van Riel
2018-10-02 10:17 ` [tip:sched/urgent] sched/numa: " tip-bot for Mel Gorman
2018-10-02 12:41 ` [PATCH 2/2] mm, numa: " Srikar Dronamraju
2018-10-02 13:54 ` Mel Gorman
2018-10-02 17:30 ` Srikar Dronamraju
2018-10-02 18:22 ` Mel Gorman
2018-10-03 13:15 ` Srikar Dronamraju
2018-10-03 13:07 ` Srikar Dronamraju
2018-10-03 13:21 ` Mel Gorman
2018-10-03 14:08 ` Srikar Dronamraju
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=20181001100525.29789-1-mgorman@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=jhladky@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=srikar@linux.vnet.ibm.com \
/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.