From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Hongbo Li <lihongbo22@huawei.com>,
xiang@kernel.org, chao@kernel.org, huyue2@coolpad.com,
jefflexu@linux.alibaba.com
Cc: linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 0/4] erofs-utils: Add --meta_fix and --meta_only format options
Date: Tue, 22 Apr 2025 21:50:20 +0800 [thread overview]
Message-ID: <2408568f-a9e6-4e32-83b2-e79aee83a55a@linux.alibaba.com> (raw)
In-Reply-To: <20250422123612.261764-1-lihongbo22@huawei.com>
Hi Hongbo,
On 2025/4/22 20:36, Hongbo Li wrote:
> In this patchset, we have added two formatting options --meta_fix and
> --meta_only to extend the ability of EROFS. In the case of using OBS,
> we can convert the directory tree structure from OBS into the erofs
> image and implement on-demand loading logic based on this. Since OBS
> objects are often large, we need to separate the metadata area from
> the data area, which is the reason we introduce the --meta_fix option.
> To accelerate the formatting process, we can skip the formatting of
> the raw data by adding --meta_only option.
Thanks for the patches!
I wonder if it's possible to reuse blobchunk.c codebase for
such usage in the short term.
Also I hope there could be some better option knobs for these
new features.
>
> A simple usage example is as follows:
> 1. Build one xattr with OBS key in s3fs.
> 2. mkfs.erofs --meta_fix --meta_only data.img /mnt/s3fs to format
> 3. Implement the loading logic in kernel or userspace.
>
> Based on the above logic, we can easily expose the directory tree
> from OBS to users in the form of the EROFS file system and implement
> on-demand data loading for large OBS objects.
BTW, It's possible to upstream OBS implementation to erofs-utils
if any chance?
Thanks,
Gao Xiang
next prev parent reply other threads:[~2025-04-22 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 12:36 [PATCH RFC 0/4] erofs-utils: Add --meta_fix and --meta_only format options Hongbo Li
2025-04-22 12:36 ` [PATCH RFC 1/4] erofs-utils: lib: introduce --meta_fix format option Hongbo Li
2025-04-22 12:36 ` [PATCH RFC 2/4] erofs-utils: lib: Implement the main logic for --meta_fix option Hongbo Li
2025-04-22 12:36 ` [PATCH RFC 3/4] erofs-utils: lib: add --meta_only format option Hongbo Li
2025-04-22 12:36 ` [PATCH RFC 4/4] erofs-utils: lib: remove the compile warning Hongbo Li
2025-04-22 13:50 ` Gao Xiang [this message]
2025-04-22 14:37 ` [PATCH RFC 0/4] erofs-utils: Add --meta_fix and --meta_only format options Hongbo Li
2025-04-24 0:39 ` 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=2408568f-a9e6-4e32-83b2-e79aee83a55a@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=chao@kernel.org \
--cc=huyue2@coolpad.com \
--cc=jefflexu@linux.alibaba.com \
--cc=lihongbo22@huawei.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiang@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