From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/8] btrfs: some speedups around nowait dio
Date: Wed, 23 Mar 2022 16:19:22 +0000 [thread overview]
Message-ID: <cover.1648051582.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
This patchset makes our direct IO code behave better for NOWAIT writes,
avoiding blocking in several places for potentially long periods due to
waits for IO. It also removes running the same nocow checks twice (which
can be expensive) and doing extra path allocations. The last patch in
the series has a test and the results I got before and after applying
this patchset.
Filipe Manana (8):
btrfs: avoid blocking on page locks with nowait dio on compressed range
btrfs: avoid blocking nowait dio when locking file range
btrfs: avoid double nocow check when doing nowait dio writes
btrfs: stop allocating a path when checking if cross reference exists
btrfs: free path at can_nocow_extent() before checking for checksum items
btrfs: release path earlier at can_nocow_extent()
btrfs: avoid blocking when allocating context for nowait dio read/write
btrfs: avoid blocking on space revervation when doing nowait dio writes
fs/btrfs/ctree.h | 5 +-
fs/btrfs/delalloc-space.c | 9 +--
fs/btrfs/extent-tree.c | 9 +--
fs/btrfs/file.c | 104 +++++++++++-----------------------
fs/btrfs/inode.c | 116 ++++++++++++++++++++++++++++----------
fs/btrfs/qgroup.c | 5 +-
fs/btrfs/qgroup.h | 12 ++--
fs/btrfs/relocation.c | 3 +-
fs/btrfs/root-tree.c | 3 +-
9 files changed, 144 insertions(+), 122 deletions(-)
--
2.33.0
next reply other threads:[~2022-03-23 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 16:19 fdmanana [this message]
2022-03-23 16:19 ` [PATCH 1/8] btrfs: avoid blocking on page locks with nowait dio on compressed range fdmanana
2022-03-23 16:19 ` [PATCH 2/8] btrfs: avoid blocking nowait dio when locking file range fdmanana
2022-03-23 16:19 ` [PATCH 3/8] btrfs: avoid double nocow check when doing nowait dio writes fdmanana
2022-03-23 16:19 ` [PATCH 4/8] btrfs: stop allocating a path when checking if cross reference exists fdmanana
2022-03-23 16:19 ` [PATCH 5/8] btrfs: free path at can_nocow_extent() before checking for checksum items fdmanana
2022-03-23 16:19 ` [PATCH 6/8] btrfs: release path earlier at can_nocow_extent() fdmanana
2022-03-23 16:19 ` [PATCH 7/8] btrfs: avoid blocking when allocating context for nowait dio read/write fdmanana
2022-03-23 16:19 ` [PATCH 8/8] btrfs: avoid blocking on space revervation when doing nowait dio writes fdmanana
2022-03-25 20:34 ` [PATCH 0/8] btrfs: some speedups around nowait dio 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.1648051582.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