From: Dave Hansen <haveblue@us.ibm.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@digeo.com>,
William Lee Irwin III <wli@holomorphy.com>
Subject: Re: Overhead of highpte (or not :)
Date: 03 Jul 2003 20:53:00 -0700 [thread overview]
Message-ID: <1057290780.18849.37.camel@nighthawk> (raw)
In-Reply-To: <68160000.1057286782@[10.10.2.4]>
After fixing my gcc stupidity
Elapsed: User: System: CPU:
high pte: 49.962s 578.888s 99.048s 1356.2%
lowpte: 49.630s 576.242s 90.158s 1342.0%
ukva: 50.122s 577.164s 88.958s 1328.4%
The increase in elapsed is probably within tolerances. The system time
isn't :) The decrease in system time compared to lowpte comes because
the PTE pages are allocated in highmem, and are node-local.
Differential profiles are up in a bit.
--
Dave Hansen
haveblue@us.ibm.com
prev parent reply other threads:[~2003-07-04 3:39 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
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 ` Dave Hansen [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=1057290780.18849.37.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=wli@holomorphy.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 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.