From: Mel Gorman <mgorman@suse.de>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Dave Hansen <dave.hansen@intel.com>,
Rik van Riel <riel@redhat.com>, Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/4] Configurable fair allocation zone policy
Date: Thu, 12 Dec 2013 15:34:22 +0000 [thread overview]
Message-ID: <20131212153422.GJ11295@suse.de> (raw)
In-Reply-To: <1386860779-2301-1-git-send-email-mgorman@suse.de>
On Thu, Dec 12, 2013 at 03:06:15PM +0000, Mel Gorman wrote:
> Commit 81c0a2bb ("mm: page_alloc: fair zone allocator policy") solved a
> bug whereby new pages could be reclaimed before old pages because of how
> the page allocator and kswapd interacted on the per-zone LRU lists.
>
> Unfortunately a side-effect missed during review was that it's now very
> easy to allocate remote memory on NUMA machines. The problem is that
> it is not a simple case of just restoring local allocation policies as
> there are genuine reasons why global page aging may be prefereable. It's
> still a major change to default behaviour so this patch makes the policy
> configurable and sets what I think is a sensible default.
>
> The patches are on top of some NUMA balancing patches currently in -mm.
> The first patch in the series is a patch posted by Johannes that must be
> taken into account before any of my patches on top. The last patch of the
> series is what alters default behaviour and makes the fair zone allocator
> policy configurable.
>
> Sniff test results based on following kernels
>
> vanilla 3.13-rc3 stock
> instrument-v5r1 NUMA balancing patches just to rule out any conflicts there
> lruslabonly-v1r2 Patch 1 only
> local-v1r2 Full series
>
These figures need to be redone. The instrument-v5r1 and later kernels
included a debugging patch that increases migration rates to trigger
another bug. The figures of local-v1r2 relative to instrument-v5r1 are
fine but not relative to 3.13.0-rc3-vanilla
--
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>
prev parent reply other threads:[~2013-12-12 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 15:06 [RFC PATCH 0/4] Configurable fair allocation zone policy Mel Gorman
2013-12-12 15:06 ` [PATCH 1/4] mm: page_alloc: exclude unreclaimable allocations from zone fairness policy Mel Gorman
2013-12-12 15:06 ` [PATCH 2/4] mm: page_alloc: Break out zone page aging distribution into its own helper Mel Gorman
2013-12-12 15:06 ` [PATCH 3/4] mm: page_alloc: Use zone node IDs to approximate locality Mel Gorman
2013-12-12 15:06 ` [PATCH 4/4] mm: page_alloc: Make zone distribution page aging policy configurable Mel Gorman
2013-12-12 15:34 ` Mel Gorman [this message]
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=20131212153422.GJ11295@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.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).