From: Rik van Riel <riel@redhat.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Lee Schermerhorn <lee.schermerhorn@hp.com>,
Kosaki Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux-mm@kvack.org, Eric Whitney <eric.whitney@hp.com>
Subject: Re: [PATCH -mm 14/24] Ramfs and Ram Disk pages are unevictable
Date: Thu, 12 Jun 2008 13:29:52 -0400 [thread overview]
Message-ID: <20080612132952.568226f6@cuia.bos.redhat.com> (raw)
In-Reply-To: <200806121054.19253.nickpiggin@yahoo.com.au>
On Thu, 12 Jun 2008 10:54:18 +1000
Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> On Thursday 12 June 2008 04:42, Rik van Riel wrote:
> > From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
> >
> > Christoph Lameter pointed out that ram disk pages also clutter the
> > LRU lists. When vmscan finds them dirty and tries to clean them,
> > the ram disk writeback function just redirties the page so that it
> > goes back onto the active list. Round and round she goes...
> This isn't the case for brd any longer. It doesn't use the buffer
> cache as its backing store, so the buffer cache is reclaimable.
What does that mean?
I know that pages of files that got paged into the page
cache from the ramdisk can be evicted (back to the ram
disk), but how do the brd pages themselves behave?
--
All Rights Reversed
--
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:[~2008-06-12 17:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080611184214.605110868@redhat.com>
2008-06-11 18:42 ` [PATCH -mm 12/24] Unevictable LRU Infrastructure Rik van Riel
2008-06-11 18:42 ` [PATCH -mm 14/24] Ramfs and Ram Disk pages are unevictable Rik van Riel
2008-06-12 0:54 ` Nick Piggin
2008-06-12 17:29 ` Rik van Riel [this message]
2008-06-12 17:37 ` Nick Piggin
2008-06-12 17:50 ` Rik van Riel
2008-06-12 17:57 ` Nick Piggin
2008-06-11 18:42 ` [PATCH -mm 16/24] mlock: mlocked " Rik van Riel, Nick Piggin
2008-06-11 18:42 ` [PATCH -mm 18/24] mmap: handle mlocked pages during map, remap, unmap Rik van Riel
2008-06-11 18:42 ` [PATCH -mm 20/24] swap: cull unevictable pages in fault path Rik van Riel, Lee Schermerhorn
2008-06-11 18:42 ` [PATCH -mm 22/24] vmscan: unevictable LRU scan sysctl Rik van Riel, Lee Schermerhorn
2008-06-11 18:42 ` [PATCH -mm 24/24] doc: unevictable LRU and mlocked pages documentation Rik van Riel
[not found] ` <20080611184339.159161465@redhat.com>
[not found] ` <4851C1CC.7070607@ct.jp.nec.com>
[not found] ` <20080613134827.5dbac5ac@cuia.bos.redhat.com>
2008-06-13 20:21 ` [PATCH] collect lru meminfo statistics from correct offset Lee Schermerhorn
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=20080612132952.568226f6@cuia.bos.redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=eric.whitney@hp.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
/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