Re: [PATCH 0/2] send: Avoid sending disknr==0 and PREALLOC extents when possible V3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Josef,
is there still an issue with applying the patch?

Thanks,
Alex.


On Mon, Jan 28, 2013 at 7:01 PM, Alex Lyakas
<alex.btrfs@xxxxxxxxxxxxxxxxx> wrote:
> These two patches address the issue of sending unneeded zero data for
> disknr==0 and PREALLOC extents.
> There is room for additional improvement for PREALLOC extents, but it
> requires adding a new send command, so for now this is not addressed.
>
> Changes in V2: no functional change; previous patchset was malformed,
> so cleanup done with checkpatch.pl.
> Changes in V3: rebased against btrfs-next
>
> Alex Lyakas (2):
>   Avoid sending disknr==0 extents when possible.
>   On a diff-send, avoid sending PREALLOC extents, if the     parent
>     root has only PREALLOC extents on an appropriate     file range.
>
>  fs/btrfs/send.c |  184 +++++++++++++++++++++++++++++++++++++++++++++++++++++--
>  1 file changed, 178 insertions(+), 6 deletions(-)
>
> --
> 1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux