From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: 'Andrew Morton' <akpm@osdl.org>
Cc: 'Hugh Dickins' <hugh@veritas.com>,
'Dave McCracken' <dmccr@us.ibm.com>,
linux-mm@kvack.org
Subject: RE: [patch] shared page table for hugetlb page - v2
Date: Wed, 20 Sep 2006 18:35:52 -0700 [thread overview]
Message-ID: <000001c6dd1e$4671ac50$1ee8030a@amr.corp.intel.com> (raw)
In-Reply-To: <20060920180825.1c1ad6ae.akpm@osdl.org>
Andrew Morton wrote on Wednesday, September 20, 2006 6:08 PM
> On Wed, 20 Sep 2006 17:57:33 -0700
> "Chen, Kenneth W" <kenneth.w.chen@intel.com> wrote:
>
> > Following up with the work on shared page table, here is a re-post of
> > shared page table for hugetlb memory.
>
> Is that actually useful? With one single pagetable page controlling,
> say, 4GB of hugepage memory, I'm surprised that there's much point in
> trying to optimise it.
Yes, there is when large number of processes using one large shared memory
segment. The optimization is not really targeted to save memory in this
case, instead, the goal of using shared PT on hugetlb is to allow faster
TLB refill and less cache pollution upon TLB miss.
Since pte entries are shared among hundreds of processes, the cache
consumption used by all the page table is a lot smaller and in return, we
got much higher cache hit rate for user space application. I have performance
counter data to back that claim if people want to see the detail. The other
effect is also that cache hit rate with hardware page walker will be higher
too and this helps to reduce tlb miss latency.
In Dave's implementation for sharing PT on normal page, the performance
gain is predominantly come from reducing memory overhead in managing PTE.
I think cache miss rate and tlb miss latency is of secondary consideration
in that scenario, though it should help there as well.
- Ken
--
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-09-21 1:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 0:57 Chen, Kenneth W
2006-09-21 1:08 ` Andrew Morton
2006-09-21 1:35 ` Chen, Kenneth W [this message]
2006-09-22 21:21 ` Andrew Morton
2006-09-22 22:53 ` Chen, Kenneth W
2006-09-26 20:03 ` Hugh Dickins
2006-09-27 8:34 ` Chen, Kenneth W
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='000001c6dd1e$4671ac50$1ee8030a@amr.corp.intel.com' \
--to=kenneth.w.chen@intel.com \
--cc=akpm@osdl.org \
--cc=dmccr@us.ibm.com \
--cc=hugh@veritas.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