From: "Jörn Engel" <joern@logfs.org>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Page scan keeps touching kernel text pages
Date: Sun, 24 Feb 2008 15:47:11 +0100 [thread overview]
Message-ID: <20080224144710.GD31293@lazybastard.org> (raw)
While tracking down some unrelated bug I noticed that shrink_page_list()
keeps testing very low page numbers (aka kernel text) until deciding
that the page lacks a mapping and cannot get freed. Looks like a waste
of cpu and cachelines to me.
Is there a better reason for this behaviour than lack of a patch?
JA?rn
--
Joern's library part 11:
http://www.unicom.com/pw/reply-to-harmful.html
--
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 reply other threads:[~2008-02-24 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 14:47 Jörn Engel [this message]
2008-02-25 15:07 ` Page scan keeps touching kernel text pages 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
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=20080224144710.GD31293@lazybastard.org \
--to=joern@logfs.org \
--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).