public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: Filipe Manana <fdmanana@kernel.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 7/7] btrfs: remove the subpage related warning message
Date: Wed, 26 Feb 2025 07:49:37 +1030	[thread overview]
Message-ID: <312b2af9-3062-4777-9f9c-35f4aeb8b0d3@suse.com> (raw)
In-Reply-To: <CAL3q7H5sT418ruX-s_V5F=5JiU6TthCq1O4K15Uc28oj0Xpv=Q@mail.gmail.com>



在 2025/2/26 04:40, Filipe Manana 写道:
> On Sun, Feb 23, 2025 at 11:47 PM Qu Wenruo <wqu@suse.com> wrote:
>>
>> Since the initial enablement of block size < page size support for
>> btrfs in v5.15, we have hit several milestones for block size < page
>> size (subpage) support:
>>
>> - RAID56 subpage support
>>    In v5.19
>>
>> - Refactored scrub support to support subpage better
>>    In v6.4
>>
>> - Block perfect (previously requires page aligned ranges) compressed write
>>    In v6.13
>>
>> - Various error handling fixes involving subpage
>>    In v6.14
>>
>> Finally the only missing feature is the pretty simple and harmless
>> inlined data extent creation, just done in previous patches.
>>
>> Now btrfs has all of its features ready for both regular and subpage
>> cases, there is no reason to output a warning about the experimental
>> subpage support, and we can finally remove it now.
>>
>> Signed-off-by: Qu Wenruo <wqu@suse.com>
> 
> I don't have a machine to test block size < page size, but I trust you
> did all the testing besides being the expert on the code base for the
> feature, so:

There will a be a very small patch series (3 patches, < 70 lines of 
modification), to enable 2K block size on DEBUG btrfs builds.

Although with a lot of extra limitations, it should be enough to trigger 
most (if not all) bugs involved in this series.

The fstests to avoid the 2K block size limit will be a much big work 
though...

Thanks,
Qu

> 
> Acked-by: Filipe Manana <fdmanana@suse.com>
> 
> Thanks.
> 
>> ---
>>   fs/btrfs/disk-io.c | 5 -----
>>   1 file changed, 5 deletions(-)
>>
>> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
>> index a799216aa264..c0b40dedceb5 100644
>> --- a/fs/btrfs/disk-io.c
>> +++ b/fs/btrfs/disk-io.c
>> @@ -3414,11 +3414,6 @@ int __cold open_ctree(struct super_block *sb, struct btrfs_fs_devices *fs_device
>>           */
>>          fs_info->max_inline = min_t(u64, fs_info->max_inline, fs_info->sectorsize);
>>
>> -       if (sectorsize < PAGE_SIZE)
>> -               btrfs_warn(fs_info,
>> -               "read-write for sector size %u with page size %lu is experimental",
>> -                          sectorsize, PAGE_SIZE);
>> -
>>          ret = btrfs_init_workqueues(fs_info);
>>          if (ret)
>>                  goto fail_sb_buffer;
>> --
>> 2.48.1
>>
>>


      reply	other threads:[~2025-02-25 21:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-23 23:46 [PATCH 0/7] btrfs: make subpage handling be feature full Qu Wenruo
2025-02-23 23:46 ` [PATCH 1/7] btrfs: prevent inline data extents read from touching blocks beyond its range Qu Wenruo
2025-02-25 15:07   ` Filipe Manana
2025-02-25 16:10     ` Filipe Manana
2025-02-23 23:46 ` [PATCH 2/7] btrfs: fix the qgroup data free range for inline data extents Qu Wenruo
2025-02-25 15:11   ` Filipe Manana
2025-02-23 23:46 ` [PATCH 3/7] btrfs: introduce a read path dedicated extent lock helper Qu Wenruo
2025-02-25 17:05   ` Filipe Manana
2025-02-25 21:12     ` Qu Wenruo
2025-02-25 23:44       ` Qu Wenruo
2025-02-26 11:07         ` Filipe Manana
2025-02-26 11:07       ` Filipe Manana
2025-02-23 23:46 ` [PATCH 4/7] btrfs: make btrfs_do_readpage() to do block-by-block read Qu Wenruo
2025-02-25 17:09   ` Filipe Manana
2025-02-23 23:46 ` [PATCH 5/7] btrfs: allow buffered write to avoid full page read if it's block aligned Qu Wenruo
2025-02-25 17:55   ` Filipe Manana
2025-02-25 21:16     ` Qu Wenruo
2025-02-23 23:46 ` [PATCH 6/7] btrfs: allow inline data extents creation if block size < page size Qu Wenruo
2025-02-25 18:03   ` Filipe Manana
2025-02-23 23:46 ` [PATCH 7/7] btrfs: remove the subpage related warning message Qu Wenruo
2025-02-25 18:10   ` Filipe Manana
2025-02-25 21:19     ` Qu Wenruo [this message]

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=312b2af9-3062-4777-9f9c-35f4aeb8b0d3@suse.com \
    --to=wqu@suse.com \
    --cc=fdmanana@kernel.org \
    --cc=linux-btrfs@vger.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