mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@techsingularity.net>
To: Linux-Stable <stable@vger.kernel.org>
Cc: Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Mel Gorman <mgorman@techsingularity.net>
Subject: [PATCH 4.3-stable 0/5] Disable automatic numa balancing on UMA
Date: Thu,  7 Jan 2016 17:57:31 +0000	[thread overview]
Message-ID: <1452189456-8486-1-git-send-email-mgorman@techsingularity.net> (raw)

Automatic NUMA balancing only makes sense on NUMA machines but was enabled
in 4.3 on UMA by commit 2a1ed24 ("sched/numa: Prefer NUMA hotness over
cache hotness") and is still enabled in 4.3.3 despite the fixes being in
mainline. With this series applied, UMA has zero automatic NUMA-related
page table updates as expected.

 kernel/sched/core.c     | 18 ++++++------------
 kernel/sched/fair.c     |  8 ++++----
 kernel/sched/features.h | 16 ----------------
 kernel/sched/sched.h    | 12 +-----------
 4 files changed, 11 insertions(+), 43 deletions(-)

-- 
2.6.4

             reply	other threads:[~2016-01-07 17:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07 17:57 Mel Gorman [this message]
2016-01-07 17:57 ` [PATCH 1/5] sched/numa: Rename numabalancing_enabled to sched_numa_balancing Mel Gorman
2016-01-07 17:57 ` [PATCH 2/5] sched/numa: Disable sched_numa_balancing on UMA systems Mel Gorman
2016-01-07 17:57 ` [PATCH 3/5] sched/numa: Remove the NUMA sched_feature Mel Gorman
2016-01-07 17:57 ` [PATCH 4/5] sched/numa: Convert sched_numa_balancing to a static_branch Mel Gorman
2016-01-07 17:57 ` [PATCH 5/5] sched/numa: Fix task_tick_fair() from disabling numa_balancing Mel Gorman

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=1452189456-8486-1-git-send-email-mgorman@techsingularity.net \
    --to=mgorman@techsingularity.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=srikar@linux.vnet.ibm.com \
    --cc=stable@vger.kernel.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

Powered by JetHome