From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v7 0/3] btrfs: allow btrfs_truncate_block() to fallback to nocow for data space reservation
Date: Sun, 28 Jun 2020 19:39:28 +0800 [thread overview]
Message-ID: <20200628113931.26576-1-wqu@suse.com> (raw)
Before this patch, btrfs_truncate_block() never checks the NODATACOW
bit, thus when we run out of data space, we can return ENOSPC for
truncate for NODATACOW inode.
This patchset will address this problem by doing the same behavior as
buffered write to address it.
Changelog:
v2:
- Rebased to misc-next
Only one minor conflict in ctree.h
v3:
- Added two new patches
- Refactor check_can_nocow()
Since the introduction of nowait, check_can_nocow() are in fact split
into two usage patterns: check_can_nocow(nowait = false) with
btrfs_drew_write_unlock(), and single check_can_nocow(nowait = true).
Refactor them into two functions: start_nocow_check() paired with
end_nocow_check(), and single try_nocow_check(). With comment added.
- Rebased to latest misc-next
- Added btrfs_assert_drew_write_locked() for btrfs_end_nocow_check()
This is a little concerning one, as it's in the hot path of buffered
write.
It has percpu_counter_sum() called in that hot path, causing
obvious performance drop for CONFIG_BTRFS_DEBUG build.
Not sure if the assert is worthy since there aren't any other users.
v4:
- Rebased to latest misc-next
- Comment update to follow the relaxed kernel-doc format
- Re-order the patches
So the fix comes first, then refactors.
- Naming updates for the refactor patch
Now the exported pair is btrfs_check_nocow_lock() and
btrfs_check_nocow_unlock().
- Remove the btrfs_assert_drew_write_lock()
It's extremely slow for btrfs/187, and we only have two call sites so
far, thus it's not really worthy.
v5:
- Fix a stupid bug that check_nocow_nolock() passes wrong bool
- Update the comment for btrfs_check_nocow_lock() as there is no
"nowait" parameter anymore
v6:
- Replace one btrfs_drew_write_unlock() with the wrapper
v7:
- Fix a "BTRF_I()" typo
Reported-by: kernel test robot <lkp@intel.com>
Qu Wenruo (3):
btrfs: allow btrfs_truncate_block() to fallback to nocow for data
space reservation
btrfs: add comments for btrfs_check_can_nocow() and can_nocow_extent()
btrfs: refactor btrfs_check_can_nocow() into two variants
fs/btrfs/ctree.h | 3 +++
fs/btrfs/file.c | 61 +++++++++++++++++++++++++++++++++++-----------
fs/btrfs/inode.c | 63 +++++++++++++++++++++++++++++++++++++++++-------
3 files changed, 104 insertions(+), 23 deletions(-)
--
2.27.0
next reply other threads:[~2020-06-28 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 11:39 Qu Wenruo [this message]
2020-06-28 11:39 ` [PATCH v7 1/3] btrfs: allow btrfs_truncate_block() to fallback to nocow for data space reservation Qu Wenruo
2020-06-28 11:39 ` [PATCH v7 2/3] btrfs: add comments for btrfs_check_can_nocow() and can_nocow_extent() Qu Wenruo
2020-06-28 11:39 ` [PATCH v7 3/3] btrfs: refactor btrfs_check_can_nocow() into two variants Qu Wenruo
2020-06-29 15:40 ` [PATCH v7 0/3] btrfs: allow btrfs_truncate_block() to fallback to nocow for data space reservation David Sterba
2020-06-29 17:09 ` 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=20200628113931.26576-1-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.