From: Coywolf Qi Hunt <coywolf@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
mel@csn.ul.ie, linux-kernel@vger.kernel.org
Subject: Re: How to reclaim inode pages on demand
Date: Thu, 11 Aug 2005 17:09:31 +0800 [thread overview]
Message-ID: <2cd57c900508110209de388f2@mail.gmail.com> (raw)
In-Reply-To: <20050811144441.54b6ef4a.akpm@osdl.org>
On 8/11/05, Andrew Morton <akpm@osdl.org> wrote:
> Magnus Damm <magnus.damm@gmail.com> wrote:
> >
> > On 8/11/05, Andrew Morton <akpm@osdl.org> wrote:
> > > Mel Gorman <mel@csn.ul.ie> wrote:
> > > > 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.
> >
> > I thought page->mapping was used by rmap for both inode-backed and
> > anonymous pages. And the PAGE_MAPPING_ANON bit was used to determine
> > that page->mapping points to struct anon_vma instead of struct
> > address_space.
> >
> > When is page->mapping NULL?
> >
>
> mm.h:page_mapping() handles all that.
at http://sosdg.org/~coywolf/lxr/source/include/linux/mm.h#L561
Should the comment be s/page_mapped/page->mapping/ ?
--
Coywolf Qi Hunt
http://ahbl.org/~coywolf/
next prev parent reply other threads:[~2005-08-11 9:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 15:52 How to reclaim inode pages on demand 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
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 [this message]
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=2cd57c900508110209de388f2@mail.gmail.com \
--to=coywolf@gmail.com \
--cc=akpm@osdl.org \
--cc=coywolf@lovecn.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.