linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@osdl.org, mbligh@mbligh.org, a.p.zijlstra@chello.nl,
	linux-mm@kvack.org, torvalds@osdl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: inactive-clean list
Date: Wed, 19 Jul 2006 00:59:53 +0900	[thread overview]
Message-ID: <20060719005953.5e34f4f1.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0607180742580.31065@schroedinger.engr.sgi.com>

On Tue, 18 Jul 2006 07:45:21 -0700 (PDT)
Christoph Lameter <clameter@sgi.com> wrote:

> On Tue, 18 Jul 2006, Andrew Morton wrote:
> 
> > Christoph Lameter <clameter@sgi.com> wrote:
> > > What other types of non freeable pages could exist?
> > 
> > PageWriteback() pages (potentially all of memory)
> 
> Doesnt write throttling take care of that?
> 
> > Pinned pages (various transient conditions, mainly get_user_pages())
> 
> Hmm....
>  
> > Some pages whose buffers are attached to an ext3 journal.
> 
> These are just pinned by an increased refcount right?
>  
> > Possibly NFS unstable pages.
> 
> These are tracked by NR_NFS_UNSTABLE.
> 
> Maybe we need a NR_UNSTABLE that includes pinned pages?
> 

I'm not sure what was discussed in VM summit. If I miss the point, sorry.

I think the important thing here is the amount of free pages we try to keep.
Remaining unused pages as page cache(and not free them) may help performance if lucky
but increases uncertainity.
 

Now, enlarging min_free_kbytes or mempool is useful to avoid page allocation failure 
in device drivers, which does write-back of dirty pages.
I think controlling free memory itself is better than controlling *used* inactive clean
pages.

Bye
-Kame


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

  reply	other threads:[~2006-07-18 15:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17 20:24 Peter Zijlstra
2006-07-18  3:37 ` Christoph Lameter
2006-07-18 12:16   ` Peter Zijlstra
2006-07-18 13:29     ` Christoph Lameter
2006-07-18 13:55       ` Martin J. Bligh
2006-07-18 13:59         ` Christoph Lameter
2006-07-18 15:12           ` Martin J. Bligh
2006-07-18 15:57             ` Christoph Lameter
2006-07-18 16:23               ` Martin J. Bligh
2006-07-18 14:03         ` Christoph Lameter
2006-07-18 14:25           ` Andrew Morton
2006-07-18 14:45             ` Christoph Lameter
2006-07-18 15:59               ` KAMEZAWA Hiroyuki [this message]
2006-07-23  5:50 ` Rik van Riel
2006-07-24 18:11   ` Christoph Lameter
2006-07-24 19:00     ` Rik van Riel
2006-07-25 20:25       ` Christoph Lameter
2006-07-25 21:37         ` Rik van Riel
2006-07-25 23:03           ` Christoph Lameter
2006-07-26  0:02             ` Rik van Riel
2006-07-26  0:05               ` Christoph Lameter
2006-07-26 11:00   ` Martin Schwidefsky
2006-07-26 11:11     ` Peter Zijlstra
2006-07-26 13:04       ` Martin Schwidefsky
2006-07-26 14:45         ` Peter Zijlstra
2006-07-27 11:16           ` Martin Schwidefsky
2006-07-26 15:41         ` Rik van Riel

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=20060719005953.5e34f4f1.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mbligh@mbligh.org \
    --cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox