linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Aubrey Li" <aubreylee@gmail.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	svaidy@linux.vnet.ibm.com, nickpiggin@yahoo.com.au,
	rgetz@blackfin.uclinux.org, Michael.Hennerich@analog.com,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Bryan Wu <cooloney.lkml@gmail.com>
Subject: Re: [RFC] Limit the size of the pagecache
Date: Wed, 24 Jan 2007 13:47:44 +0800	[thread overview]
Message-ID: <6d6a94c50701232147g7453fe79q6ce0df94da2ac749@mail.gmail.com> (raw)
In-Reply-To: <20070124115310.48cda374.kamezawa.hiroyu@jp.fujitsu.com>

Christoph's patch is better than mine. The only thing I think is that
zone->max_pagecache_pages should be checked never less than
zone->pages_low.

The good part of the patch is using the existing reclaimer. But the
problem in my opinion of the idea is the existing reclaimer too. Think
of  when vfs cache limit is
hit, reclaimer doesn't reclaim all of the reclaimable pages, it just
give few out. So next time vfs pagecache request, it is quite possible
reclaimer is triggered again. That means after limit is hit, reclaim
will be implemented every time fs ops allocating memory. That's the
point in my mind impacting the performance of the applications.

-Aubrey

--
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>

  parent reply	other threads:[~2007-01-24  5:47 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24  0:49 [RFC] Limit the size of the pagecache Christoph Lameter
2007-01-24  2:53 ` KAMEZAWA Hiroyuki
2007-01-24  3:01   ` Christoph Lameter
2007-01-24  5:47   ` Aubrey Li [this message]
2007-01-24  3:00 ` Nick Piggin
2007-01-24  3:14   ` Christoph Lameter
2007-01-24  3:51     ` Aubrey Li
2007-01-24  4:03       ` Nick Piggin
2007-01-26 10:27         ` Andrew Morton
2007-01-24  3:13 ` KAMEZAWA Hiroyuki
2007-01-24  4:30   ` Christoph Lameter
2007-01-24  5:15     ` KAMEZAWA Hiroyuki
2007-01-25  0:32       ` KAMEZAWA Hiroyuki
2007-01-25  2:41         ` Christoph Lameter
2007-01-25  3:12           ` KAMEZAWA Hiroyuki
2007-01-25  4:28             ` Rik van Riel
2007-01-25  5:19               ` KAMEZAWA Hiroyuki
2007-01-25  5:40                 ` Rik van Riel
2007-01-25  6:00                   ` KAMEZAWA Hiroyuki
2007-01-26 10:29       ` Andrew Morton
2007-01-26 18:01         ` KAMEZAWA Hiroyuki
2007-01-24  7:04 ` Vaidyanathan Srinivasan
2007-01-24  7:55 ` Peter Zijlstra
2007-01-24 12:50   ` Nick Piggin
2007-01-24 12:58     ` Peter Zijlstra
2007-01-24 14:58     ` Christoph Lameter
2007-01-24 20:06       ` Erik Andersen
2007-01-25  2:40         ` Christoph Lameter
2007-01-25  8:07           ` Vaidyanathan Srinivasan
2007-01-24 14:22   ` Aubrey Li
2007-01-24 14:56     ` Peter Zijlstra
2007-01-25  2:27       ` Aubrey Li
2007-01-24 12:33 ` Vaidyanathan Srinivasan
2007-01-24 14:56   ` Christoph Lameter
2007-01-25  4:17     ` Vaidyanathan Srinivasan
2007-01-25  4:45       ` Rik van Riel
2007-01-25  5:49         ` Vaidyanathan Srinivasan
2007-01-25 16:07           ` Rik van Riel
2007-01-25 17:57             ` Balbir Singh
2007-01-25  6:35       ` Aubrey Li
2007-01-25  6:47         ` Christoph Lameter
2007-01-25  7:49         ` Vaidyanathan Srinivasan
2007-01-25  4:18 ` Rik van Riel
     [not found] <7GEEK-4lH-39@gated-at.bofh.it>
     [not found] ` <7GLdb-5Uz-13@gated-at.bofh.it>
     [not found]   ` <7GRix-7fU-1@gated-at.bofh.it>
     [not found]     ` <7GRLZ-7Uy-29@gated-at.bofh.it>
2007-01-25 14:51       ` Bodo Eggert

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=6d6a94c50701232147g7453fe79q6ce0df94da2ac749@mail.gmail.com \
    --to=aubreylee@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=clameter@sgi.com \
    --cc=cooloney.lkml@gmail.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=rgetz@blackfin.uclinux.org \
    --cc=svaidy@linux.vnet.ibm.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).