From: Josef Bacik <josef@toxicpanda.com>
To: Neal Gompa <neal@gompa.dev>
Cc: Linux BTRFS Development <linux-btrfs@vger.kernel.org>,
Anand Jain <anand.jain@oracle.com>,
Qu Wenruo <quwenruo.btrfs@gmx.com>, Qu Wenruo <wqu@suse.com>,
David Sterba <dsterba@suse.cz>, Hector Martin <marcan@marcan.st>,
Sven Peter <sven@svenpeter.dev>,
Davide Cavalca <davide@cavalca.name>, Jens Axboe <axboe@fb.com>,
Asahi Lina <lina@asahilina.net>,
Asahi Linux <asahi@lists.linux.dev>
Subject: Re: [PATCH v4 0/1] Enforce 4k sectorize by default for mkfs
Date: Mon, 27 Nov 2023 11:07:05 -0500 [thread overview]
Message-ID: <20231127160705.GC2366036@perftesting> (raw)
In-Reply-To: <20231116160235.2708131-1-neal@gompa.dev>
On Thu, Nov 16, 2023 at 11:02:23AM -0500, Neal Gompa wrote:
> The Fedora Asahi SIG[0] is working on bringing up support for
> Apple Silicon Macintosh computers through the Fedora Asahi Remix[1].
>
> Apple Silicon Macs are unusual in that they currently require 16k
> page sizes, which means that the current default for mkfs.btrfs(8)
> makes a filesystem that is unreadable on x86 PCs and most other ARM
> PCs.
>
> This is now even more of a problem within Apple Silicon Macs as it is now
> possible to nest 4K Fedora Linux VMs on 16K Fedora Asahi Remix machines to
> enable performant x86 emulation[2] and the host storage needs to be compatible
> for both environments.
>
> Thus, I'd like to see us finally make the switchover to 4k sectorsize
> for new filesystems by default, regardless of page size.
>
> The initial test run by Hector Martin[3] at request of Qu Wenruo
> looked promising[4], and we've been running with this behavior on
> Fedora Linux since Fedora Linux 36 (at around 6.2) with no issues.
>
This is a good change and well documented. This isn't being ignored, it's just
a policy change that we have to be conservative about considering. We only in
the last 3 months have added a Apple Silicon machine to our testing
infrastructure (running Fedora Asahi fwiw) to make sure we're getting consistent
subpage-blocksize testing. Generally speaking it's been fine, we've fixed a few
things and haven't broken anything, but it's still comes with some risks when
compared to the default of using the pagesize.
We will continue to discuss this amongst ourselves and figure out what we think
would be a reasonable timeframe to make this switch and let you know what we're
thinking ASAP. Thanks,
Josef
next prev parent reply other threads:[~2023-11-27 16:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 16:02 [PATCH v4 0/1] Enforce 4k sectorize by default for mkfs Neal Gompa
2023-11-16 16:02 ` [PATCH v4 1/1] btrfs-progs: mkfs: Enforce 4k sectorsize by default Neal Gompa
2023-11-17 10:41 ` Eric Curtin
2023-11-27 16:07 ` Josef Bacik [this message]
2023-11-28 15:01 ` [PATCH v4 0/1] Enforce 4k sectorize by default for mkfs Hector Martin
2023-11-28 19:57 ` Qu Wenruo
2023-11-28 20:09 ` Roman Mamedov
2023-11-28 20:31 ` Qu Wenruo
2023-11-28 21:24 ` Neal Gompa
2023-11-29 12:58 ` Hector Martin
2023-11-29 20:27 ` Qu Wenruo
2023-11-30 3:38 ` Neal Gompa
2023-12-13 22:25 ` David Sterba
2024-01-05 23:10 ` Neal Gompa
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=20231127160705.GC2366036@perftesting \
--to=josef@toxicpanda.com \
--cc=anand.jain@oracle.com \
--cc=asahi@lists.linux.dev \
--cc=axboe@fb.com \
--cc=davide@cavalca.name \
--cc=dsterba@suse.cz \
--cc=lina@asahilina.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=neal@gompa.dev \
--cc=quwenruo.btrfs@gmx.com \
--cc=sven@svenpeter.dev \
--cc=wqu@suse.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