From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: David Howells <dhowells@redhat.com>,
Minchan Kim <minchan.kim@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
kosaki.motohiro@jp.fujitsu.com, torvalds@linux-foundation.org,
peterz@infradead.org, nrik.Berkhan@ge.com,
uclinux-dev@uclinux.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, riel@surriel.com
Subject: Re: [PATCH 0/2] Make the Unevictable LRU available on NOMMU
Date: Mon, 23 Mar 2009 16:07:40 -0400 [thread overview]
Message-ID: <1237838860.7334.59.camel@lts-notebook> (raw)
In-Reply-To: <20090321102044.GA3427@cmpxchg.org>
On Sat, 2009-03-21 at 11:20 +0100, Johannes Weiner wrote:
> On Fri, Mar 20, 2009 at 02:30:15PM -0400, Lee Schermerhorn wrote:
> > On Fri, 2009-03-20 at 16:24 +0000, David Howells wrote:
> > > Lee Schermerhorn <Lee.Schermerhorn@hp.com> wrote:
> > >
> > > > I just want to point out [again :)] that removing the ramfs pages from
> > > > the lru will prevent them from being migrated
> > >
> > > This is less of an issue for NOMMU kernels, since you can't migrate pages that
> > > are mapped.
> >
> >
> > Agreed. So, you could eliminate them [ramfs pages] from the lru for
> > just the nommu kernels, if you wanted to go that route.
>
> These pages don't come with much overhead anymore when they sit on the
> unevictable list, right? So I don't see much point in special casing
> them all over the place.
I agree: not much overhead; no NEED to special case. I was only
agreeing with David, that it would be OK to keep them off the LRU for
NOMMU kernels.
>
> I have a patchset that decouples the unevictable lru feature from
> mlock, enables the latter on nommu and then makes sure ramfs pages go
> immediately to the unevictable list so they don't need the scanner to
> move them. This is just wiring up of features we already have.
Yeah. I didn't do it that way, because I didn't see any benefit in
doing that for ram disk pages. If one doesn't run vmscan, having the
pages on the normal lru doesn't hurt. If you do need to run vmscan,
moving them to the unevictable list from there seems the least of your
problems :). And, doing in the pagevec flush function adds overhead to
the fault path. Granted, it's amortized over PAGEVEC_SIZE pages. Would
probably we worth measuring the performance cost. And any code size
increase--NOMMU kernel users might care about that.
>
> I will sent this mondayish, need to test it more especially on a NOMMU
> setup.
Saw them. Will take a look...
Lee
--
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:[~2009-03-23 18:55 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090311153034.9389.19938.stgit@warthog.procyon.org.uk>
2009-03-11 22:03 ` [PATCH] NOMMU: Pages allocated to a ramfs inode's pagecache may get wrongly discarded Andrew Morton
2009-03-11 22:36 ` Johannes Weiner
2009-03-12 0:02 ` Andrew Morton
2009-03-12 0:35 ` Minchan Kim
2009-03-12 1:04 ` KOSAKI Motohiro
2009-03-12 1:52 ` Minchan Kim
2009-03-12 1:56 ` Minchan Kim
2009-03-12 2:00 ` KOSAKI Motohiro
2009-03-12 2:11 ` Minchan Kim
2009-03-12 12:19 ` Robin Getz
2009-03-12 17:55 ` [uClinux-dev] " Jamie Lokier
2009-03-13 17:33 ` [PATCH 0/2] Make the Unevictable LRU available on NOMMU David Howells
2009-03-13 17:33 ` [PATCH 1/2] NOMMU: There is no mlock() for NOMMU, so don't provide the bits David Howells
2009-03-14 11:17 ` KOSAKI Motohiro
2009-03-13 17:33 ` [PATCH 2/2] NOMMU: Make CONFIG_UNEVICTABLE_LRU available when CONFIG_MMU=n David Howells
2009-03-14 11:17 ` KOSAKI Motohiro
2009-03-14 0:27 ` [PATCH 0/2] Make the Unevictable LRU available on NOMMU Minchan Kim
2009-03-20 16:08 ` Lee Schermerhorn
2009-03-20 16:24 ` David Howells
2009-03-20 18:30 ` Lee Schermerhorn
2009-03-21 10:20 ` Johannes Weiner
2009-03-22 20:13 ` [patch 1/3] mm: decouple unevictable lru from mmu Johannes Weiner
2009-03-22 23:46 ` KOSAKI Motohiro
2009-03-23 0:14 ` Johannes Weiner
2009-03-23 10:48 ` David Howells
2009-03-22 20:13 ` [patch 2/3] ramfs-nommu: use generic lru cache Johannes Weiner
2009-03-23 2:22 ` KOSAKI Motohiro
2009-03-22 20:13 ` [patch 3/3] mm: keep pages from unevictable mappings off the LRU lists Johannes Weiner
2009-03-23 0:44 ` Minchan Kim
2009-03-23 2:21 ` KOSAKI Motohiro
2009-03-23 8:42 ` Johannes Weiner
2009-03-23 9:01 ` KOSAKI Motohiro
2009-03-23 9:23 ` KOSAKI Motohiro
2009-03-26 0:48 ` Johannes Weiner
2009-03-23 10:40 ` [patch 2/3] ramfs-nommu: use generic lru cache David Howells
2009-03-23 10:53 ` [patch 3/3] mm: keep pages from unevictable mappings off the LRU lists David Howells
2009-03-26 0:01 ` Johannes Weiner
2009-03-26 8:56 ` KOSAKI Motohiro
2009-03-26 10:36 ` Johannes Weiner
2009-03-23 20:07 ` Lee Schermerhorn [this message]
2009-03-13 11:53 ` [PATCH] NOMMU: Pages allocated to a ramfs inode's pagecache may get wrongly discarded David Howells
2009-03-13 22:49 ` Johannes Weiner
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=1237838860.7334.59.camel@lts-notebook \
--to=lee.schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=nrik.Berkhan@ge.com \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=torvalds@linux-foundation.org \
--cc=uclinux-dev@uclinux.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;
as well as URLs for NNTP newsgroup(s).