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: [PATCH 6/7] mm: page_alloc: Only account batch allocations requests that are eligible Date: Tue, 17 Dec 2013 16:06:06 +0000 [thread overview] Message-ID: <20131217160606.GE11295@suse.de> (raw) In-Reply-To: <20131217154351.GD21724@cmpxchg.org> On Tue, Dec 17, 2013 at 10:43:51AM -0500, Johannes Weiner wrote: > On Tue, Dec 17, 2013 at 11:20:07AM +0000, Mel Gorman wrote: > > On Mon, Dec 16, 2013 at 03:52:37PM -0500, Johannes Weiner wrote: > > > On Fri, Dec 13, 2013 at 02:10:06PM +0000, Mel Gorman wrote: > > > > Not signed off. Johannes, was the intent really to decrement the batch > > > > counts regardless of whether the policy was being enforced or not? > > > > > > Yes. Bursts of allocations for which the policy does not get enforced > > > will still create memory pressure and affect cache aging on a given > > > node. So even if we only distribute page cache, we want to distribute > > > it in a way that all allocations on the eligible zones equal out. > > > > This means that allocations for page table pages affects the distribution of > > page cache pages. An adverse workload could time when it faults anonymous > > pages (to allocate anon and page table pages) in batch sequences and then > > access files to force page cache pages to be allocated from a single node. > > > > I think I know what your response will be. It will be that the utilisation of > > the zone for page table pages and anon pages means that you want more page > > cache pages to be allocated from the other zones so the reclaim pressure > > is still more or less even. If this is the case or there is another reason > > then it could have done with a comment because it's a subtle detail. > > Yes, that was the idea, that the cache placement compensates for pages > that still are always allocated on the preferred zone first, so that > the end result is approximately as if round-robin had been applied to > everybody. > Ok, understood. I wanted to be sure that was the thinking behind it. > This should be documented as part of the patch that first diverges > between the allocations that are counted and the allocations that are > round-robined: > > mm: page_alloc: exclude unreclaimable allocations from zone fairness policy > > I'm updating my tree. I'll leave it alone in mine then. We'll figure out how to sync up later. -- Mel Gorman SUSE Labs
WARNING: multiple messages have this Message-ID (diff)
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: [PATCH 6/7] mm: page_alloc: Only account batch allocations requests that are eligible Date: Tue, 17 Dec 2013 16:06:06 +0000 [thread overview] Message-ID: <20131217160606.GE11295@suse.de> (raw) In-Reply-To: <20131217154351.GD21724@cmpxchg.org> On Tue, Dec 17, 2013 at 10:43:51AM -0500, Johannes Weiner wrote: > On Tue, Dec 17, 2013 at 11:20:07AM +0000, Mel Gorman wrote: > > On Mon, Dec 16, 2013 at 03:52:37PM -0500, Johannes Weiner wrote: > > > On Fri, Dec 13, 2013 at 02:10:06PM +0000, Mel Gorman wrote: > > > > Not signed off. Johannes, was the intent really to decrement the batch > > > > counts regardless of whether the policy was being enforced or not? > > > > > > Yes. Bursts of allocations for which the policy does not get enforced > > > will still create memory pressure and affect cache aging on a given > > > node. So even if we only distribute page cache, we want to distribute > > > it in a way that all allocations on the eligible zones equal out. > > > > This means that allocations for page table pages affects the distribution of > > page cache pages. An adverse workload could time when it faults anonymous > > pages (to allocate anon and page table pages) in batch sequences and then > > access files to force page cache pages to be allocated from a single node. > > > > I think I know what your response will be. It will be that the utilisation of > > the zone for page table pages and anon pages means that you want more page > > cache pages to be allocated from the other zones so the reclaim pressure > > is still more or less even. If this is the case or there is another reason > > then it could have done with a comment because it's a subtle detail. > > Yes, that was the idea, that the cache placement compensates for pages > that still are always allocated on the preferred zone first, so that > the end result is approximately as if round-robin had been applied to > everybody. > Ok, understood. I wanted to be sure that was the thinking behind it. > This should be documented as part of the patch that first diverges > between the allocations that are counted and the allocations that are > round-robined: > > mm: page_alloc: exclude unreclaimable allocations from zone fairness policy > > I'm updating my tree. I'll leave it alone in mine then. We'll figure out how to sync up later. -- 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>
next prev parent reply other threads:[~2013-12-17 16:06 UTC|newest] Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-13 14:10 [RFC PATCH 0/7] Configurable fair allocation zone policy v2r6 Mel Gorman 2013-12-13 14:10 ` Mel Gorman 2013-12-13 14:10 ` [PATCH 1/7] mm: page_alloc: exclude unreclaimable allocations from zone fairness policy Mel Gorman 2013-12-13 14:10 ` Mel Gorman 2013-12-13 15:45 ` Rik van Riel 2013-12-13 15:45 ` Rik van Riel 2013-12-13 14:10 ` [PATCH 2/7] mm: page_alloc: Break out zone page aging distribution into its own helper Mel Gorman 2013-12-13 14:10 ` Mel Gorman 2013-12-13 15:46 ` Rik van Riel 2013-12-13 15:46 ` Rik van Riel 2013-12-16 20:16 ` Johannes Weiner 2013-12-16 20:16 ` Johannes Weiner 2013-12-13 14:10 ` [PATCH 3/7] mm: page_alloc: Use zone node IDs to approximate locality Mel Gorman 2013-12-13 14:10 ` Mel Gorman 2013-12-16 13:20 ` Rik van Riel 2013-12-16 13:20 ` Rik van Riel 2013-12-16 20:25 ` Johannes Weiner 2013-12-16 20:25 ` Johannes Weiner 2013-12-17 11:13 ` Mel Gorman 2013-12-17 11:13 ` Mel Gorman 2013-12-17 15:38 ` Johannes Weiner 2013-12-17 15:38 ` Johannes Weiner 2013-12-17 16:08 ` Mel Gorman 2013-12-17 16:08 ` Mel Gorman 2013-12-17 20:11 ` Johannes Weiner 2013-12-17 20:11 ` Johannes Weiner 2013-12-17 21:03 ` Mel Gorman 2013-12-17 21:03 ` Mel Gorman 2013-12-17 22:31 ` Johannes Weiner 2013-12-17 22:31 ` Johannes Weiner 2013-12-13 14:10 ` [PATCH 4/7] mm: Annotate page cache allocations Mel Gorman 2013-12-13 14:10 ` Mel Gorman 2013-12-16 15:20 ` Rik van Riel 2013-12-16 15:20 ` Rik van Riel 2013-12-13 14:10 ` [PATCH 5/7] mm: page_alloc: Make zone distribution page aging policy configurable Mel Gorman 2013-12-13 14:10 ` Mel Gorman 2013-12-16 19:25 ` Rik van Riel 2013-12-16 19:25 ` Rik van Riel 2013-12-16 20:42 ` Johannes Weiner 2013-12-16 20:42 ` Johannes Weiner 2013-12-17 15:29 ` Mel Gorman 2013-12-17 15:29 ` Mel Gorman 2013-12-17 15:54 ` Johannes Weiner 2013-12-17 15:54 ` Johannes Weiner 2013-12-17 16:14 ` Mel Gorman 2013-12-17 16:14 ` Mel Gorman 2013-12-17 17:43 ` Johannes Weiner 2013-12-17 17:43 ` Johannes Weiner 2013-12-17 21:22 ` Mel Gorman 2013-12-17 21:22 ` Mel Gorman 2013-12-17 22:57 ` Johannes Weiner 2013-12-17 22:57 ` Johannes Weiner 2013-12-17 23:24 ` Mel Gorman 2013-12-17 23:24 ` Mel Gorman 2013-12-13 14:10 ` [PATCH 6/7] mm: page_alloc: Only account batch allocations requests that are eligible Mel Gorman 2013-12-13 14:10 ` Mel Gorman 2013-12-16 20:52 ` Johannes Weiner 2013-12-16 20:52 ` Johannes Weiner 2013-12-17 11:20 ` Mel Gorman 2013-12-17 11:20 ` Mel Gorman 2013-12-17 15:43 ` Johannes Weiner 2013-12-17 15:43 ` Johannes Weiner 2013-12-17 16:06 ` Mel Gorman [this message] 2013-12-17 16:06 ` Mel Gorman 2013-12-13 14:10 ` [PATCH 7/7] mm: page_alloc: Default allow file pages to use remote nodes for fair allocation policy Mel Gorman 2013-12-13 14:10 ` Mel Gorman 2013-12-13 17:04 ` Johannes Weiner 2013-12-13 17:04 ` Johannes Weiner 2013-12-13 19:20 ` Mel Gorman 2013-12-13 19:20 ` Mel Gorman 2013-12-13 22:15 ` Johannes Weiner 2013-12-13 22:15 ` Johannes Weiner 2013-12-17 16:04 ` Mel Gorman 2013-12-17 16:04 ` Mel Gorman 2013-12-16 19:26 ` Rik van Riel 2013-12-16 19:26 ` Rik van Riel 2013-12-17 15:07 ` [RFC PATCH 0/7] Configurable fair allocation zone policy v2r6 Zlatko Calusic 2013-12-17 15:07 ` Zlatko Calusic 2013-12-17 21:23 ` Mel Gorman 2013-12-17 21:23 ` Mel Gorman 2013-12-21 16:03 ` Zlatko Calusic 2013-12-21 16:03 ` Zlatko Calusic 2013-12-23 10:26 ` Mel Gorman 2013-12-23 10:26 ` 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=20131217160606.GE11295@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: linkBe 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.