From: "Jörn Engel" <joern@logfs.org>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: "Andy Whitcroft" <apw@shadowen.org>,
"Jörn Engel" <joern@logfs.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Page scan keeps touching kernel text pages
Date: Mon, 25 Feb 2008 19:53:20 +0100 [thread overview]
Message-ID: <20080225185319.GA14699@lazybastard.org> (raw)
In-Reply-To: <1203961702.6662.35.camel@nimitz.home.sr71.net>
On Mon, 25 February 2008 09:48:22 -0800, Dave Hansen wrote:
> On Mon, 2008-02-25 at 15:07 +0000, Andy Whitcroft wrote:
> > shrink_page_list() would be expected to be passed pages pulled from
> > the active or inactive lists via isolate_lru_pages()? I would not have
> > expected to find the kernel text on the LRU and therefore not expect to
> > see it passed to shrink_page_list()?
>
> It may have been kernel text at one time, but what about __init
> functions? Don't we free that section back to the normal allocator
> after init time? Those can end up on the LRU.
Pages below 0x2ba should be non-init in my test kernel:
c02ba000 T __init_begin
...
c02d5000 B __init_end
scanning zone DMA
page 3fa 3 00000000 628
page 2bf 2 00000000 628
page 97 3 00000000 628
page 98 2 00000000 628
So __init explains one page of this minimal sample, but not the other
three.
JA?rn
--
Never argue with idiots - first they drag you down to their level,
then they beat you with experience.
-- unknown
--
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:[~2008-02-25 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 14:47 Page scan keeps touching kernel text pages Jörn Engel
2008-02-25 15:07 ` Andy Whitcroft
2008-02-25 15:15 ` Jörn Engel
2008-02-25 17:35 ` Jörn Engel
2008-02-25 17:48 ` Dave Hansen
2008-02-25 18:53 ` Jörn Engel [this message]
2008-02-25 19:21 ` Andy Whitcroft
2008-02-25 19:46 ` Dave McCracken
2008-02-25 20:38 ` Jörn Engel
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=20080225185319.GA14699@lazybastard.org \
--to=joern@logfs.org \
--cc=apw@shadowen.org \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).