From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: some speedup with fiemap when leaves are shared
Date: Tue, 17 Jan 2023 11:21:37 +0000 [thread overview]
Message-ID: <cover.1673954069.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Add a couple assertions for the fiemap code that checks if extents are
shared and speedup the extent sharedness check when we already know the
current leaf is shared. More details on the changelogs.
Filipe Manana (2):
btrfs: assert commit root semaphore is held when accessing backref cache
btrfs: skip backref walking during fiemap if we know the leaf is shared
fs/btrfs/backref.c | 33 ++++++++++++++++++++++++++++++---
1 file changed, 30 insertions(+), 3 deletions(-)
--
2.35.1
next reply other threads:[~2023-01-17 11:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 11:21 fdmanana [this message]
2023-01-17 11:21 ` [PATCH 1/2] btrfs: assert commit root semaphore is held when accessing backref cache fdmanana
2023-01-17 12:34 ` Johannes Thumshirn
2023-01-17 11:21 ` [PATCH 2/2] btrfs: skip backref walking during fiemap if we know the leaf is shared fdmanana
2023-01-19 19:36 ` [PATCH 0/2] btrfs: some speedup with fiemap when leaves are shared 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.1673954069.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