From: Askar Safin <safinaskar@gmail.com>
To: Eric Curtin <ecurtin@redhat.com>
Cc: initramfs@vger.kernel.org
Subject: Re: [RFC] initoverlayfs - a scalable initial filesystem
Date: Tue, 19 Dec 2023 02:31:44 +0300 [thread overview]
Message-ID: <CAPnZJGAALQKGR4ieqWd3eJ6MmuqwqweN=Xb5TqjPAGNFDknsug@mail.gmail.com> (raw)
In-Reply-To: <CAOgh=FyA94-7YqGpsAqVQjadegRusoAvRhD=t-ipzVWN0CiJRQ@mail.gmail.com>
> Yes, your understanding is correct
Cool! Then I think your current solution is better than other
solutions proposed in the thread. I. e. it is better than to have the
bootloader to load erofs image into memory, because we don't want this
extra copy
--
Askar Safin
next prev parent reply other threads:[~2023-12-18 23:32 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 21:59 [RFC] initoverlayfs - a scalable initial filesystem Askar Safin
[not found] ` <CAOgh=FyA94-7YqGpsAqVQjadegRusoAvRhD=t-ipzVWN0CiJRQ@mail.gmail.com>
2023-12-18 23:31 ` Askar Safin [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-08 17:59 Eric Curtin
2023-12-09 12:46 ` Luca Boccassi
2023-12-09 14:42 ` Eric Curtin
2023-12-09 14:56 ` Andrei Borzenkov
2023-12-09 15:07 ` Eric Curtin
2023-12-09 15:22 ` Daan De Meyer
2023-12-09 15:46 ` Eric Curtin
2023-12-09 17:19 ` Luca Boccassi
2023-12-09 17:24 ` Eric Curtin
2023-12-09 17:46 ` Luca Boccassi
2023-12-09 17:57 ` Eric Curtin
2023-12-09 18:11 ` Luca Boccassi
2023-12-09 18:26 ` Eric Curtin
2023-12-11 9:57 ` Lennart Poettering
2023-12-11 10:07 ` Lennart Poettering
2023-12-11 11:20 ` Eric Curtin
2023-12-11 11:28 ` Eric Curtin
2023-12-11 11:42 ` Eric Curtin
2023-12-11 11:58 ` Lennart Poettering
2023-12-11 11:51 ` Lennart Poettering
2023-12-11 12:48 ` Eric Curtin
2023-12-11 12:52 ` Eric Curtin
2023-12-12 17:37 ` Lennart Poettering
2023-12-12 17:40 ` Lennart Poettering
2023-12-12 19:05 ` Demi Marie Obenour
2023-12-11 16:28 ` Demi Marie Obenour
2023-12-11 17:03 ` Eric Curtin
2023-12-11 17:46 ` Demi Marie Obenour
2023-12-12 18:00 ` Lennart Poettering
2023-12-12 20:34 ` Nils Kattenbeck
2023-12-12 20:48 ` Eric Curtin
2023-12-12 21:02 ` Lennart Poettering
2023-12-12 22:01 ` Nils Kattenbeck
2023-12-13 9:03 ` Lennart Poettering
2023-12-14 1:17 ` Nils Kattenbeck
2023-12-16 14:34 ` Lennart Poettering
2023-12-11 17:33 ` Neal Gompa
2023-12-11 20:15 ` Luca Boccassi
2023-12-11 20:43 ` Demi Marie Obenour
2023-12-11 20:58 ` Luca Boccassi
2023-12-11 21:20 ` Demi Marie Obenour
2023-12-11 21:45 ` Luca Boccassi
2023-12-12 3:47 ` Paul Menzel
2023-12-12 3:56 ` Paul Menzel
2023-12-12 15:26 ` Paul Menzel
2023-12-11 21:24 ` Eric Curtin
2023-12-12 17:50 ` Lennart Poettering
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='CAPnZJGAALQKGR4ieqWd3eJ6MmuqwqweN=Xb5TqjPAGNFDknsug@mail.gmail.com' \
--to=safinaskar@gmail.com \
--cc=ecurtin@redhat.com \
--cc=initramfs@vger.kernel.org \
/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).