[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <198ead62fff.fc7d206346787.2754614060206901867@zohomail.com>
Date: Wed, 27 Aug 2025 13:22:42 +0400
From: Askar Safin <safinaskar@...omail.com>
To: "Gao Xiang" <hsiangkao@...ux.alibaba.com>
Cc: "Byron Stanoszek" <gandalf@...ds.org>, "Christoph Hellwig" <hch@....de>,
"gregkh" <gregkh@...uxfoundation.org>,
"julian.stecklina" <julian.stecklina@...erus-technology.de>,
"linux-fsdevel" <linux-fsdevel@...r.kernel.org>,
"linux-kernel" <linux-kernel@...r.kernel.org>,
"rafael" <rafael@...nel.org>,
"torvalds" <torvalds@...ux-foundation.org>,
"viro" <viro@...iv.linux.org.uk>,
"Thomas Weißschuh" <thomas.weissschuh@...utronix.de>,
"Christian Brauner" <brauner@...nel.org>
Subject: Re: [PATCH] initrd: support erofs as initrd
---- On Tue, 26 Aug 2025 19:32:34 +0400 Gao Xiang <hsiangkao@...ux.alibaba.com> wrote ---
> I completely agree with that point. However, since EROFS is a
> block-based filesystem (Thanks to strictly block alignment, meta(data)
> can work efficiently on both block-addressed storage
> devices and byte-addressed memory devices. Also if the fsblock size
As I said previously, just put your erofs image to initramfs
(or to disk) and then (in your initramfs init) create ramdisk out of it
or loop mount it (both ramdisks and loop devices are block devices).
This way you will have erofs on top of block device.
And you will not depend on initrd. (Again: I plan to remove initial ramdisk
support, not ramdisk support per se.)
--
Askar Safin
https://types.pl/@safinaskar
Powered by blists - more mailing lists