From: Christoph Lameter <clameter@sgi.com>
To: akpm@osdl.org
Cc: schamp@sgi.com, linux-mm@kvack.org
Subject: ZVC/zone_reclaim: Leave 1% of unmapped pagecache pages for file I/O
Date: Thu, 29 Jun 2006 19:51:38 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606291949320.30754@schroedinger.engr.sgi.com> (raw)
It turns out that it is advantageous to leave a small portion of
unmapped file backed pages if a zone is overallocated.
This allows recently used file I/O buffers to stay on the node and
reduces the times that zone reclaim is invoked if file I/O occurs
when we run out of memory in a zone.
Signed-off-by: Christoph Lameter <clameter@sgi.com>
Index: linux-2.6.17-mm4/mm/vmscan.c
===================================================================
--- linux-2.6.17-mm4.orig/mm/vmscan.c 2006-06-29 13:34:13.128150411 -0700
+++ linux-2.6.17-mm4/mm/vmscan.c 2006-06-29 19:44:54.717779791 -0700
@@ -1598,18 +1598,22 @@ int zone_reclaim(struct zone *zone, gfp_
int node_id;
/*
- * Do not reclaim if there are not enough reclaimable pages in this
- * zone that would satify this allocations.
+ * Zone reclaim reclaims unmapped file backed pages.
*
- * All unmapped pagecache pages are reclaimable.
+ * A small portion of unmapped file backed pages is needed for
+ * file I/O otherwise pages read by file I/O will be immediately
+ * thrown out if the zone is overallocated. So we do not reclaim
+ * if less than 1% of the zone is used by unmapped file backed pages.
*
- * Both counters may be temporarily off a bit so we use
- * SWAP_CLUSTER_MAX as the boundary. It may also be good to
- * leave a few frequently used unmapped pagecache pages around.
+ * The division by 128 approximates this and is here because a division
+ * would be too expensive in this hot code path.
+ *
+ * Is it be useful to have a way to set the limit via /proc?
*/
if (zone_page_state(zone, NR_FILE_PAGES) -
- zone_page_state(zone, NR_FILE_MAPPED) < SWAP_CLUSTER_MAX)
- return 0;
+ zone_page_state(zone, NR_FILE_MAPPED) <
+ zone->present_pages / 128)
+ return 0;
/*
* Avoid concurrent zone reclaims, do not reclaim in a zone that does
--
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 reply other threads:[~2006-06-30 2:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 2:51 Christoph Lameter [this message]
2006-06-30 3:07 ` Andrew Morton
2006-06-30 6:08 ` Christoph Lameter
2006-06-30 10:19 ` Andi Kleen
2006-06-30 21:14 ` Christoph Lameter
2006-06-30 23:38 ` Andrew Morton
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=Pine.LNX.4.64.0606291949320.30754@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=schamp@sgi.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