From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Sandeep Dhavale <dhavale@google.com>
Cc: kernel-team@android.com, linux-erofs@lists.ozlabs.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/4] erofs: add file-backed mount support
Date: Sat, 31 Aug 2024 11:00:18 +0800 [thread overview]
Message-ID: <134cbf1b-06fd-41fb-830b-ba97e6ae4bfe@linux.alibaba.com> (raw)
In-Reply-To: <CAB=BE-R3wU7hBBaeAXdkDp2kvODxSFWNQtcmc5tCppN5qwdQgw@mail.gmail.com>
Hi Sandeep,
On 2024/8/31 08:30, Sandeep Dhavale via Linux-erofs wrote:
> On Thu, Aug 29, 2024 at 8:29 PM Gao Xiang <hsiangkao@linux.alibaba.com> wrote:
>>
>> It actually has been around for years: For containers and other sandbox
>> use cases, there will be thousands (and even more) of authenticated
>> (sub)images running on the same host, unlike OS images.
>>
>> Of course, all scenarios can use the same EROFS on-disk format, but
>> bdev-backed mounts just work well for OS images since golden data is
>> dumped into real block devices. However, it's somewhat hard for
>> container runtimes to manage and isolate so many unnecessary virtual
>> block devices safely and efficiently [1]: they just look like a burden
>> to orchestrators and file-backed mounts are preferred indeed. There
>> were already enough attempts such as Incremental FS, the original
>> ComposeFS and PuzzleFS acting in the same way for immutable fses. As
>> for current EROFS users, ComposeFS, containerd and Android APEXs will
>> be directly benefited from it.
>>
> Hi Gao,
> Thank you for the series! This is an interesting idea and will
> definitely help the Android ecosystem for APEXes if we can remove the
> loopback device. I will take a deeper look and provide comments soon.
Yes, I've seen no issue so far, and it will be submited for 6.12
since there are many users which really need this and wait for it.
Thanks,
Gao Xiang
next prev parent reply other threads:[~2024-08-31 3:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 3:28 Gao Xiang
2024-08-30 3:28 ` [PATCH v2 2/4] erofs: support unencoded inodes for fileio Gao Xiang
2024-08-31 0:19 ` Sandeep Dhavale
2024-08-31 2:54 ` Gao Xiang
2024-08-31 4:25 ` Sandeep Dhavale
2024-08-31 7:54 ` Gao Xiang
2024-09-01 20:47 ` Sandeep Dhavale
2024-09-04 6:56 ` Gao Xiang
2024-09-05 9:01 ` Chao Yu
2024-09-05 9:13 ` Gao Xiang
2024-08-30 3:28 ` [PATCH v2 3/4] erofs: support compressed " Gao Xiang
2024-09-01 20:47 ` Sandeep Dhavale
2024-09-05 9:01 ` Chao Yu
2024-09-05 9:14 ` Gao Xiang
2024-09-05 9:46 ` Chao Yu
2024-08-30 3:28 ` [PATCH v2 4/4] erofs: mark experimental fscache backend deprecated Gao Xiang
2024-09-01 20:48 ` Sandeep Dhavale
2024-09-05 9:03 ` Chao Yu
2024-08-31 0:30 ` [PATCH v2 1/4] erofs: add file-backed mount support Sandeep Dhavale
2024-08-31 3:00 ` Gao Xiang [this message]
2024-09-01 20:46 ` Sandeep Dhavale
2024-09-05 8:22 ` Chao Yu
2024-09-05 9:30 ` [PATCH v3 2/4] erofs: support unencoded inodes for fileio Gao Xiang
2024-09-05 9:44 ` Chao Yu
2024-09-24 9:21 ` [PATCH v2 1/4] erofs: add file-backed mount support Geert Uytterhoeven
2024-09-24 9:29 ` Gao Xiang
2024-09-30 14:18 ` Jan Kara
2024-09-30 14:22 ` Geert Uytterhoeven
2024-10-02 6:12 ` Christian Brauner
2024-10-02 11:25 ` Gao Xiang
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=134cbf1b-06fd-41fb-830b-ba97e6ae4bfe@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=dhavale@google.com \
--cc=kernel-team@android.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®