From: Mel Gorman <mgorman@suse.de>
To: Christoph Lameter <cl@linux.com>
Cc: sivanich@sgi.com, Andrew Morton <akpm@linux-foundation.org>,
Robert Haas <robertmhaas@gmail.com>,
Josh Berkus <josh@agliodbs.com>,
Andres Freund <andres@2ndquadrant.com>,
Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] mm: Disable zone_reclaim_mode by default
Date: Tue, 8 Apr 2014 15:47:35 +0100 [thread overview]
Message-ID: <20140408144735.GK7292@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.10.1404080910040.8782@nuc>
On Tue, Apr 08, 2014 at 09:14:05AM -0500, Christoph Lameter wrote:
> On Mon, 7 Apr 2014, Mel Gorman wrote:
>
> > zone_reclaim_mode causes processes to prefer reclaiming memory from local
> > node instead of spilling over to other nodes. This made sense initially when
> > NUMA machines were almost exclusively HPC and the workload was partitioned
> > into nodes. The NUMA penalties were sufficiently high to justify reclaiming
> > the memory. On current machines and workloads it is often the case that
> > zone_reclaim_mode destroys performance but not all users know how to detect
> > this. Favour the common case and disable it by default. Users that are
> > sophisticated enough to know they need zone_reclaim_mode will detect it.
>
> Ok that is going to require SGI machines to deal with zone_reclaim
> configurations on bootup. Dimitri? Any comments?
>
The SGI machines are also likely to be managed by system administrators
who are both aware of zone_reclaim_mode and know how to evaluate if it
should be enabled or not. The pair of patches is really aimmed at the
common case of 2-8 socket machines running workloads that are not NUMA
aware.
--
Mel Gorman
SUSE Labs
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mgorman@suse.de>
To: Christoph Lameter <cl@linux.com>
Cc: sivanich@sgi.com, Andrew Morton <akpm@linux-foundation.org>,
Robert Haas <robertmhaas@gmail.com>,
Josh Berkus <josh@agliodbs.com>,
Andres Freund <andres@2ndquadrant.com>,
Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] mm: Disable zone_reclaim_mode by default
Date: Tue, 8 Apr 2014 15:47:35 +0100 [thread overview]
Message-ID: <20140408144735.GK7292@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.10.1404080910040.8782@nuc>
On Tue, Apr 08, 2014 at 09:14:05AM -0500, Christoph Lameter wrote:
> On Mon, 7 Apr 2014, Mel Gorman wrote:
>
> > zone_reclaim_mode causes processes to prefer reclaiming memory from local
> > node instead of spilling over to other nodes. This made sense initially when
> > NUMA machines were almost exclusively HPC and the workload was partitioned
> > into nodes. The NUMA penalties were sufficiently high to justify reclaiming
> > the memory. On current machines and workloads it is often the case that
> > zone_reclaim_mode destroys performance but not all users know how to detect
> > this. Favour the common case and disable it by default. Users that are
> > sophisticated enough to know they need zone_reclaim_mode will detect it.
>
> Ok that is going to require SGI machines to deal with zone_reclaim
> configurations on bootup. Dimitri? Any comments?
>
The SGI machines are also likely to be managed by system administrators
who are both aware of zone_reclaim_mode and know how to evaluate if it
should be enabled or not. The pair of patches is really aimmed at the
common case of 2-8 socket machines running workloads that are not NUMA
aware.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2014-04-08 14:47 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 22:34 [PATCH 0/2] Disable zone_reclaim_mode by default Mel Gorman
2014-04-07 22:34 ` Mel Gorman
2014-04-07 22:34 ` [PATCH 1/2] mm: " Mel Gorman
2014-04-07 22:34 ` Mel Gorman
2014-04-07 23:35 ` Johannes Weiner
2014-04-07 23:35 ` Johannes Weiner
2014-04-08 1:17 ` Zhang Yanfei
2014-04-08 1:17 ` Zhang Yanfei
2014-04-08 7:14 ` Andres Freund
2014-04-08 7:14 ` Andres Freund
2014-04-08 14:14 ` Christoph Lameter
2014-04-08 14:14 ` Christoph Lameter
2014-04-08 14:47 ` Mel Gorman [this message]
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 22:34 ` Mel Gorman
2014-04-07 23:36 ` Johannes Weiner
2014-04-07 23:36 ` Johannes Weiner
2014-04-08 1:17 ` Zhang Yanfei
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 7:26 ` Vlastimil Babka
2014-04-08 14:17 ` Christoph Lameter
2014-04-08 14:17 ` Christoph Lameter
2014-04-08 14:26 ` Andres Freund
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 14:46 ` Josh Berkus
2014-04-08 19:53 ` Robert Haas
2014-04-08 19:53 ` Robert Haas
[not found] ` <WM!55d2a092da9f6180473043487a4eb612ae8195f78d2ffdd83f673ed5cb2cb9659cf61e0c8d5bae23f5c914057bcd2ee4!@asav-3.01.com>
2014-04-08 19:56 ` Josh Berkus
2014-04-08 19:56 ` Josh Berkus
2014-04-09 13:08 ` Mel Gorman
2014-04-09 13:08 ` Mel Gorman
2014-04-08 22:58 ` Christoph Lameter
2014-04-08 22:58 ` Christoph Lameter
2014-04-08 23:26 ` Mel Gorman
2014-04-08 23:26 ` Mel Gorman
2014-04-10 10:26 ` Jeremy Harris
2014-04-10 10:26 ` Jeremy Harris
2014-04-18 15:49 ` Michal Hocko
2014-04-18 15:49 ` Michal Hocko
2014-04-18 16:44 ` Christoph Lameter
2014-04-18 16:44 ` Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2014-04-08 8:22 [PATCH 0/2] Disable zone_reclaim_mode by default v2 Mel Gorman
2014-04-08 8:22 ` [PATCH 1/2] mm: Disable zone_reclaim_mode by default Mel Gorman
2014-04-08 8:22 ` 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=20140408144735.GK7292@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 \
--cc=sivanich@sgi.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.