From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Ning Qu <quning@google.com>, Andi Kleen <ak@linux.intel.com>,
Dave Hansen <dave.hansen@intel.com>
Subject: [LSF/MM TOPIC] THP page cache
Date: Thu, 20 Mar 2014 21:43:55 +0200 [thread overview]
Message-ID: <20140320194355.GA4896@node.dhcp.inet.fi> (raw)
Hi,
I believe we will get to transparent huge pages at summit anyway. Below is data
points on file-backed transparent huge pages.
The code I have by the time is in my repo[1], see branches
thp/pc/v7/p1-base and thp/pc/v7/p2-mmap. Ning Qu works on rebasing
shmem/tmpfs support on top of this.
Workloads known to benefit from THP for page cache:
- MongoDB: mongoperf on ramfs shows increase number of iops by 1.9x for r/o and
1.7x for r/w;
- Google search/indexing benchmark shows +3% (in addition to +5% from AnonTHP),
on pair with hugetlbfs;
- IOZone shows improvement up to 2.5x on ramfs;
Should help also with:
- Reducing ITLB pressure:
+ x86-64 binaries is ready to be mapped with 2M pages: binutils creates
binaries with required file offset and virtual address alignment, no
changes required;
+ reported 11% performance increase of RDBMS by putting code to hugetlbfs;
+ MySQL spends 2.5% of cycles in page table walk due ITLB misses[2];
- HPC workloads on many-cores systems (like Xeon Phi): large code and data,
small TLB, limited memory bandwidth.
[1] git://git.kernel.org/pub/scm/linux/kernel/git/kas/linux.git
[2] http://research.cs.wisc.edu/multifacet/papers/isca13_direct_segment.pdf
--
Kirill A. Shutemov
--
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:[~2014-03-20 19:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140320194355.GA4896@node.dhcp.inet.fi \
--to=kirill@shutemov.name \
--cc=ak@linux.intel.com \
--cc=dave.hansen@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=quning@google.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 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.