From: "John Stoffel" <john@stoffel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mel Gorman <mgorman@suse.de>, 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>,
Michal Hocko <mhocko@suse.cz>
Subject: Re: [PATCH 0/2] Disable zone_reclaim_mode by default v2
Date: Fri, 18 Apr 2014 16:48:25 -0400 [thread overview]
Message-ID: <21329.36761.970643.523119@quad.stoffel.home> (raw)
In-Reply-To: <20140418130543.8619064c0e5d26cd914c4c3c@linux-foundation.org>
>>>>> "Andrew" == Andrew Morton <akpm@linux-foundation.org> writes:
Andrew> On Tue, 8 Apr 2014 09:22:58 +0100 Mel Gorman <mgorman@suse.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.
This is unclear here. "see major performance <what> due" doesn't make
sense to me.
--
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>
next prev parent reply other threads:[~2014-04-18 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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:23 ` [PATCH 2/2] mm: page_alloc: Do not cache reclaim distances Mel Gorman
2014-04-18 20:05 ` [PATCH 0/2] Disable zone_reclaim_mode by default v2 Andrew Morton
2014-04-18 20:48 ` John Stoffel [this message]
2014-04-20 20:59 ` 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=21329.36761.970643.523119@quad.stoffel.home \
--to=john@stoffel.org \
--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=mgorman@suse.de \
--cc=mhocko@suse.cz \
--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).