From: Josef Bacik <jbacik@fusionio.com>
To: Alex Lyakas <alex.btrfs@zadarastorage.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Josef Bacik <JBacik@fusionio.com>,
Alexander Block <ablock84@googlemail.com>,
Jan Schmidt <list.btrfs@jan-o-sch.net>,
Chen Yang <chenyang.fnst@cn.fujitsu.com>,
Arne Jansen <sensille@gmx.net>
Subject: Re: [PATCH 1/2] V2 Avoid sending disknr==0 extents when possible.
Date: Thu, 24 Jan 2013 10:48:41 -0500 [thread overview]
Message-ID: <20130124154841.GD2349@localhost.localdomain> (raw)
In-Reply-To: <CAOcd+r1_hiz7A98r0o1e_=60+3tN16n+HTgQs0SgMhHjGG-E7Q@mail.gmail.com>
On Mon, Jan 21, 2013 at 03:27:22AM -0700, Alex Lyakas wrote:
> In the following cases we do not send disknr==0 extents:
> 1) full send 2) new inode in a diff-send 3) when disknr==0 extents are
> added to the end of an inode
>
> Original-version-by: Chen Yang <chenyang.fnst@cn.fujitsu.com>
> Signed-off-by: Alex Lyakas <alex@zadarastorage.com>
Neither of these would apply to btrfs-next, please rebase against btrfs-next and
resend. Thanks,
Josef
next prev parent reply other threads:[~2013-01-24 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 10:22 [PATCH 0/2] send: Avoid sending disknr==0 and PREALLOC extents when possible V2 Alex Lyakas
2013-01-21 10:27 ` [PATCH 1/2] V2 Avoid sending disknr==0 extents when possible Alex Lyakas
2013-01-24 15:48 ` Josef Bacik [this message]
2013-01-21 10:30 ` [PATCH 2/2] V2 On a diff-send, avoid sending PREALLOC extents Alex Lyakas
-- strict thread matches above, loose matches on Subject: below --
2013-01-28 17:03 [PATCH 1/2] V2 Avoid sending disknr==0 extents when possible 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=20130124154841.GD2349@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=ablock84@googlemail.com \
--cc=alex.btrfs@zadarastorage.com \
--cc=chenyang.fnst@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox