From: Alex Lyakas <alex.btrfs@zadarastorage.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 2/2] On a diff-send, avoid sending PREALLOC extent
Date: Mon, 21 Jan 2013 12:33:39 +0200 [thread overview]
Message-ID: <CAOcd+r14SSEBLkPoTapjSwxQhcGCmym3eeTDbUD_nso8RrhMJw@mail.gmail.com> (raw)
In-Reply-To: <20130114184529.GD1876@localhost.localdomain>
Hi Josef,
I have resent the patches. There are still some "please, no space
before tabs" warnings, which I am not sure how to correct, because I
don't see space before tab in that place. If there is still a problem,
can you please advise what is wrong.
Thanks,
Alex.
On Mon, Jan 14, 2013 at 8:45 PM, Josef Bacik <jbacik@fusionio.com> wrote:
> 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-21 10:33 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
2013-01-21 10:33 ` Alex Lyakas [this message]
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=CAOcd+r14SSEBLkPoTapjSwxQhcGCmym3eeTDbUD_nso8RrhMJw@mail.gmail.com \
--to=alex.btrfs@zadarastorage.com \
--cc=jbacik@fusionio.com \
--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;
as well as URLs for NNTP newsgroup(s).