From: Mike Kravetz <mike.kravetz@oracle.com>
To: Hugh Dickins <hughd@google.com>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [LSF/MM ATTEND] Huge Page Futures
Date: Thu, 28 Jan 2016 11:06:54 -0800 [thread overview]
Message-ID: <56AA66CE.8080000@oracle.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1601280022040.4201@eggly.anvils>
On 01/28/2016 12:49 AM, Hugh Dickins wrote:
> On Wed, 27 Jan 2016, Mike Kravetz wrote:
>> On 01/25/2016 05:50 AM, Mike Kravetz wrote:
>>> On 01/25/2016 03:01 AM, Kirill A. Shutemov wrote:
>>>> On Sun, Jan 24, 2016 at 05:57:12PM -0800, Mike Kravetz wrote:
>>>>> - Adding shared page table (PMD) support to DAX much like that which exists
>>>>> for hugetlbfs
>>>>
>>>> Shared page tables for hugetlbfs is rather ugly hack.
>>>>
>>>> Do you have any thoughts how it's going to be implemented? It would be
>>>> nice to have some design overview or better proof-of-concept patch before
>>>> the summit to be able analyze implications for the kernel.
>>>>
>>>
>>> Good to know the hugetlbfs implementation is considered a hack. I just
>>> started looking at this, and was going to use hugetlbfs as a starting
>>> point. I'll reconsider that decision.
>>
>> Kirill, can you (or others) explain your reasons for saying the hugetlbfs
>> implementation is an ugly hack? I do not have enough history/experience
>> with this to say what is most offensive. I would be happy to start by
>> cleaning up issues with the current implementation.
>
> I disagree that the hugetlbfs shared pagetables are an ugly hack.
> What they are is a dark backwater that very few people are aware of,
> which we therefore can very easily break or be broken by.
>
> I have regretted bringing them into mm for that reason, and have
> thought that they're next in line for the axe, after those non-linear
> vmas which Kirill dispatched without tears last year. But if you're
> intent on making more use of them, exposing them to the light of day
> is a fair alternative to consider.
It is interesting to note that at least one DB vendor (my employer) is
very aware of hugetlbfs shared pagetables, and takes advantage of them
in their DB architecture. Their primary concern is the memory savings
that sharing provides. I agree with you that very few people know
about them. I didn't know they existed until informed by the DB team
and I looked at the code.
--
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>
next prev parent reply other threads:[~2016-01-28 19:07 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 [this message]
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=56AA66CE.8080000@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=hughd@google.com \
--cc=kirill@shutemov.name \
--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).