[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230703224803.GF4378@monkey>
Date: Mon, 3 Jul 2023 15:48:03 -0700
From: Mike Kravetz <mike.kravetz@...cle.com>
To: "Darrick J. Wong" <djwong@...nel.org>
Cc: Thomas Weißschuh <linux@...ssschuh.net>,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Willy Tarreau <w@....eu>,
Zhangjin Wu <falcon@...ylab.org>
Subject: Re: [PATCH] mm: make MEMFD_CREATE into a selectable config option
On 06/30/23 08:32, Darrick J. Wong wrote:
> On Fri, Jun 30, 2023 at 11:08:53AM +0200, Thomas Weißschuh wrote:
> > The memfd_create() syscall, enabled by CONFIG_MEMFD_CREATE, is useful on
> > its own even when not required by CONFIG_TMPFS or CONFIG_HUGETLBFS.
>
> If you don't have tmpfs or hugetlbfs enabled, then what fs ends up
> backing the file returned by memfd_create()? ramfs?
>
> (Not an objection, I'm just curious...)
>
It looks like shmem/tmpfs falls back to ramfs?
--
Mike Kravetz
Powered by blists - more mailing lists