From: William Lee Irwin III <wli@holomorphy.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [RFC] i386: Remove page sized slabs for pgds and pmds
Date: Wed, 28 Mar 2007 13:50:55 -0700 [thread overview]
Message-ID: <20070328205055.GX8915@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703281309210.12985@schroedinger.engr.sgi.com>
On Wed, Mar 28, 2007 at 01:12:56PM -0700, Christoph Lameter wrote:
> The benefit of preconstructed pgds and pmds in the i386 arch code seem to
> be debatable. The performance measurements indicate that there may be a slight
> benefit but it seems to almost vanish in the noise ratio.
> Method used (i386 1G memory):
> 1. Boot kernel
> 2. make clean
> 3. time make all
Getting the relevant results without tremendous amounts of noise from
other kernel activity needs something like lmbench's fault and fork()
microbenchmarks. Also, /proc/profile and/or oprofile results would be
useful here to get useful notions of what's happening performancewise,
in particular oprofile with L2 cache miss performance counters.
The magnitude of the degradation in the specific operations can't
really be established without these sorts of affairs. We need to know
how large a fraction of the workload is attributable to the operations
in question. Profiling would already give something of a breakdown but
it's difficult to get the numbers to add up properly or to separate
fork() from faults, so the microbenchmarks focused on the particular
operations are needed. The profiles are still needed to understand how
the time shuffled around and to either confirm or invalidate notions
regarding cache behavior.
In any event, I already know the answers because I already did all this
a number of years ago: it's all dominated by PTE caching, which was
never merged, but I carried out-of-tree for several years, so of course
it's in the noise. PMD and PTE caching are only pertinent to fork()
anyway, so the vast majority of your workload is unaffected, and it's
even more "in the noise" due to that. I can't be arsed to care about it
anymore since i386 became a target-system-only architecture for me and
am sick of the flak coming at me for my pagetable caching code anyway.
Hence this patch.
-- wli
next prev parent reply other threads:[~2007-03-28 20:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 20:12 [RFC] i386: Remove page sized slabs for pgds and pmds Christoph Lameter
2007-03-28 20:45 ` Andrew Morton
2007-03-28 21:05 ` Christoph Lameter
2007-03-28 21:16 ` William Lee Irwin III
2007-03-28 21:20 ` Christoph Lameter
2007-03-28 22:37 ` William Lee Irwin III
2007-03-28 23:44 ` Christoph Lameter
2007-03-29 0:53 ` William Lee Irwin III
2007-03-29 1:09 ` Christoph Lameter
2007-03-29 1:17 ` Benjamin LaHaise
2007-03-28 20:50 ` William Lee Irwin III [this message]
2007-03-28 21:00 ` Christoph Lameter
2007-03-28 21:24 ` William Lee Irwin III
2007-03-28 21:38 ` Christoph Lameter
2007-03-28 22:01 ` William Lee Irwin III
2007-03-28 22:22 ` Christoph Lameter
2007-03-29 0:28 ` Alan Cox
2007-03-29 0:59 ` William Lee Irwin III
2007-03-28 22:26 ` Chris Wright
2007-03-28 22:33 ` William Lee Irwin III
2007-03-28 22:45 ` Chris Wright
2007-03-28 23:42 ` Zachary Amsden
2007-03-28 22:47 ` Chris Wright
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=20070328205055.GX8915@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.