From: William Lee Irwin III <wli@holomorphy.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: linux-mm@kvack.org
Subject: Re: meminfo documentation
Date: Tue, 8 Apr 2003 18:19:11 -0700 [thread overview]
Message-ID: <20030409011911.GA21761@holomorphy.com> (raw)
In-Reply-To: <3E936E2A.4080400@us.ibm.com>
On Tue, Apr 08, 2003 at 05:49:46PM -0700, Dave Hansen wrote:
> ReverseMaps: number of rmap pte chains
It's not about the number of pte_chains. There are 3 ways to think of it:
(1) number of reverse mappings performed.
(2) total number of pte's in pte_chains
(3) total faulted-in memory-backed virtualspace
pte_chain objects may partially utilize slabs, and a given chain of
pte_chain objects may be partially utilized within a given chain,
as there are 7 pointers or so in an object, and you have to fill a
chain with a precise number of pte's to fully utilize the objects.
So, there are two levels at which internal fragmentation can happen.
This measures the one _not_ detectable from /proc/slabinfo, which is
the internal fragmentation at the pte-filling-object-level.
The number these days is not particularly useful for the measurement
of internal fragmentation due to the PG_direct changes, but could be
fixed up to measure it again. This stat is slated to be removed soon
because it's measurably expensive to collect (which is good; any stat
with that kind of performance impact should either die or be config'd).
-- wli
--
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:"aart@kvack.org">aart@kvack.org</a>
prev parent reply other threads:[~2003-04-09 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 0:49 Dave Hansen
2003-04-09 1:19 ` William Lee Irwin III [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=20030409011911.GA21761@holomorphy.com \
--to=wli@holomorphy.com \
--cc=haveblue@us.ibm.com \
--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