From: Dave Chen <davechen@synology.com>
To: linux-btrfs@vger.kernel.org, dsterba@suse.com
Cc: cccheng@synology.com, robbieko@synology.com,
Dave Chen <davechen@synology.com>
Subject: [PATCH] btrfs: skip clearing EXTENT_DEFRAG for nocow ordered extents
Date: Mon, 30 Mar 2026 11:31:48 +0800 [thread overview]
Message-ID: <20260330033148.696942-1-davechen@synology.com> (raw)
In btrfs_finish_one_ordered(), clear_bits is unconditionally initialized
with EXTENT_DEFRAG. For nocow ordered extents this is always a no-op
because should_nocow() already forces the COW path when EXTENT_DEFRAG is
set, so a nocow ordered extent can never have EXTENT_DEFRAG on its range.
Although harmless, the unconditional btrfs_clear_extent_bit() call still
performs a cold rbtree lookup under the io tree spinlock on every nocow
write completion. Avoid this by only adding EXTENT_DEFRAG to clear_bits
for non-nocow ordered extents, and skip the call entirely when there are
no bits to clear.
Signed-off-by: Dave Chen <davechen@synology.com>
Signed-off-by: Robbie Ko <robbieko@synology.com>
---
fs/btrfs/inode.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
index f643a05208720..80daf7e248ab8 100644
--- a/fs/btrfs/inode.c
+++ b/fs/btrfs/inode.c
@@ -3203,7 +3203,7 @@ int btrfs_finish_one_ordered(struct btrfs_ordered_extent *ordered_extent)
bool freespace_inode;
bool truncated = false;
bool clear_reserved_extent = true;
- unsigned int clear_bits = EXTENT_DEFRAG;
+ unsigned int clear_bits = 0;
start = ordered_extent->file_offset;
end = start + ordered_extent->num_bytes - 1;
@@ -3214,6 +3214,9 @@ int btrfs_finish_one_ordered(struct btrfs_ordered_extent *ordered_extent)
!test_bit(BTRFS_ORDERED_ENCODED, &ordered_extent->flags))
clear_bits |= EXTENT_DELALLOC_NEW;
+ if (!test_bit(BTRFS_ORDERED_NOCOW, &ordered_extent->flags))
+ clear_bits |= EXTENT_DEFRAG;
+
freespace_inode = btrfs_is_free_space_inode(inode);
if (!freespace_inode)
btrfs_lockdep_acquire(fs_info, btrfs_ordered_extent);
@@ -3345,8 +3348,9 @@ int btrfs_finish_one_ordered(struct btrfs_ordered_extent *ordered_extent)
goto out;
}
out:
- btrfs_clear_extent_bit(&inode->io_tree, start, end, clear_bits,
- &cached_state);
+ if (clear_bits)
+ btrfs_clear_extent_bit(&inode->io_tree, start, end, clear_bits,
+ &cached_state);
if (trans)
btrfs_end_transaction(trans);
--
2.43.0
Disclaimer: The contents of this e-mail message and any attachments are confidential and are intended solely for addressee. The information may also be legally privileged. This transmission is sent in trust, for the sole purpose of delivery to the intended recipient. If you have received this transmission in error, any use, reproduction or dissemination of this transmission is strictly prohibited. If you are not the intended recipient, please immediately notify the sender by reply e-mail or phone and delete this message and its attachments, if any.
next reply other threads:[~2026-03-30 3:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 3:31 Dave Chen [this message]
2026-04-07 11:23 ` [PATCH] btrfs: skip clearing EXTENT_DEFRAG for nocow ordered extents Filipe Manana
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=20260330033148.696942-1-davechen@synology.com \
--to=davechen@synology.com \
--cc=cccheng@synology.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=robbieko@synology.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