From: Eric Curtin <ecurtin@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Gao Xiang" <hsiangkao@linux.alibaba.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 21:17:29 +0000 [thread overview]
Message-ID: <CAOgh=Fw2TcOFgCz1HbU1E=_HGRnf1PTTG2Qp_nD1D9f083RwUA@mail.gmail.com> (raw)
In-Reply-To: <ZXha1IxzRfhsRNOu@infradead.org>
On Tue, 12 Dec 2023 at 13:06, Christoph Hellwig <hch@infradead.org> wrote:
>
> 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.
>
I was politely poked this morning to highlight the graphs on the
initoverlayfs page, so as promised highlighting. That's not to say
this is either kernelspace's or userspace's role to optimize, but it
does prove there are benefits if we put some effort into optimizing
early boot.
https://github.com/containers/initoverlayfs
With this approach systemd starts ~300ms faster on a Raspberry Pi 4
with sd card, and this systemd instance has access to all the files
that a traditional initramfs would. I did this test on a Raspberry Pi
4 with NVMe drive over USB and the results were closer to a 500ms
benefit in systemd start time.
Is mise le meas/Regards,
Eric Curtin
prev parent reply other threads:[~2023-12-12 21:18 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
2023-12-12 21:17 ` Eric Curtin [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='CAOgh=Fw2TcOFgCz1HbU1E=_HGRnf1PTTG2Qp_nD1D9f083RwUA@mail.gmail.com' \
--to=ecurtin@redhat.com \
--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=hch@infradead.org \
--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 NNTP newsgroup(s).