From: Andrew Morton <akpm@osdl.org>
To: Mel Gorman <mel@csn.ul.ie>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to reclaim inode pages on demand
Date: Wed, 10 Aug 2005 10:17:14 -0700 [thread overview]
Message-ID: <20050810101714.147e1333.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0508101730441.11984@skynet>
Mel Gorman <mel@csn.ul.ie> wrote:
>
> On Mon, 8 Aug 2005, Andrew Morton wrote:
>
> > Mel Gorman <mel@csn.ul.ie> wrote:
> > >
> > > Hi,
> > >
> > > I am working on a direct reclaim strategy to free up large blocks of
> > > contiguous pages. The part I have is working fine, but I am finding a
> > > hundreds of pages that are being used for inodes that I need to reclaim. I
> > > tried purging the inode lists using a variation of prune_icache() but it
> > > is not working out.
> > >
> > > Given a struct page, that one knows is an inode, can anyone suggest the
> > > best way to find the inode using it and free it?
> >
> > Simple answer: invalidate_mapping_pages(page->mapping, start, end).
> >
>
> The majority of pages I am seeing no longer have page->mapping set. Does
> this mean they are in the process of being cleared up?
They're just anonymous pages, aren't they? But you said "pages that are
being used for inodes". Confused.
next prev parent reply other threads:[~2005-08-10 17:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 15:52 Mel Gorman
2005-08-08 16:08 ` Jörn Engel
2005-08-08 16:23 ` Mel Gorman
2005-08-08 23:08 ` Andrew Morton
2005-08-10 16:32 ` Mel Gorman
2005-08-10 17:17 ` Andrew Morton [this message]
2005-08-10 17:27 ` Mel Gorman
2005-08-10 17:40 ` Andrew Morton
2005-08-10 17:51 ` Mel Gorman
2005-08-10 17:52 ` Andrew Morton
2005-08-10 17:50 ` Dave Hansen
2005-08-10 17:59 ` Mel Gorman
2005-08-11 3:08 ` Magnus Damm
2005-08-11 4:44 ` Andrew Morton
2005-08-11 5:43 ` Magnus Damm
2005-08-11 9:09 ` Coywolf Qi Hunt
2005-08-11 14:09 ` Hugh Dickins
2005-08-09 4:06 ` 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=20050810101714.147e1333.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
/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
all inboxes | Powered by JetHome®