From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: some optimizations for send
Date: Mon, 19 Feb 2024 11:59:29 +0000 [thread overview]
Message-ID: <cover.1708260967.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
The following are two optimizations for send, one to avoid sending
unnecessary holes (writes full of zeros), which can waste a lot of space
at the receiver and increase stream size for cases where sparse files are
used, such as images of thin provisioned filesystems for example as
recently reported by a user. The second is just a small optimization to
avoid repeating a btree search. More details in the respective change logs.
Filipe Manana (2):
btrfs: send: don't issue unnecessary zero writes for trailing hole
btrfs: send: avoid duplicated search for last extent when sending hole
fs/btrfs/send.c | 44 +++++++++++++++++++++++++-------------------
1 file changed, 25 insertions(+), 19 deletions(-)
--
2.40.1
next reply other threads:[~2024-02-19 11:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 11:59 fdmanana [this message]
2024-02-19 11:59 ` [PATCH 1/2] btrfs: send: don't issue unnecessary zero writes for trailing hole fdmanana
2024-02-19 11:59 ` [PATCH 2/2] btrfs: send: avoid duplicated search for last extent when sending hole fdmanana
2024-02-19 19:00 ` [PATCH 0/2] btrfs: some optimizations for send Sweet Tea Dorminy
2024-02-19 19:10 ` David Sterba
2024-02-20 15:21 ` Josef Bacik
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.1708260967.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