From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: some refactor and cleanup for NOCOW write paths
Date: Wed, 30 Mar 2022 15:31:05 +0100 [thread overview]
Message-ID: <cover.1648650280.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
This refactors some duplicated NOCOW checks into a single helper function,
plus it removes some no longer needed logic. This came out some in progress
work on the NOCOW paths, but has it's fairly indepedent of that work, it
is being sent out in a separate patchset.
Filipe Manana (2):
btrfs: move common NOCOW checks against a file extent into a helper
btrfs: do not test for free space inode during NOCOW check against
file extent
fs/btrfs/inode.c | 428 ++++++++++++++++++++++++-----------------------
1 file changed, 216 insertions(+), 212 deletions(-)
--
2.33.0
next reply other threads:[~2022-03-30 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 14:31 fdmanana [this message]
2022-03-30 14:31 ` [PATCH 1/2] btrfs: move common NOCOW checks against a file extent into a helper fdmanana
2022-03-30 14:31 ` [PATCH 2/2] btrfs: do not test for free space inode during NOCOW check against file extent fdmanana
2022-03-31 18:14 ` [PATCH 0/2] btrfs: some refactor and cleanup for NOCOW write paths David Sterba
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.1648650280.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox