From: Christoph Hellwig <hch@infradead.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: "Eric Curtin" <ecurtin@redhat.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-unionfs@vger.kernel.org, linux-erofs@lists.ozlabs.org,
"Daan De Meyer" <daan.j.demeyer@gmail.com>,
"Stephen Smoogen" <ssmoogen@redhat.com>,
"Yariv Rachmani" <yrachman@redhat.com>,
"Daniel Walsh" <dwalsh@redhat.com>,
"Douglas Landgraf" <dlandgra@redhat.com>,
"Alexander Larsson" <alexl@redhat.com>,
"Colin Walters" <walters@redhat.com>,
"Brian Masney" <bmasney@redhat.com>,
"Eric Chanudet" <echanude@redhat.com>,
"Pavol Brilla" <pbrilla@redhat.com>,
"Lokesh Mandvekar" <lmandvek@redhat.com>,
"Petr Šabata" <psabata@redhat.com>,
"Lennart Poettering" <lennart@poettering.net>,
"Luca Boccassi" <bluca@debian.org>, "Neal Gompa" <neal@gompa.dev>,
nvdimm@lists.linux.dev
Subject: Re: [RFC KERNEL] initoverlayfs - a scalable initial filesystem
Date: Mon, 11 Dec 2023 23:35:31 -0800 [thread overview]
Message-ID: <ZXgNQ85PdUKrQU1j@infradead.org> (raw)
In-Reply-To: <941aff31-6aa4-4c37-bb94-547c46250304@linux.alibaba.com>
On Tue, Dec 12, 2023 at 08:50:56AM +0800, Gao Xiang wrote:
> For non-virtualization cases, I guess you could try to use `memmap`
> kernel option [2] to specify a memory region by bootloaders which
> contains an EROFS rootfs and a customized init for booting as
> erofs+overlayfs at least for `initoverlayfs`. The main benefit is
> that the memory region specified by the bootloader can be directly
> used for mounting. But I never tried if this option actually works.
>
> Furthermore, compared to traditional ramdisks, using direct address
> can avoid page cache totally for uncompressed files like it can
> just use unencoded data as mmaped memory. For compressed files, it
> still needs page cache to support mmaped access but we could adapt
> more for persistent memory scenarios such as disable cache
> decompression compared to previous block devices.
>
> I'm not sure if it's worth implementing this in kernelspace since
> it's out of scope of an individual filesystem anyway.
IFF the use case turns out to be generally useful (it looks quite
convoluted and odd to me), we could esily do an initdax concept where
a chunk of memory passed by the bootloader is presented as a DAX device
properly without memmap hacks.
next prev parent reply other threads:[~2023-12-12 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOgh=Fwb+JCTQ-iqzjq8st9qbvauxc4gqqafjWG2Xc08MeBabQ@mail.gmail.com>
2023-12-12 0:50 ` [RFC KERNEL] initoverlayfs - a scalable initial filesystem Gao Xiang
2023-12-12 7:35 ` Christoph Hellwig [this message]
2023-12-12 7:50 ` Gao Xiang
2023-12-12 13:06 ` Christoph Hellwig
2023-12-12 21:17 ` Eric Curtin
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=ZXgNQ85PdUKrQU1j@infradead.org \
--to=hch@infradead.org \
--cc=alexl@redhat.com \
--cc=bluca@debian.org \
--cc=bmasney@redhat.com \
--cc=daan.j.demeyer@gmail.com \
--cc=dlandgra@redhat.com \
--cc=dwalsh@redhat.com \
--cc=echanude@redhat.com \
--cc=ecurtin@redhat.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=lennart@poettering.net \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=lmandvek@redhat.com \
--cc=neal@gompa.dev \
--cc=nvdimm@lists.linux.dev \
--cc=pbrilla@redhat.com \
--cc=psabata@redhat.com \
--cc=ssmoogen@redhat.com \
--cc=walters@redhat.com \
--cc=yrachman@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).