public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "Luck, Tony" <tony.luck@intel.com>,
	Ian Wienand <ianw@gelato.unsw.edu.au>,
	linux-ia64@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: RE: [RFC 2/3] LVHPT - Setup LVHPT
Date: Tue, 02 May 2006 17:30:07 +0000	[thread overview]
Message-ID: <4t153d$t4bok@azsmga001.ch.intel.com> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F066076B6@scsmsx401.amr.corp.intel.com>
In-Reply-To: <20060502052557.8990.87273.sendpatchset@wagner.orchestra.cse.unsw.EDU.AU>

Luck, Tony wrote on Tuesday, May 02, 2006 8:03 AM
> Thanks for keeping this alive.  Previous measurements on long
> format VHPT were mostly close to neutral performance-wise with
> short format ... 

This is a fairly gentle comments :-)  Digging up my result of performance
evaluation on database workload, the regression is quite big at 2.8%.  I'm
not that happy at all :-(


> so this is still waiting for the killer-app in
> the form of another patch that actually uses features of the
> long format VHPT to do something that can't easily be done by
> the short format

Database workload can be the potential killer-app ....


> to give me an incentive to complicate the code
> by adding yet another CONFIG option.  In fact, I'd prefer to see
> a compelling use case for long format so that it would be clear
> that the right thing to do would be to just remove short format
> and replace it with long format, but I don't expect that things
> will ever be that simple :-(


Boot time option to the rescue!  I have a patch that does just like that.
Though first order of business is to make lvhpt to perform on large
workload. If I recall correctly, lvhpt introduces performance regression
on certain components of cpu2000.

- Ken

  parent reply	other threads:[~2006-05-02 17:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-02  5:25 [RFC 0/3] IA64 Long Format VHPT support Ian Wienand
2006-05-02  5:25 ` [RFC 1/3] LVHPT - Fault handler modifications Ian Wienand
2006-05-02  8:04   ` Keith Owens
2006-05-02 17:40   ` Chen, Kenneth W
2006-05-03  7:42     ` Ian Wienand
2006-05-02  5:25 ` [RFC 2/3] LVHPT - Setup LVHPT Ian Wienand
2006-05-02 15:03   ` Luck, Tony
2006-05-02 21:29     ` Ian Wienand
2006-05-02 17:30   ` Chen, Kenneth W [this message]
2006-05-03  7:49     ` Ian Wienand
2006-05-03  8:07       ` Christian Hildner
2006-05-02 21:33   ` Luck, Tony
2006-05-03 10:53   ` Ian Wienand
2006-05-03 11:15   ` Christian Hildner
2006-05-04 16:58   ` Luck, Tony
2006-05-02  5:26 ` [RFC 3/3] LVHPT - LVHPT MM support functions 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='4t153d$t4bok@azsmga001.ch.intel.com' \
    --to=kenneth.w.chen@intel.com \
    --cc=ianw@gelato.unsw.edu.au \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tony.luck@intel.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