linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Robert Haas <robertmhaas@gmail.com>,
	Josh Berkus <josh@agliodbs.com>,
	Andres Freund <andres@2ndquadrant.com>,
	Christoph Lameter <cl@linux.com>, Linux-MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>, Mel Gorman <mgorman@suse.de>
Subject: [PATCH 0/2] Disable zone_reclaim_mode by default
Date: Mon,  7 Apr 2014 23:34:26 +0100	[thread overview]
Message-ID: <1396910068-11637-1-git-send-email-mgorman@suse.de> (raw)

When it was introduced, zone_reclaim_mode made sense as NUMA distances
punished and workloads were generally partitioned to fit into a NUMA
node. NUMA machines are now common but few of the workloads are NUMA-aware
and it's routine to see major performance due to zone_reclaim_mode being
disabled but relatively few can identify the problem.

Those that require zone_reclaim_mode are likely to be able to detect when
it needs to be enabled and tune appropriately so lets have a sensible
default for the bulk of users.

 Documentation/sysctl/vm.txt | 17 +++++++++--------
 include/linux/mmzone.h      |  1 -
 mm/page_alloc.c             | 17 +----------------
 3 files changed, 10 insertions(+), 25 deletions(-)

-- 
1.8.4.5

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2014-04-07 22:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 22:34 Mel Gorman [this message]
2014-04-07 22:34 ` [PATCH 1/2] mm: Disable zone_reclaim_mode by default Mel Gorman
2014-04-07 23:35   ` Johannes Weiner
2014-04-08  1:17   ` Zhang Yanfei
2014-04-08  7:14   ` Andres Freund
2014-04-08 14:14   ` Christoph Lameter
2014-04-08 14:47     ` Mel Gorman
2014-04-07 22:34 ` [PATCH 2/2] mm: page_alloc: Do not cache reclaim distances Mel Gorman
2014-04-07 23:36   ` Johannes Weiner
2014-04-08  1:17   ` Zhang Yanfei
2014-04-08  7:26 ` [PATCH 0/2] Disable zone_reclaim_mode by default Vlastimil Babka
2014-04-08 14:17   ` Christoph Lameter
2014-04-08 14:26     ` Andres Freund
     [not found]     ` <WM!ea1193ee171854a74828ee30c859d97ff2ce66405ffa3a0b8c31a1233c6a0b55530cdf3cbfcd989c0ec18fef1d533f81!@asav-3.01.com>
2014-04-08 14:46       ` Josh Berkus
2014-04-08 19:53     ` Robert Haas
     [not found]       ` <WM!55d2a092da9f6180473043487a4eb612ae8195f78d2ffdd83f673ed5cb2cb9659cf61e0c8d5bae23f5c914057bcd2ee4!@asav-3.01.com>
2014-04-08 19:56         ` Josh Berkus
2014-04-09 13:08           ` Mel Gorman
2014-04-08 22:58       ` Christoph Lameter
2014-04-08 23:26         ` Mel Gorman
2014-04-10 10:26         ` Jeremy Harris
2014-04-18 15:49 ` Michal Hocko
2014-04-18 16:44   ` Christoph Lameter

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=1396910068-11637-1-git-send-email-mgorman@suse.de \
    --to=mgorman@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=andres@2ndquadrant.com \
    --cc=cl@linux.com \
    --cc=josh@agliodbs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=robertmhaas@gmail.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 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).