From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/6] btrfs: some tweaks and cleanups around ordered extents
Date: Tue, 4 Jun 2024 12:08:46 +0100 [thread overview]
Message-ID: <cover.1717495660.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Details in the individual change logs.
Filipe Manana (6):
btrfs: reduce critical section at btrfs_wait_ordered_roots()
btrfs: reduce critical section at btrfs_wait_ordered_extents()
btrfs: add comment about locking to btrfs_split_ordered_extent()
btrfs: avoid removal and re-insertion of split ordered extent
btrfs: mark ordered extent insertion failure checks as unlikely
btrfs: update panic message when splitting ordered extent
fs/btrfs/ordered-data.c | 51 ++++++++++++++++++++++++-----------------
1 file changed, 30 insertions(+), 21 deletions(-)
--
2.43.0
next reply other threads:[~2024-06-04 11:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 11:08 fdmanana [this message]
2024-06-04 11:08 ` [PATCH 1/6] btrfs: reduce critical section at btrfs_wait_ordered_roots() fdmanana
2024-06-04 11:08 ` [PATCH 2/6] btrfs: reduce critical section at btrfs_wait_ordered_extents() fdmanana
2024-06-04 11:08 ` [PATCH 3/6] btrfs: add comment about locking to btrfs_split_ordered_extent() fdmanana
2024-06-04 11:08 ` [PATCH 4/6] btrfs: avoid removal and re-insertion of split ordered extent fdmanana
2024-06-04 11:08 ` [PATCH 5/6] btrfs: mark ordered extent insertion failure checks as unlikely fdmanana
2024-06-04 11:08 ` [PATCH 6/6] btrfs: update panic message when splitting ordered extent fdmanana
2024-06-04 16:02 ` [PATCH 0/6] btrfs: some tweaks and cleanups around ordered extents Josef Bacik
2024-06-04 22:50 ` Qu Wenruo
2024-06-05 7:35 ` Johannes Thumshirn
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.1717495660.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