public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Neal Gompa <neal@gompa.dev>, Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/4] btrfs: initial subpage support for zoned devices
Date: Mon, 4 Mar 2024 18:02:20 +1030	[thread overview]
Message-ID: <e4bd611d-1187-4f91-aee8-91a028ab11b2@gmx.com> (raw)
In-Reply-To: <CAEg-Je-tpYX5rikHjf3mXeqN1Rj+3Tr9arAift2j+Ycj+ma-sQ@mail.gmail.com>



在 2024/3/4 15:40, Neal Gompa 写道:
> On Sun, Mar 3, 2024 at 10:13 PM Qu Wenruo <wqu@suse.com> wrote:
>>
>> Ping?
>>
>> I know this is a very niche scenario (subpage + zoned), and the change
>> itself looks very scary, but the change should be safe for non-subpage
>> routine (as the new lock all delalloc ranges covers the page would still
>> at most lock one delalloc range for normal cases).
>>
>> Furthermore without this series, there seems be no proper way to support
>> subpage + zoned, unless we do a much larger change to merge
>> extent_writepage_io() into run_delalloc_range() (which I believe it's
>> still needed, but can be done in the future).
>>
>
> On the contrary, I don't think this is a niche scenario at all. Quite
> the opposite: I expect this to be a *very* common scenario because we
> will see AArch64 systems increasingly rely on subpage because 16K
> AArch64 Linux is used on two very popular platforms: Apple Silicon
> Macs (Fedora Asahi Remix) and Raspberry Pi 5 (Raspbian/RPi OS).

In fact, the above 2 platforms further prove this is still a very niche
combination, at least for consumer hardware.

Apple Silicons, you know it's the usual anti-repair and anti-customer
Apple, there is no way to add a zoned device natively, and if one goes a
convertor/dongle, I strongly doubt if a SATA/SAS to USB convertor
supports APPEND operation correctly.

It's possible to go thunderbolt -> PCIE -> U.2/NVME to attach a ZNS
device, but I strongly doubt if any Asahi Linux user has such hardware
to go in the first place.

It's the same for RPI5, I really appreciate the performance improvement
since RPI4, but the IO is even worse than Apple, and not really get any
better even in RPI5.

For my environment, it's indeed aarch64, but with a better board with a
lot of more IOs (RK3588, 4x PCIE3.0 + 1x PCIE2.0 + 1x PCIE2.0), but it's
still not ideal, and I have to go tcmu-runner to emulate a zoned HDD.

Unfortunately, we're still in the wild west of subpage world.

Thanks,
Qu
>
> We *need* this series, but I do not have the hardware to stress this
> patch set, unfortunately.
>
> The code otherwise looks reasonable to me, though.
>
> Acked-by: Neal Gompa <neal@gompa.dev>
>
>

  reply	other threads:[~2024-03-04  7:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19  6:08 [PATCH 0/4] btrfs: initial subpage support for zoned devices Qu Wenruo
2024-02-19  6:08 ` [PATCH 1/4] btrfs: make __extent_writepage_io() to write specified range only Qu Wenruo
2024-02-19  6:08 ` [PATCH 2/4] btrfs: lock subpage ranges in one go for writepage_delalloc() Qu Wenruo
2024-02-19  6:08 ` [PATCH 3/4] btrfs: subpage: introduce helpers to handle subpage delalloc locking Qu Wenruo
2024-02-20  0:52   ` kernel test robot
2024-02-20  1:16     ` Qu Wenruo
2024-02-20  7:58       ` Yujie Liu
2024-02-20  8:26         ` Qu Wenruo
2024-02-20  9:23           ` Yujie Liu
2024-02-19  6:08 ` [PATCH 4/4] btrfs: migrate writepage_delalloc() to use subpage helpers Qu Wenruo
2024-03-04  3:13 ` [PATCH 0/4] btrfs: initial subpage support for zoned devices Qu Wenruo
2024-03-04  5:10   ` Neal Gompa
2024-03-04  7:32     ` Qu Wenruo [this message]
2024-03-04 10:51       ` 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=e4bd611d-1187-4f91-aee8-91a028ab11b2@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=neal@gompa.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