From: Du Rui <durui@linux.alibaba.com>
To: gscrivan@redhat.com
Cc: agk@redhat.com, alexl@redhat.com, dm-devel@redhat.com,
durui@linux.alibaba.com, hsiangkao@linux.alibaba.com,
linux-kernel@vger.kernel.org, snitzer@kernel.org
Subject: Re: Re: dm overlaybd: targets mapping OverlayBD image
Date: Fri, 26 May 2023 18:28:56 +0800 [thread overview]
Message-ID: <20230526102855.36774-1-durui@linux.alibaba.com> (raw)
In-Reply-To: <87r0r6ywri.fsf@redhat.com>
Hi Giuseppe,
> The current OCI format, with some tweaks like (e)stargz or zstd:chunked,
> already make its content addressable and a client can retrieve only the
> subset of the files that are needed. At the same time we maintain the
> simplicity of a tarball and it won't break existing clients.
Yes, I believe backward compatibility is very important. That's why we
have another design called foci (fast oci). It realize a virtual block
device from gzip image blobs. See the following link for details if interested.
https://github.com/containerd/accelerated-container-image/blob/main/docs/FASTOCI.md
next prev parent reply other threads:[~2023-05-26 10:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 10:27 [RFC] dm overlaybd: targets mapping OverlayBD image Du Rui
2023-05-23 17:28 ` Mike Snitzer
2023-05-24 0:56 ` [dm-devel] " Gao Xiang
2023-05-24 6:43 ` Alexander Larsson
2023-05-24 7:13 ` Gao Xiang
2023-05-24 8:11 ` Giuseppe Scrivano
2023-05-24 8:26 ` Gao Xiang
2023-05-24 10:48 ` Giuseppe Scrivano
2023-05-24 11:06 ` Gao Xiang
2023-05-26 10:28 ` Du Rui [this message]
2023-05-26 10:26 ` Du Rui
2023-05-26 16:43 ` Gao Xiang
2023-05-27 3:13 ` Du Rui
2023-05-27 4:12 ` Gao Xiang
2023-05-24 6:59 ` Du Rui
2023-05-26 10:25 ` Du Rui
2023-05-24 7:24 ` [RFC PATCH v2] " Du Rui
2023-05-24 7:40 ` [RFC PATCH v3] " Du Rui
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=20230526102855.36774-1-durui@linux.alibaba.com \
--to=durui@linux.alibaba.com \
--cc=agk@redhat.com \
--cc=alexl@redhat.com \
--cc=dm-devel@redhat.com \
--cc=gscrivan@redhat.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@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).