linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Paul Cameron Davies <pauld@cse.unsw.EDU.AU>
To: Hugh Dickins <hugh@veritas.com>
Cc: Jes Sorensen <jes@sgi.com>, linux-mm@kvack.org
Subject: Re: [Patch 0/17] PTI: Explation of Clean Page Table Interface
Date: Thu, 1 Jun 2006 16:35:49 +1000 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.62.0606011632400.25647@weill.orchestra.cse.unsw.EDU.AU> (raw)
In-Reply-To: <Pine.LNX.4.64.0605310412530.5488@blonde.wat.veritas.com>

On Wed, 31 May 2006, Hugh Dickins wrote:

> On Wed, 31 May 2006, Paul Cameron Davies wrote:
>>
>> What level of degradation in peformance in acceptable (if any)?
>
> None.  What is the point in slowing it down, even on the architecture
> you are targeting, while making it all more complicated, moving
> significant code around from the .cs where we expect it into .hs?

The PTI (page table interface) will give a small performance hit,
but we believe that when the MLPT is replaced with some other
implementation, for example the GPT (guarded page table), that
a better overall performance will be achieved.

In particular, this will be true for apps with large memory
requirements on 64-bit architectures.

We have access to some papers discussing the problems that will
occur when large memory spaces are more commonly used, but
unfortunately there is no URL to directly access them.
We do have a paper that discusses variable radix page tables
(which is a GPT by another name) found here:

www.ertos.nicta.com.au/publications/papers/Szmajda_Heiser_03.pdf

As a pragmatist, I agree that it is of real concern that the
page table interface would slow down commonly-used architectures.
However, current performance depends on the kernel being
organised to suit the MLPT implementation. That is likely to
prevent efficient use of large memory spaces in the future.

Directly accessing the VM data structure works well at the moment.
In the near future, it is likely that many systems will want to
work with large amounts of memory, and the optimisations that
work well now will not work well with those systems.

> And please, next time, make sure the patches can actually be applied:
> your mailer (pine) messed with the whitespace - quell-flowed-text is,
> I think, the feature you need to add, but mail yourself the patches
> first as a test to make sure they can be applied by recipients.
Sorry, thanks for the tip.

Cheers

Paul

--
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>

      reply	other threads:[~2006-06-01  6:35 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
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 [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=Pine.LNX.4.62.0606011632400.25647@weill.orchestra.cse.unsw.EDU.AU \
    --to=pauld@cse.unsw.edu.au \
    --cc=hugh@veritas.com \
    --cc=jes@sgi.com \
    --cc=linux-mm@kvack.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