From: "Marc-André Lureau" <marcandre.lureau@gmail.com>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: linux-mm@kvack.org, open list <linux-kernel@vger.kernel.org>,
Hugh Dickins <hughd@google.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Michal Hocko <mhocko@kernel.org>,
David Herrmann <dh.herrmann@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC PATCH 0/3] restructure memfd code
Date: Mon, 20 Nov 2017 11:28:09 +0100 [thread overview]
Message-ID: <CAJ+F1CKsehGaan8ZgSNEBQ6sveyMVYH5Wr4ggys-czpmbV8Qvg@mail.gmail.com> (raw)
In-Reply-To: <20171109014109.21077-1-mike.kravetz@oracle.com>
Hi
On Thu, Nov 9, 2017 at 2:41 AM, Mike Kravetz <mike.kravetz@oracle.com> wrote:
> With the addition of memfd hugetlbfs support, we now have the situation
> where memfd depends on TMPFS -or- HUGETLBFS. Previously, memfd was only
> supported on tmpfs, so it made sense that the code resides in shmem.c.
>
> This patch series moves the memfd code to separate files (memfd.c and
> memfd.h). It creates a new config option MEMFD_CREATE that is defined
> if either TMPFS or HUGETLBFS is defined.
That looks good to me
>
> In the current code, memfd is only functional if TMPFS is defined. If
> HUGETLFS is defined and TMPFS is not defined, then memfd functionality
> will not be available for hugetlbfs. This does not cause BUGs, just a
> potential lack of desired functionality.
>
Indeed
> Another way to approach this issue would be to simply make HUGETLBFS
> depend on TMPFS.
>
> This patch series is built on top of the Marc-André Lureau v3 series
> "memfd: add sealing to hugetlb-backed memory":
> http://lkml.kernel.org/r/20171107122800.25517-1-marcandre.lureau@redhat.com
Are you waiting for this series to be merged before resending as non-rfc?
>
> Mike Kravetz (3):
> mm: hugetlbfs: move HUGETLBFS_I outside #ifdef CONFIG_HUGETLBFS
> mm: memfd: split out memfd for use by multiple filesystems
> mm: memfd: remove memfd code from shmem files and use new memfd files
>
> fs/Kconfig | 3 +
> fs/fcntl.c | 2 +-
> include/linux/hugetlb.h | 27 ++--
> include/linux/memfd.h | 16 +++
> include/linux/shmem_fs.h | 13 --
> mm/Makefile | 1 +
> mm/memfd.c | 341 +++++++++++++++++++++++++++++++++++++++++++++++
> mm/shmem.c | 323 --------------------------------------------
> 8 files changed, 378 insertions(+), 348 deletions(-)
> create mode 100644 include/linux/memfd.h
> create mode 100644 mm/memfd.c
>
> --
> 2.13.6
>
Thanks
--
Marc-André Lureau
--
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:[~2017-11-20 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 1:41 Mike Kravetz
2017-11-09 1:41 ` [RFC PATCH 1/3] mm: hugetlbfs: move HUGETLBFS_I outside #ifdef CONFIG_HUGETLBFS Mike Kravetz
2017-11-09 1:41 ` [RFC PATCH 2/3] mm: memfd: split out memfd for use by multiple filesystems Mike Kravetz
2017-11-09 1:41 ` [RFC PATCH 3/3] mm: memfd: remove memfd code from shmem files and use new memfd files Mike Kravetz
2017-11-20 10:28 ` Marc-André Lureau [this message]
2017-11-20 22:55 ` [RFC PATCH 0/3] restructure memfd code Mike Kravetz
2017-11-21 16:32 ` Khalid Aziz
2017-11-22 0:40 ` Mike Kravetz
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=CAJ+F1CKsehGaan8ZgSNEBQ6sveyMVYH5Wr4ggys-czpmbV8Qvg@mail.gmail.com \
--to=marcandre.lureau@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dh.herrmann@gmail.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.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