[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140418130543.8619064c0e5d26cd914c4c3c@linux-foundation.org>
Date: Fri, 18 Apr 2014 13:05:43 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Mel Gorman <mgorman@...e.de>
Cc: Robert Haas <robertmhaas@...il.com>,
Josh Berkus <josh@...iodbs.com>,
Andres Freund <andres@...quadrant.com>,
Christoph Lameter <cl@...ux.com>,
Linux-MM <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
Michal Hocko <mhocko@...e.cz>
Subject: Re: [PATCH 0/2] Disable zone_reclaim_mode by default v2
On Tue, 8 Apr 2014 09:22:58 +0100 Mel Gorman <mgorman@...e.de> wrote:
> Changelog since v1
> o topology comment updates
>
> 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
> enabled 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.
>
This patchset conflicts with
commit 70ef57e6c22c3323dce179b7d0d433c479266612
Author: Michal Hocko <mhocko@...e.cz>
AuthorDate: Mon Apr 7 15:37:01 2014 -0700
Commit: Linus Torvalds <torvalds@...ux-foundation.org>
CommitDate: Mon Apr 7 16:35:50 2014 -0700
mm: exclude memoryless nodes from zone_reclaim
It was pretty simple to resolve, but please check that I didn't miss
anything.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists