| Message ID | cover.1708260967.git.fdmanana@suse.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | btrfs: some optimizations for send | expand |
On 2/19/24 06:59, fdmanana@kernel.org wrote: > 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(-) > For both: Reviewed-by: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
On Mon, Feb 19, 2024 at 11:59:29AM +0000, fdmanana@kernel.org wrote: > 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 Reviewed-by: David Sterba <dsterba@suse.com>
On Mon, Feb 19, 2024 at 11:59:29AM +0000, fdmanana@kernel.org wrote: > 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. > Reviewed-by: Josef Bacik <josef@toxicpanda.com> Thanks, Josef
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(-)