From: "Francis Moreau" <francis.moro@gmail.com>
To: "Hugh Dickins" <hugh@veritas.com>
Cc: "Rik van Riel" <riel@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: question about do_anonymous_page()
Date: Fri, 8 Aug 2008 11:22:29 +0200 [thread overview]
Message-ID: <38b2ab8a0808080222h6d810b7fheefaf3633e65ea8a@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0808080938001.15941@blonde.site>
On Fri, Aug 8, 2008 at 10:51 AM, Hugh Dickins <hugh@veritas.com> wrote:
>> Is it simply because lru_add_active() doesn't exist ?
>
> Yes.
>
great at least one thing I understood from the kernel mm internals ;)
> It just happens that whoever (Rik?) originally named that function was
> primarily thinking of the page cache at the time; or perhaps wasn't
> thinking of the file page cache at all, just regarding all the pages
> we put on that list as cached in some sense.
>
I think it might be the second reason since the page is not directly
added to the LRU
but to a pagevec structure since the term 'cache'. But IMHO if so,
it's just confusing and
lru_cache_add_active() shouldn't contain implemantation details in its name.
> You're right that it's a little anomalous, but nothing to worry about.
well, it's just that I got confusing when reading the code for the
first time. I really have hard
time to understand it...
> I get more bothered by page_cache_get(), which is and always(?) has
> been the same thing as get_page(): sometimes we use one, sometimes
> the other, and often we use page_cache_get() on anonymous pages.
>
Yes and this is what confused me: lru_cache_add_active() does call
page_cache_get()
for anymous pages, hence my question.
Thanks !
--
Francis
prev parent reply other threads:[~2008-08-08 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 8:01 Francis Moreau
2008-08-08 8:23 ` Francis Moreau
2008-08-08 8:51 ` Hugh Dickins
2008-08-08 9:22 ` Francis Moreau [this message]
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=38b2ab8a0808080222h6d810b7fheefaf3633e65ea8a@mail.gmail.com \
--to=francis.moro@gmail.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
/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®