From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: Long Format VHPT patches
Date: Wed, 25 Aug 2004 17:12:37 +0000 [thread overview]
Message-ID: <200408251712.i7PHCbY31390@unix-os.sc.intel.com> (raw)
In-Reply-To: <20040825023439.GA15782@cse.unsw.EDU.AU>
On Tuesday, August 24, 2004 7:34 pm, Ian Wienand wrote:
> 11-lf-VHPT-kconfig.patch
Jesse Barnes wrote on Wednesday, August 25, 2004 10:02 AM
> 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.
The benchmarks done in the paper are very limited in my opinion, I don't
think it covers the whole spectrum of usage model. Our internal evaluation
shows otherwise (i.e., LVHPT are slower in some industry benchmarks). My
point is switching unconditionally so early is probably not a wise idea.
- Ken
next prev parent reply other threads:[~2004-08-25 17:12 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 [this message]
2004-08-25 20:17 ` Arun Sharma
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=200408251712.i7PHCbY31390@unix-os.sc.intel.com \
--to=kenneth.w.chen@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