linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Kravetz <mike.kravetz@oracle.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [LSF/MM ATTEND] Huge Page Futures
Date: Thu, 28 Jan 2016 11:28:33 -0800	[thread overview]
Message-ID: <56AA6BE1.2050809@oracle.com> (raw)
In-Reply-To: <87bn85ycbh.fsf@linux.vnet.ibm.com>

On 01/28/2016 07:05 AM, Aneesh Kumar K.V wrote:
> Mike Kravetz <mike.kravetz@oracle.com> writes:
> 
>> 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.
> 
> I am also interested in this discussion. We had some nice challenge
> w.r.t to powerpc implementation of THP.
> 
>>
>> - 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.
>>
> 
> I am also looking at switching powerpc hugetlbfs to GENERAL_HUGETLB. To
> support 16GB pages I would need hugepage at PUD/PGD. Can you elaborate
> why supporting huge PUD page is a challenge ?

For hugetlbfs it should not be an issue.  However, page fault handling for
hugetlbfs is already a special case today.  Is that what you were asking?

Matt's work adds THP for PUD sized huge pages to DAX mappings.  The thought
that popped into my head is "Does it make sense to try and expand THP for
PUD sized pages elsewhere?".  Perhaps that is nonsense and a silly question
to ask.

-- 
Mike Kravetz

> 
> -aneesh
> 
> --
> 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>
> 

--
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-28 19:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25  1:57 [LSF/MM ATTEND] Huge Page Futures Mike Kravetz
2016-01-25 11:01 ` 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 [this message]
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=56AA6BE1.2050809@oracle.com \
    --to=mike.kravetz@oracle.com \
    --cc=aneesh.kumar@linux.vnet.ibm.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).