All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/7] btrfs: remove ASSERT()s for folio_order() and folio_test_large()
Date: Thu, 13 Mar 2025 14:50:42 +1030	[thread overview]
Message-ID: <cover.1741839616.git.wqu@suse.com> (raw)

There are quite some ASSERT()s checking folio_order() or
folio_test_large() on data folios.

They are the blockage for the incoming larger data folios.

This series will remove most of them, with the following exceptions
remaining:

- wait_dev_supers() and write_dev_supers()
  They are folios from block device cache, will not be affected by our
  larger data folios support.

- relocation_one_folio()
  It's about data relocation inode, and we can disable larger data folios
  for such special inode easily.

- btrfs_attach_subpage()
  The folio_test_large() is only for metadata, just change it to be a
  metadata specific check.

- defrage_prepare_one_folio()
  It rejects larger folios gracefully so no need to handle it yet.
  Although we still need some extra work to make defrag to properly
  support larger folios.

- btrfs_end_repair_bio()
  This will be covered by a dedicated series converting the bio layer to
  use folio interfaces other than bvec interfaces.
  Until then the ASSERT() will stay.

The first patch is just a small cleanup for send, exposed during the
removal of ASSERT()s.

Qu Wenruo (7):
  btrfs: send: remove the again label inside put_file_data()
  btrfs: send: prepare put_file_data() for larger data folios
  btrfs: prepare btrfs_page_mkwrite() for larger data folios
  btrfs: prepare prepare_one_folio() for larger data folios
  btrfs: prepare end_bbio_data_write() for larger data folios
  btrfs: subpage: prepare for larger data folios
  btrfs: zlib: prepare copy_data_into_buffer() for larger data folios

 fs/btrfs/extent_io.c |  3 ---
 fs/btrfs/file.c      |  6 +-----
 fs/btrfs/send.c      | 29 +++++++++++++----------------
 fs/btrfs/subpage.c   |  6 ++----
 fs/btrfs/zlib.c      |  2 --
 5 files changed, 16 insertions(+), 30 deletions(-)

-- 
2.48.1


             reply	other threads:[~2025-03-13  4:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13  4:20 Qu Wenruo [this message]
2025-03-13  4:20 ` [PATCH 1/7] btrfs: send: remove the again label inside put_file_data() Qu Wenruo
2025-03-14 16:52   ` David Sterba
2025-03-14 21:50     ` Qu Wenruo
2025-03-14 22:58       ` David Sterba
2025-03-14 23:25         ` Qu Wenruo
2025-03-14 23:38           ` David Sterba
2025-03-13  4:20 ` [PATCH 2/7] btrfs: send: prepare put_file_data() for larger data folios Qu Wenruo
2025-03-13  4:20 ` [PATCH 3/7] btrfs: prepare btrfs_page_mkwrite() " Qu Wenruo
2025-03-13  4:20 ` [PATCH 4/7] btrfs: prepare prepare_one_folio() " Qu Wenruo
2025-03-13  4:20 ` [PATCH 5/7] btrfs: prepare end_bbio_data_write() " Qu Wenruo
2025-03-13  4:20 ` [PATCH 6/7] btrfs: subpage: prepare " Qu Wenruo
2025-03-13  4:20 ` [PATCH 7/7] btrfs: zlib: prepare copy_data_into_buffer() " Qu Wenruo

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=cover.1741839616.git.wqu@suse.com \
    --to=wqu@suse.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.