public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Rik van Riel <riel@imladris.surriel.com>,
	Andrew Morton <akpm@digeo.com>,
	"Martin J. Bligh" <mbligh@aracnet.com>,
	linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net,
	dmccr@us.ibm.com
Subject: Re: [Lse-tech] Re: Performance of partial object-based rmap
Date: Fri, 21 Feb 2003 11:15:38 -0800	[thread overview]
Message-ID: <20030221191538.GD10401@holomorphy.com> (raw)
In-Reply-To: <20030221100010.GB10401@holomorphy.com>

On Fri, Feb 21, 2003 at 02:00:10AM -0800, William Lee Irwin III wrote:
> nr_page_table_pages                  689
> which amounts to 2756KB RAM used for PTE's, demonstrating large

Pagetables are also grossly fragmented. From the same sample:

nr_reverse_maps                   156027

To preempt the FAQ, this is the number of reverse mappings performed,
where one is done for every instantiated non-swap PTE.

$ echo $(( (689*1024)/156027.0 ))
4.5218840328917427

So the space flushed down the toilet there is also relatively large.
Approximately 4.5 PTE's per pagetable page, or a utilization of:

$ echo $(( (100*689)/156027.0 ))
0.44159023758708427

percent.

-- wli

  reply	other threads:[~2003-02-21 19:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20  4:25 Performance of partial object-based rmap Martin J. Bligh
2003-02-20  4:47 ` William Lee Irwin III
2003-02-20  5:14   ` Martin J. Bligh
2003-02-20  5:16     ` [Lse-tech] " William Lee Irwin III
2003-02-20  5:27       ` Martin J. Bligh
2003-02-21  1:44 ` Martin J. Bligh
2003-02-21  3:08   ` Andrew Morton
2003-02-21  3:25     ` Rik van Riel
2003-02-21  3:47       ` Andrew Morton
2003-02-21  4:25         ` Rik van Riel
2003-02-21 10:00           ` William Lee Irwin III
2003-02-21 19:15             ` William Lee Irwin III [this message]
2003-02-21 19:27               ` [Lse-tech] " William Lee Irwin III
2003-02-21  3:32     ` Martin J. Bligh

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=20030221191538.GD10401@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=akpm@digeo.com \
    --cc=dmccr@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=mbligh@aracnet.com \
    --cc=riel@imladris.surriel.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