From: Christoph Hellwig <hch@infradead.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: "Christoph Hellwig" <hch@infradead.org>,
"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: Tue, 12 Dec 2023 05:06:28 -0800 [thread overview]
Message-ID: <ZXha1IxzRfhsRNOu@infradead.org> (raw)
In-Reply-To: <58d175f8-a06e-4b00-95fe-1bd5a79106df@linux.alibaba.com>
On Tue, Dec 12, 2023 at 03:50:25PM +0800, Gao Xiang wrote:
> I have no idea how it's faster than the current initramfs or initrd.
> So if it's really useful, maybe some numbers can be posted first
> with the current `memmap` hack and see it's worth going further with
> some new infrastructure like initdax.
Agreed.
next prev parent reply other threads:[~2023-12-12 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 13:45 [RFC KERNEL] initoverlayfs - a scalable initial filesystem Eric Curtin
2023-12-11 14:17 ` Neal Gompa
2023-12-12 0:50 ` Gao Xiang
2023-12-12 7:35 ` Christoph Hellwig
2023-12-12 7:50 ` Gao Xiang
2023-12-12 13:06 ` Christoph Hellwig [this message]
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=ZXha1IxzRfhsRNOu@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