linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Kravetz <mike.kravetz@oracle.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: [LSF/MM ATTEND] Huge Page Futures
Date: Sun, 24 Jan 2016 17:57:12 -0800	[thread overview]
Message-ID: <56A580F8.4060301@oracle.com> (raw)

In a search of the archives, it appears huge page support in one form or
another has been a discussion topic in almost every LSF/MM gathering. Based
on patches submitted this past year, huge pages is still an area of active
development.  And, it appears this level of activity will  continue in the
coming year.

I propose a "Huge Page Futures" session to discuss large works in progress
as well as work people are considering for 2016.  Areas of discussion would
minimally include:

- Krill Shutemov's THP new refcounting code and the push for huge page
  support in the page cache.

- Matt Wilcox's huge page support in DAX enabled filesystems, but perhaps
  more interesting is the desire for supporting PUD pages.  This seems to
  beg the question of supporting transparent PUD pages elsewhere.

- Other suggestions?

My interest in attending also revolves around huge pages.  This past year
I have added functionality to hugetlbfs.  hugetlbfs is not dead, and is
very much in use by some DB implementations.  Proposed future work I will
be attempting includes:
- Adding userfaultfd support to hugetlbfs
- Adding shared page table (PMD) support to DAX much like that which exists
  for hugetlbfs

-- 
Mike Kravetz

--
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:[~2016-01-25  1:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25  1:57 Mike Kravetz [this message]
2016-01-25 11:01 ` [LSF/MM ATTEND] Huge Page Futures Kirill A. Shutemov
2016-01-25 13:50   ` Mike Kravetz
2016-01-27 17:49     ` Mike Kravetz
2016-01-28  8:49       ` Hugh Dickins
2016-01-28 19:06         ` Mike Kravetz
2016-01-28  9:21       ` [Lsf-pc] " Mel Gorman
2016-01-28 18:24         ` Mike Kravetz
2016-01-28 15:05 ` Aneesh Kumar K.V
2016-01-28 19:28   ` Mike Kravetz
2016-01-29 10:01     ` Kirill A. Shutemov

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=56A580F8.4060301@oracle.com \
    --to=mike.kravetz@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).