From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/6] btrfs: some minor improvements and cleanups mostly around extent logging
Date: Thu, 3 Feb 2022 14:55:44 +0000 [thread overview]
Message-ID: <cover.1643898312.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
This is a mix of small improvements around logging extents, replacing
extents in a log tree or subvolume tree, while others are more generic
ones, and some cleanups. They are grouped in the same patchset, but they
are all independent of each other.
Filipe Manana (6):
btrfs: remove unnecessary leaf free space checks when pushing items
btrfs: avoid unnecessary COW of leaves when deleting items from a leaf
btrfs: avoid unnecessary computation when deleting items from a leaf
btrfs: remove constraint on number of visited leaves when replacing extents
btrfs: remove useless path release in the fast fsync path
btrfs: prepare extents to be logged before locking a log tree path
fs/btrfs/ctree.c | 66 ++++++++++++++++++++++++++-------------------
fs/btrfs/file.c | 5 +---
fs/btrfs/tree-log.c | 65 +++++++++++++++++++-------------------------
3 files changed, 67 insertions(+), 69 deletions(-)
--
2.33.0
next reply other threads:[~2022-02-03 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 14:55 fdmanana [this message]
2022-02-03 14:55 ` [PATCH 1/6] btrfs: remove unnecessary leaf free space checks when pushing items fdmanana
2022-02-03 14:55 ` [PATCH 2/6] btrfs: avoid unnecessary COW of leaves when deleting items from a leaf fdmanana
2022-02-03 14:55 ` [PATCH 3/6] btrfs: avoid unnecessary computation " fdmanana
2022-02-03 14:55 ` [PATCH 4/6] btrfs: remove constraint on number of visited leaves when replacing extents fdmanana
2022-02-03 14:55 ` [PATCH 5/6] btrfs: remove useless path release in the fast fsync path fdmanana
2022-02-03 14:55 ` [PATCH 6/6] btrfs: prepare extents to be logged before locking a log tree path fdmanana
2022-02-04 16:36 ` [PATCH 0/6] btrfs: some minor improvements and cleanups mostly around extent logging David Sterba
2022-02-08 15:44 ` 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.1643898312.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 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.