From: Rik van Riel <riel@redhat.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Mel Gorman <mgorman@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Hansen <dave.hansen@intel.com>,
Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/6] Configurable fair allocation zone policy v3
Date: Wed, 18 Dec 2013 08:47:45 -0500 [thread overview]
Message-ID: <52B1A781.50002@redhat.com> (raw)
In-Reply-To: <20131218061750.GK21724@cmpxchg.org>
On 12/18/2013 01:17 AM, Johannes Weiner wrote:
> Updated version with your tmpfs __GFP_PAGECACHE parts added and
> documentation, changelog updated as necessary. I remain unconvinced
> that tmpfs pages should be round-robined, but I agree with you that it
> is the conservative change to do for 3.12 and 3.12 and we can figure
> out the rest later. I sure hope that this doesn't drive most people
> on NUMA to disable pagecache interleaving right away as I expect most
> tmpfs workloads to see little to no reclaim and prefer locality... :/
Actually, I suspect most tmpfs heavy workloads will be things like
databases with shared memory segments. Those tend to benefit from
having all of the system's memory bandwidth available. The worker
threads/processes tend to live all over the system, too...
--
All rights reversed
--
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: Rik van Riel <riel@redhat.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Mel Gorman <mgorman@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Hansen <dave.hansen@intel.com>,
Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/6] Configurable fair allocation zone policy v3
Date: Wed, 18 Dec 2013 08:47:45 -0500 [thread overview]
Message-ID: <52B1A781.50002@redhat.com> (raw)
In-Reply-To: <20131218061750.GK21724@cmpxchg.org>
On 12/18/2013 01:17 AM, Johannes Weiner wrote:
> Updated version with your tmpfs __GFP_PAGECACHE parts added and
> documentation, changelog updated as necessary. I remain unconvinced
> that tmpfs pages should be round-robined, but I agree with you that it
> is the conservative change to do for 3.12 and 3.12 and we can figure
> out the rest later. I sure hope that this doesn't drive most people
> on NUMA to disable pagecache interleaving right away as I expect most
> tmpfs workloads to see little to no reclaim and prefer locality... :/
Actually, I suspect most tmpfs heavy workloads will be things like
databases with shared memory segments. Those tend to benefit from
having all of the system's memory bandwidth available. The worker
threads/processes tend to live all over the system, too...
--
All rights reversed
next prev parent reply other threads:[~2013-12-18 13:47 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 16:48 [RFC PATCH 0/6] Configurable fair allocation zone policy v3 Mel Gorman
2013-12-17 16:48 ` Mel Gorman
2013-12-17 16:48 ` [PATCH 1/6] mm: page_alloc: exclude unreclaimable allocations from zone fairness policy Mel Gorman
2013-12-17 16:48 ` Mel Gorman
2013-12-17 16:48 ` [PATCH 2/6] mm: page_alloc: Break out zone page aging distribution into its own helper Mel Gorman
2013-12-17 16:48 ` Mel Gorman
2013-12-17 16:48 ` [PATCH 3/6] mm: page_alloc: Use zone node IDs to approximate locality Mel Gorman
2013-12-17 16:48 ` Mel Gorman
2013-12-17 16:48 ` [PATCH 4/6] mm: Annotate page cache allocations Mel Gorman
2013-12-17 16:48 ` Mel Gorman
2013-12-17 16:48 ` [PATCH 5/6] mm: page_alloc: Make zone distribution page aging policy configurable Mel Gorman
2013-12-17 16:48 ` Mel Gorman
2013-12-17 16:48 ` [PATCH 6/6] mm: page_alloc: add vm.pagecache_interleave to control default mempolicy for page cache Mel Gorman
2013-12-17 16:48 ` Mel Gorman
2013-12-17 20:02 ` [RFC PATCH 0/6] Configurable fair allocation zone policy v3 Johannes Weiner
2013-12-17 20:02 ` Johannes Weiner
2013-12-18 6:17 ` Johannes Weiner
2013-12-18 6:17 ` Johannes Weiner
2013-12-18 13:47 ` Rik van Riel [this message]
2013-12-18 13:47 ` Rik van Riel
2013-12-18 14:17 ` Johannes Weiner
2013-12-18 14:17 ` Johannes Weiner
2013-12-18 15:00 ` Mel Gorman
2013-12-18 15:00 ` Mel Gorman
2013-12-18 16:09 ` Mel Gorman
2013-12-18 16:09 ` Mel Gorman
2013-12-18 19:48 ` Johannes Weiner
2013-12-18 19:48 ` Johannes Weiner
2013-12-19 11:20 ` Mel Gorman
2013-12-19 11:20 ` Mel Gorman
2013-12-18 14:51 ` Michal Hocko
2013-12-18 14:51 ` Michal Hocko
2013-12-18 15:18 ` Johannes Weiner
2013-12-18 15:18 ` Johannes Weiner
2013-12-18 16:20 ` Michal Hocko
2013-12-18 16:20 ` Michal Hocko
2013-12-18 19:20 ` Johannes Weiner
2013-12-18 19:20 ` Johannes Weiner
2013-12-19 12:59 ` Michal Hocko
2013-12-19 12:59 ` Michal Hocko
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=52B1A781.50002@redhat.com \
--to=riel@redhat.com \
--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=mgorman@suse.de \
/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.