public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@digeo.com>,
	haveblue@us.ibm.com
Subject: Re: Overhead of highpte
Date: Wed, 2 Jul 2003 17:02:59 -0700	[thread overview]
Message-ID: <20030703000259.GL26348@holomorphy.com> (raw)
In-Reply-To: <20030702231502.GJ26348@holomorphy.com>

On Wed, Jul 02, 2003 at 03:53:24PM -0700, Martin J. Bligh wrote:
>> Some people were saying they couldn't see an overhead with highpte.
>> Seems pretty obvious to me still. It should help *more* on the NUMA
>> box, as PTEs become node-local.
>> The kmap_atomic is, of course, perfectly understandable. The increase
>> in the rmap functions is a bit of a mystery to me.

On Wed, Jul 02, 2003 at 04:15:02PM -0700, William Lee Irwin III wrote:
> The rmap functions perform kmap_atomic() internally while traversing
> pte_chains and so will take various additional TLB misses and incur
> various bits of computational expense with i386's kmap_atomic() semantics.
> The observations I made were in combination with both highpmd and an as
> of yet unmerged full 3-level pagetable cacheing patch.

Actually they were made with something approaching 0.5MB of diff vs.
the core VM and i386 arch code, so it isn't in the least bit remotely
likely to resemble any results on mainline.

Now, OTOH, my test was done on the same tree with different .config
settings, so it wasn't completely useless.


-- wli

  reply	other threads:[~2003-07-02 23:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02 22:53 Overhead of highpte Martin J. Bligh
2003-07-02 23:15 ` William Lee Irwin III
2003-07-03  0:02   ` William Lee Irwin III [this message]
2003-07-04  2:34 ` Dave Hansen
2003-07-04  2:46   ` Martin J. Bligh
2003-07-04  2:54     ` Dave Hansen
2003-07-04  3:53     ` Overhead of highpte (or not :) Dave Hansen

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=20030703000259.GL26348@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=akpm@digeo.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.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