From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-mm <linux-mm@kvack.org>
Subject: [PATCH] mm: cleanup and document reclaim recursion
Date: Thu, 16 Nov 2006 10:52:25 +0100 [thread overview]
Message-ID: <1163670745.5968.83.camel@twins> (raw)
In-Reply-To: <20061115140049.c835fbfd.akpm@osdl.org>
On Wed, 2006-11-15 at 14:00 -0800, Andrew Morton wrote:
> On Wed, 15 Nov 2006 22:32:58 +0100
> Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
>
> > + current->flags |= PF_MEMALLOC;
> > try_to_free_pages(zones, GFP_NOFS);
> > + current->flags &= ~PF_MEMALLOC;
>
> Sometime, later, in a different patch, we might as well suck that into
> try_to_free_pages() itself. Along with nice comment explaining
> what it means and WARN_ON(current->flags & PF_MEMALLOC).
---
Cleanup and document the reclaim recursion avoiding properties of PF_MEMALLOC.
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
---
fs/buffer.c | 9 +++++----
mm/page_alloc.c | 2 --
mm/vmscan.c | 15 +++++++++++++++
3 files changed, 20 insertions(+), 6 deletions(-)
Index: linux-2.6-git/fs/buffer.c
===================================================================
--- linux-2.6-git.orig/fs/buffer.c 2006-11-16 10:28:13.000000000 +0100
+++ linux-2.6-git/fs/buffer.c 2006-11-16 10:37:32.000000000 +0100
@@ -358,13 +358,14 @@ static void free_more_memory(void)
wakeup_pdflush(1024);
yield();
+ /* We're already in reclaim */
+ if (current->flags & PF_MEMALLOC)
+ return;
+
for_each_online_pgdat(pgdat) {
zones = pgdat->node_zonelists[gfp_zone(GFP_NOFS)].zones;
- if (*zones && !(current->flags & PF_MEMALLOC)) {
- current->flags |= PF_MEMALLOC;
+ if (*zones)
try_to_free_pages(zones, GFP_NOFS);
- current->flags &= ~PF_MEMALLOC;
- }
}
}
Index: linux-2.6-git/mm/page_alloc.c
===================================================================
--- linux-2.6-git.orig/mm/page_alloc.c 2006-11-16 10:28:13.000000000 +0100
+++ linux-2.6-git/mm/page_alloc.c 2006-11-16 10:37:32.000000000 +0100
@@ -1067,14 +1067,12 @@ rebalance:
/* We now go into synchronous reclaim */
cpuset_memory_pressure_bump();
- p->flags |= PF_MEMALLOC;
reclaim_state.reclaimed_slab = 0;
p->reclaim_state = &reclaim_state;
did_some_progress = try_to_free_pages(zonelist->zones, gfp_mask);
p->reclaim_state = NULL;
- p->flags &= ~PF_MEMALLOC;
cond_resched();
Index: linux-2.6-git/mm/vmscan.c
===================================================================
--- linux-2.6-git.orig/mm/vmscan.c 2006-11-16 10:28:13.000000000 +0100
+++ linux-2.6-git/mm/vmscan.c 2006-11-16 10:37:32.000000000 +0100
@@ -1030,6 +1030,20 @@ unsigned long try_to_free_pages(struct z
count_vm_event(ALLOCSTALL);
+ /*
+ * PF_MEMALLOC also keeps direct reclaim from recursing into itself.
+ * Any invocation of direct reclaim with PF_MEMALLOC set is therefore
+ * invalid.
+ *
+ * This makes sense, in that PF_MEMALLOC results in ALLOC_NO_WATERMARKS
+ * for allocations (except __GFP_NOMEMALLOC), which only makes sense
+ * for reclaim (or reclaim aiding) contexts. So starting reclaim
+ * from a context that either helps out reclaim or is reclaim doesn't
+ * make sense.
+ */
+ WARN_ON(current->flags & PF_MEMALLOC);
+ current->flags |= PF_MEMALLOC;
+
for (i = 0; zones[i] != NULL; i++) {
struct zone *zone = zones[i];
@@ -1093,6 +1107,7 @@ out:
zone->prev_priority = priority;
}
+ current->flags &= ~PF_MEMALLOC;
return ret;
}
--
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:[~2006-11-16 9:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 19:25 mm: call into direct reclaim without PF_MEMALLOC set Peter Zijlstra
2006-11-15 20:42 ` Andrew Morton
2006-11-15 21:23 ` [PATCH] " Peter Zijlstra
2006-11-15 21:32 ` Andrew Morton
[not found] ` <1163625058.5968.64.camel@twins>
[not found] ` <20061115132340.3cbf4008.akpm@osdl.org>
2006-11-15 21:32 ` Peter Zijlstra
2006-11-15 22:00 ` Andrew Morton
2006-11-15 22:12 ` Arjan van de Ven
2006-11-15 22:24 ` Andrew Morton
2006-11-16 9:52 ` Peter Zijlstra [this message]
2006-11-17 0:16 ` [PATCH] mm: cleanup and document reclaim recursion Andrew Morton
2006-11-17 8:31 ` Peter Zijlstra
2006-11-17 12:18 ` Peter Zijlstra
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=1163670745.5968.83.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
/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.