From: Ning Qu <quning@gmail.com>
To: Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Hugh Dickins <hughd@google.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Wu Fengguang <fengguang.wu@intel.com>, Jan Kara <jack@suse.cz>,
Mel Gorman <mgorman@suse.de>,
linux-mm@kvack.org, Andi Kleen <ak@linux.intel.com>,
Matthew Wilcox <willy@linux.intel.com>,
Hillf Danton <dhillf@gmail.com>, Dave Hansen <dave@sr71.net>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Ning Qu <quning@google.com>
Subject: [PATCH 00/12] Transparent huge page cache support on tmpfs
Date: Mon, 14 Oct 2013 17:11:12 -0700 [thread overview]
Message-ID: <20131015001112.GA3432@hippobay.mtv.corp.google.com> (raw)
Transparent huge page support on tmpfs.
Please review.
Intro
-----
The goal of the project is to enable transparent huge page support on
tmpfs.
The whole patchset is based on Kirill's latest patchset about Transparent
huge page cache v6. As the link below:
https://lkml.org/lkml/2013/9/23/230
To further proof that the proposed changes are functional we try enable
this feature for a more complex file system tmpfs besides ramfs. tmpfs
comes with swap support which make is more usable.
Design overview
---------------
We share the exact same design from Kirill's work. However, due to the
complexity of tmpfs, we do a lot of refactoring on the implementation.
Known problem
---------------
We do try to make it work with swapping, but currently there are still
some problem with it. I am debbugging it.
However, it would be great to have more opinions about the design in
the current patchset and where we should be heading to.
Ning Qu (12):
mm, thp, tmpfs: add function to alloc huge page for tmpfs
mm, thp, tmpfs: support to add huge page into page cache for tmpfs
mm, thp, tmpfs: handle huge page cases in shmem_getpage_gfp
mm, thp, tmpfs: split huge page when moving from page cache to swap
mm, thp, tmpfs: request huge page in shm_fault when needed
mm, thp, tmpfs: initial support for huge page in write_begin/write_end
in tmpfs
mm, thp, tmpfs: handle huge page in shmem_undo_range for truncate
mm, thp, tmpfs: huge page support in do_shmem_file_read
mm, thp, tmpfs: huge page support in shmem_fallocate
mm, thp, tmpfs: only alloc small pages in shmem_file_splice_read
mm, thp, tmpfs: enable thp page cache in tmpfs
mm, thp, tmpfs: misc fixes for thp tmpfs
mm/Kconfig | 4 +-
mm/huge_memory.c | 27 +++
mm/shmem.c | 511 +++++++++++++++++++++++++++++++++++++++++++++++--------
3 files changed, 467 insertions(+), 75 deletions(-)
--
1.8.4
--
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:[~2013-10-15 0:11 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=20131015001112.GA3432@hippobay.mtv.corp.google.com \
--to=quning@gmail.com \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=dave@sr71.net \
--cc=dhillf@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=quning@google.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox