From: Arun Sharma <arun.sharma@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Long Format VHPT patches
Date: Wed, 25 Aug 2004 20:17:32 +0000 [thread overview]
Message-ID: <412CF3DC.6010604@intel.com> (raw)
In-Reply-To: <20040825023439.GA15782@cse.unsw.EDU.AU>
On 8/25/2004 10:01 AM, Jesse Barnes wrote:
> On Tuesday, August 24, 2004 7:34 pm, Ian Wienand wrote:
>> 11-lf-VHPT-kconfig.patch
>
> Given your conclusions in the paper, would it make sense to unconditionally
> switch to long format VHPT? It would simplify things a little and maybe
> avoid some trouble in the future.
>
When the super page optimizations are implemented, long format might be a more attractive option. Without it, the increased cache footprint of the long format pte is not compensated by the benefits on the workloads we tried.
-Arun
next prev parent reply other threads:[~2004-08-25 20:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 2:34 Long Format VHPT patches Ian Wienand
2004-08-25 17:01 ` Jesse Barnes
2004-08-25 17:12 ` Chen, Kenneth W
2004-08-25 20:17 ` Arun Sharma [this message]
2004-08-25 22:46 ` Peter Chubb
2004-08-26 20:19 ` Christoph Lameter
2004-08-26 21:20 ` Peter Chubb
2004-08-27 17:15 ` Arun Sharma
2004-08-31 5:53 ` Ian Wienand
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=412CF3DC.6010604@intel.com \
--to=arun.sharma@intel.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox