[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090321102044.GA3427@cmpxchg.org>
Date: Sat, 21 Mar 2009 11:20:44 +0100
From: Johannes Weiner <hannes@...xchg.org>
To: Lee Schermerhorn <Lee.Schermerhorn@...com>
Cc: David Howells <dhowells@...hat.com>,
Minchan Kim <minchan.kim@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
kosaki.motohiro@...fujitsu.com, torvalds@...ux-foundation.org,
peterz@...radead.org, nrik.Berkhan@...com, uclinux-dev@...inux.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, riel@...riel.com
Subject: Re: [PATCH 0/2] Make the Unevictable LRU available on NOMMU
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@...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 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.
I will sent this mondayish, need to test it more especially on a NOMMU
setup.
Hannes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists