public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: allow creating inline data extents for sector size < page size case
Date: Fri, 15 Nov 2024 16:33:42 +1030	[thread overview]
Message-ID: <cover.1731650263.git.wqu@suse.com> (raw)

There are two features disabled when sector size < page size (subpage) is
allowed for btrfs:

- Inline data extent creation
- Sector perfect compressed write

Both share one critical technical problem, that inline or async
submission all unlock the whole page.

Thankfully the major technical blockage is already solved with the
recent sector perfect compressed write support for subpage cases.

So there is no need to disable inline data extent creation either.
Yes, there are cases we can mixing inline and regular data extents, but
that's also the case when page size == sector size, so it's not a show
stopper.

The first patch is to fix a harmless bug that is only affecting subpage
cases.
The second one enables the inline data extent creation for subpage
cases.

Qu Wenruo (2):
  btrfs: fix the qgroup data free range for inline data extents
  btrfs: allow inline data extents creation if sector size < page size

 fs/btrfs/inode.c | 15 +--------------
 1 file changed, 1 insertion(+), 14 deletions(-)

-- 
2.47.0


             reply	other threads:[~2024-11-15  6:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-15  6:03 Qu Wenruo [this message]
2024-11-15  6:03 ` [PATCH 1/2] btrfs: fix the qgroup data free range for inline data extents Qu Wenruo
2024-11-15  6:03 ` [PATCH 2/2] btrfs: allow inline data extents creation if sector size < page size 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.1731650263.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox