From: Josef Bacik <jbacik@fusionio.com>
To: Alex Lyakas <alex.btrfs@zadarastorage.com>
Cc: Alexander Block <ablock84@googlemail.com>,
Jan Schmidt <list.btrfs@jan-o-sch.net>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Arne Jansen <sensille@gmx.net>
Subject: Re: [PATCH 2/2] On a diff-send, avoid sending PREALLOC extent
Date: Mon, 14 Jan 2013 13:45:29 -0500 [thread overview]
Message-ID: <20130114184529.GD1876@localhost.localdomain> (raw)
In-Reply-To: <CAOcd+r1ZioBQEykibvDdfx-1gmLfUPFfodNK5Dhnv8OB0EFApw@mail.gmail.com>
On Wed, Jan 09, 2013 at 10:41:10AM -0700, Alex Lyakas wrote:
> Subject: [PATCH 2/2] On a diff-send, avoid sending PREALLOC extents, if the
> parent root has only PREALLOC extents on an appropriate
> file range.
>
> This does not fully avoids sending PREALLOC extents, because on full-send or
> new inode we need a new send command to do that. But this patch improves
> the situation by handling diff-sends.
>
> Signed-off-by: Alex Lyakas <alex.btrfs@zadarastorage.com>
> ---
Malformed patch and it confused patchwork, please resend. Thanks,
Josef
next prev parent reply other threads:[~2013-01-14 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 17:37 [PATCH 0/2] send: Avoid sending disknr==0 and PREALLOC extents when possible Alex Lyakas
2013-01-09 17:39 ` [PATCH 1/2] Avoid sending disknr==0 " Alex Lyakas
2013-01-09 17:41 ` [PATCH 2/2] On a diff-send, avoid sending PREALLOC extent Alex Lyakas
2013-01-14 18:45 ` Josef Bacik [this message]
2013-01-21 10:33 ` Alex Lyakas
2013-01-10 3:25 ` [PATCH 0/2] send: Avoid sending disknr==0 and PREALLOC extents when possible Chen Yang
2013-01-10 8:46 ` Alex Lyakas
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=20130114184529.GD1876@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=ablock84@googlemail.com \
--cc=alex.btrfs@zadarastorage.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
--cc=sensille@gmx.net \
/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.