From: Michal Hocko <mhocko@kernel.org>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org, Hugh Dickins <hughd@google.com>,
Andrea Arcangeli <aarcange@redhat.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC PATCH 0/1] Add hugetlbfs support to memfd_create()
Date: Tue, 8 Aug 2017 07:33:58 +0200 [thread overview]
Message-ID: <20170808053357.GA27790@dhcp22.suse.cz> (raw)
In-Reply-To: <1502149672-7759-1-git-send-email-mike.kravetz@oracle.com>
Hi,
I am one foot out of office and will be offline for two days so I
didn't get to review the patch yet but this information is an useful
information about the usecase that should be in the patch directly for
future reference.
On Mon 07-08-17 16:47:51, Mike Kravetz wrote:
> This patch came out of discussions in this e-mail thread [1].
>
> The Oracle JVM team is developing a new garbage collection model. This
> new model requires multiple mappings of the same anonymous memory. One
> straight forward way to accomplish this is with memfd_create. They can
> use the returned fd to create multiple mappings of the same memory.
>
> The JVM today has an option to use (static hugetlb) huge pages. If this
> option is specified, they would like to use the same garbage collection
> model requiring multiple mappings to the same memory. Using hugetlbfs,
> it is possible to explicitly mount a filesystem and specify file paths
> in order to get an fd that can be used for multiple mappings. However,
> this introduces additional system admin work and coordination.
>
> Ideally they would like to get a hugetlbfs fd without requiring explicit
> mounting of a filesystem. Today, mmap and shmget can make use of
> hugetlbfs without explicitly mounting a filesystem. The patch adds this
> functionality to hugetlbfs.
>
> A new flag MFD_HUGETLB is introduced to request a hugetlbfs file. Like
> other system calls where hugetlb can be requested, the huge page size
> can be encoded in the flags argument is the non-default huge page size
> is desired. hugetlbfs does not support sealing operations, therefore
> specifying MFD_ALLOW_SEALING with MFD_HUGETLB will result in EINVAL.
>
> Of course, the memfd_man page would need updating if this type of
> functionality moves forward.
>
> [1] https://lkml.org/lkml/2017/7/6/564
>
> Mike Kravetz (1):
> mm/shmem: add hugetlbfs support to memfd_create()
>
> include/uapi/linux/memfd.h | 24 ++++++++++++++++++++++++
> mm/shmem.c | 37 +++++++++++++++++++++++++++++++------
> 2 files changed, 55 insertions(+), 6 deletions(-)
>
> --
> 2.7.5
--
Michal Hocko
SUSE Labs
--
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>
prev parent reply other threads:[~2017-08-08 5:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 23:47 Mike Kravetz
2017-08-07 23:47 ` [RFC PATCH 1/1] mm/shmem: add " Mike Kravetz
2017-08-08 5:33 ` Michal Hocko [this message]
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=20170808053357.GA27790@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.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