From: Nick Chan <towinchenmi@gmail.com>
To: "Ernesto A. Fernández" <ernesto.mnd.fernandez@gmail.com>
Cc: Yangtao Li <frank.li@vivo.com>,
ethan@ethancedwards.com, asahi@lists.linux.dev,
brauner@kernel.org, dan.carpenter@linaro.org,
ernesto@corellium.com, gargaditya08@live.com,
gregkh@linuxfoundation.org, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev, sven@svenpeter.dev, tytso@mit.edu,
viro@zeniv.linux.org.uk, willy@infradead.org, slava@dubeyko.com,
glaubitz@physik.fu-berlin.de
Subject: Re: Subject: [RFC PATCH v2 0/8] staging: apfs: init APFS filesystem support
Date: Thu, 15 May 2025 13:08:19 +0800 [thread overview]
Message-ID: <e6a5a737-ce64-4d31-aeea-2e6190da2ff5@gmail.com> (raw)
In-Reply-To: <20250514201925.GA8597@eaf>
Ernesto A. Fernández 於 2025/5/15 凌晨4:19 寫道:
> Hi Nick,
>
> On Tue, May 13, 2025 at 12:13:23PM +0800, Nick Chan wrote:
>> 2. When running Linux on iPhone, iPad, iPod touch, Apple TV (currently there are Apple A7-A11 SoC support in
>> upstream), resizing the main APFS volume is not feasible especially on A11 due to shenanigans with the encrypted
>> data volume. So the safe ish way to store a file system on the disk becomes a using linux-apfs-rw on a (possibly
>> fixed size) volume that only has one file and that file is used as a loopback device.
> That's very interesting. Fragmentation will be brutal after a while though.
> Unless you are patching away the copy-on-write somehow?'
On a fixed size (preallocated size == max size) volume with only a single non-sparse file on it,
copy-on-write should not happen. I believe the xART volume is also the same case with only
one non-sparse file.
[...]
> Ernesto
Nick Chan
next prev parent reply other threads:[~2025-05-15 5:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 0:13 [RFC PATCH v2 0/8] staging: apfs: init APFS filesystem support Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 1/8] staging: apfs: init lzfse compression library for APFS Ethan Carter Edwards
2025-03-20 3:00 ` Aditya Garg
2025-03-20 0:13 ` [PATCH RFC v2 2/8] staging: apfs: init unicode.{c,h} Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 3/8] staging: apfs: init apfs_raw.h to handle on-disk structures Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 4/8] staging: apfs: init libzbitmap.{c,h} for decompression Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 5/8] staging: apfs: init APFS Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 6/8] staging: apfs: init build support for APFS Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 7/8] staging: apfs: init TODO and README.rst Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 8/8] MAINTAINERS: apfs: add entry and relevant information Ethan Carter Edwards
2025-03-20 0:43 ` [RFC PATCH v2 0/8] staging: apfs: init APFS filesystem support Gao Xiang
2025-03-20 5:39 ` Dan Carpenter
2025-05-12 10:11 ` Subject: " Yangtao Li
2025-05-12 23:40 ` Ernesto A. Fernández
2025-05-13 4:13 ` Nick Chan
2025-05-13 10:43 ` Jan Kara
2025-05-13 11:41 ` Aditya Garg
2025-05-14 20:19 ` Ernesto A. Fernández
2025-05-15 5:08 ` Nick Chan [this message]
2025-05-15 16:00 ` Sven Peter
2025-05-20 5:08 ` Yangtao Li
2025-05-20 18:59 ` Ernesto A. Fernández
2025-05-21 10:14 ` Jan Kara
2025-05-21 16:27 ` Ernesto A. Fernández
2025-05-15 5:10 ` John Paul Adrian Glaubitz
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=e6a5a737-ce64-4d31-aeea-2e6190da2ff5@gmail.com \
--to=towinchenmi@gmail.com \
--cc=asahi@lists.linux.dev \
--cc=brauner@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=ernesto.mnd.fernandez@gmail.com \
--cc=ernesto@corellium.com \
--cc=ethan@ethancedwards.com \
--cc=frank.li@vivo.com \
--cc=gargaditya08@live.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=slava@dubeyko.com \
--cc=sven@svenpeter.dev \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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