From: Jes Sorensen <jes@sgi.com>
To: Paul Cameron Davies <pauld@cse.unsw.EDU.AU>
Cc: linux-mm@kvack.org
Subject: Re: [Patch 0/17] PTI: Explation of Clean Page Table Interface
Date: 30 May 2006 03:59:43 -0400 [thread overview]
Message-ID: <yq0irnot028.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0605301334520.10816@weill.orchestra.cse.unsw.EDU.AU>
>>>>> "Paul" == Paul Cameron Davies <pauld@cse.unsw.EDU.AU> writes:
Paul> This patch series provides the architectural independent
Paul> interface. It has been tested and benchmarked for IA64 using
Paul> lmbench. It also passes all relevant tests in the Linux Test
Paul> Project (LTP) on IA64. This patch should 5~also compile and run
Paul> for i386. To run on other architectures add CONFIG_DEFAULT_PT
Paul> to the architectures config. Turn off HugeTLB.
Paul> Summary of performance degradation using lmbench on IA64: ~3.5%
Paul> deterioration in fork latency on IA64. ~1.0% deterioration in
Paul> mmap latency on IA64
Paul,
Let me just get it right as I am not sure I am reading it correctly.
Are you saying that this patch causes a 3.5% fork performance
degradation on ia64 or are you saying it is improving 3.5%?
Thanks,
Jes
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-05-30 7:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 7:01 Paul Cameron Davies
2006-05-30 7:59 ` Jes Sorensen [this message]
2006-05-30 8:29 ` Peter Chubb
2006-05-30 8:32 ` Paul Cameron Davies
2006-05-30 8:42 ` Jes Sorensen
2006-05-31 1:17 ` Paul Cameron Davies
2006-05-31 2:25 ` Nick Piggin
2006-06-01 3:21 ` Paul Cameron Davies
2006-06-02 3:10 ` Nick Piggin
2006-05-31 3:24 ` Hugh Dickins
2006-06-01 6:35 ` Paul Cameron Davies
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=yq0irnot028.fsf@jaguar.mkp.net \
--to=jes@sgi.com \
--cc=linux-mm@kvack.org \
--cc=pauld@cse.unsw.EDU.AU \
/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