From: Chao Yu <chao@kernel.org>
To: Jia Zhu <zhujia.zj@bytedance.com>,
xiang@kernel.org, gerry@linux.alibaba.com,
linux-erofs@lists.ozlabs.org, jefflexu@linux.alibaba.com
Cc: huyue2@coolpad.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3] erofs: support flattened block device for multi-blob images
Date: Sun, 16 Apr 2023 22:30:44 +0800 [thread overview]
Message-ID: <78f01742-a672-7471-ccb3-e38d5047dab9@kernel.org> (raw)
In-Reply-To: <20230302071751.48425-1-zhujia.zj@bytedance.com>
On 2023/3/2 15:17, Jia Zhu wrote:
> In order to support mounting multi-blobs container image as a single
> block device, add flattened block device feature for EROFS.
>
> In this mode, all meta/data contents will be mapped into one block
> address. User could compose a block device(by nbd/ublk/virtio-blk/
> vhost-user-blk) from multiple sources and mount the block device by
> EROFS directly. It can reduce the number of block devices used, and
> it's also benefits in both VM file passthrough and distributed storage
> scenarios.
>
> You can test this using the method mentioned by:
> https://github.com/dragonflyoss/image-service/pull/1111
> 1. Compose a (nbd)block device from multi-blobs.
> 2. Mount EROFS on mntdir/.
> 3. Compare the md5sum between source dir and mntdir/.
>
> Later, we could also use it to refer original tar blobs.
>
> Signed-off-by: Jia Zhu <zhujia.zj@bytedance.com>
> Signed-off-by: Xin Yin <yinxin.x@bytedance.com>
> Reviewed-by: Jingbo Xu <jefflexu@linux.alibaba.com>
Acked-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2023-04-16 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 12:59 [PATCH V2] erofs: support flattened block device for multi-blob images Jia Zhu
2023-03-02 6:39 ` Jingbo Xu
2023-03-02 7:17 ` [PATCH V3] " Jia Zhu
2023-04-16 14:30 ` Chao Yu [this message]
2023-04-16 14:34 ` Gerry Liu
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=78f01742-a672-7471-ccb3-e38d5047dab9@kernel.org \
--to=chao@kernel.org \
--cc=gerry@linux.alibaba.com \
--cc=huyue2@coolpad.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiang@kernel.org \
--cc=zhujia.zj@bytedance.com \
/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).