All of lore.kernel.org
 help / color / mirror / Atom feed
From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs: some improvements around nocow checking
Date: Wed,  9 Jul 2025 21:20:27 +0100	[thread overview]
Message-ID: <cover.1752092303.git.fdmanana@suse.com> (raw)

From: Filipe Manana <fdmanana@suse.com>

Improve nocow write checking to avoid less iterations and less work when
doing buffered writes by checking multiple consecutive extents, plus a
couple cleanups.

Filipe Manana (3):
  btrfs: update function comment for btrfs_check_nocow_lock()
  btrfs: assert we can NOCOW the range in btrfs_truncate_block()
  btrfs: make btrfs_check_nocow_lock() check more than one extent

 fs/btrfs/file.c  | 43 +++++++++++++++++++++++++++++++++----------
 fs/btrfs/inode.c |  7 +++++--
 2 files changed, 38 insertions(+), 12 deletions(-)

-- 
2.47.2


             reply	other threads:[~2025-07-09 20:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 20:20 fdmanana [this message]
2025-07-09 20:20 ` [PATCH 1/3] btrfs: update function comment for btrfs_check_nocow_lock() fdmanana
2025-07-09 20:20 ` [PATCH 2/3] btrfs: assert we can NOCOW the range in btrfs_truncate_block() fdmanana
2025-07-09 20:20 ` [PATCH 3/3] btrfs: make btrfs_check_nocow_lock() check more than one extent fdmanana
2025-07-09 22:38 ` [PATCH 0/3] btrfs: some improvements around nocow checking Boris Burkov

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.1752092303.git.fdmanana@suse.com \
    --to=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 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.