From: Chao Yu <chao@kernel.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>, linux-erofs@lists.ozlabs.org
Cc: chao@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 1/2] erofs: add on-disk definition for metadata compression
Date: Mon, 21 Jul 2025 17:28:56 +0800 [thread overview]
Message-ID: <b66bc9ae-2ed9-499c-a06f-6f9817880fa8@kernel.org> (raw)
In-Reply-To: <20250717070804.1446345-2-hsiangkao@linux.alibaba.com>
On 7/17/25 15:08, Gao Xiang wrote:
> Filesystem metadata has a high degree of redundancy, so it should
> compress well in the general case.
>
> Although metadata compression can increase overall I/O latency, many
> users care more about minimized image sizes than extreme runtime
> performance. Let's implement metadata compression in response to user
> requests [1].
>
> Actually, it's quite simple to implement metadata compression: since
> EROFS already supports per-inode compression, we can simply treat a
> special inode (called `the metabox inode`) as a container for compressed
> inode metadata. Since EROFS supports multiple algorithms, users can
> even specify LZ4 for metadata and LZMA for data.
>
> To better support incremental builds, the MSB of NIDs indicates where
> the inode metadata is located: if bit 63 is set, the inode itself should
> be read from `the metabox inode`.
>
> Optionally, shared xattrs can also be kept in `the metabox inode` if
> COMPAT_SHARED_EA_IN_METABOX is set.
>
> [1] https://issues.redhat.com/browse/RHEL-75783
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Acked-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2025-07-21 9:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 17:33 [PATCH v3 0/2] erofs: support metadata compression Gao Xiang
2025-07-16 17:33 ` [PATCH v3 1/2] erofs: add on-disk definition for " Gao Xiang
2025-07-16 17:33 ` [PATCH v3 2/2] erofs: implement " Gao Xiang
2025-07-16 17:58 ` [PATCH v4 " Gao Xiang
2025-07-17 7:08 ` [PATCH v5 0/3] erofs: support " Gao Xiang
2025-07-17 7:08 ` [PATCH v5 1/2] erofs: add on-disk definition for " Gao Xiang
2025-07-21 9:28 ` Chao Yu [this message]
2025-07-17 7:08 ` [PATCH v5 2/2] erofs: implement " Gao Xiang
2025-07-18 3:19 ` [PATCH v6 " Gao Xiang
2025-07-21 9:29 ` Chao Yu
2025-07-22 0:32 ` [PATCH v7 " 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=b66bc9ae-2ed9-499c-a06f-6f9817880fa8@kernel.org \
--to=chao@kernel.org \
--cc=hsiangkao@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).