From: Nick Piggin <nickpiggin@yahoo.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] pte prefetching
Date: Fri, 25 Mar 2005 05:22:02 +0000 [thread overview]
Message-ID: <42439FFA.7040300@yahoo.com.au> (raw)
In-Reply-To: <424269B9.9020306@yahoo.com.au>
David Mosberger wrote:
>>>>>>On Thu, 24 Mar 2005 18:18:17 +1100, Nick Piggin <nickpiggin@yahoo.com.au> said:
>
>
> Nick> After applying the recent freepgt patchset from Hugh (on
> Nick> lkml), the time to fork+exit a process mapping 64GB of address
> Nick> (32MB of page tables) is 0.471s. With the prefetch patch, this
> Nick> drops to 0.357s.
>
Sorry, above numbers were wrong:
0.118s versus 0.089s. Improvement ratio is the same, I just used the
wrong divisor.
> Looks like a nice improvement to me.
>
> Does prefetching 1 line ahead give the best results? That's only
> 128/8\x16 PTEs. Assuming a 200 cycle latency, this would allow
> for only 12.5 cycles/iteration. Especially for large (NUMA) machines,
> prefetching further out might help more.
>
Hmm... yeah it may do. Although I don't think that changes your cycles
/ iteration ratio, does it? Just allows for for a little bit more
variation.
I just retested, and prefetching 2 lines ahead gives virtually the same
performance.
But actually, my tests are set up so each pte page has only a single
'present' pte (I did it that way to speed up initial faulting time).
So the loop will almost always get stopped by the pte_none tests. So
perhaps that is able to complete in close to or less than 12 cycles.
Nick
prev parent reply other threads:[~2005-03-25 5:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 7:18 [PATCH] pte prefetching Nick Piggin
2005-03-24 20:15 ` David Mosberger
2005-03-25 5:22 ` Nick Piggin [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=42439FFA.7040300@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.