From: Marc MERLIN <marc@merlins.org>
To: Filipe David Borba Manana <fdmanana@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [RFC PATCH] Btrfs: send, add calculate data size flag to allow for progress estimation
Date: Sat, 5 Apr 2014 17:18:38 -0700 [thread overview]
Message-ID: <20140406001838.GA9485@merlins.org> (raw)
In-Reply-To: <1396624841-1363-1-git-send-email-fdmanana@gmail.com>
On Fri, Apr 04, 2014 at 04:20:41PM +0100, Filipe David Borba Manana wrote:
> This new send flag makes send calculate first the amount of new file data (in bytes)
> the send root has relatively to the parent root, or for the case of a non-incremental
> send, the total amount of file data we will send through the send stream. In other words,
> it computes the sum of the lengths of all write and clone operations that will be sent
> through the send stream.
Thanks for this patch, much appreciated.
A few questions:
1) I tried to apply to 3.14.0, and it all applied except one line:
--- fs/btrfs/send.c
+++ fs/btrfs/send.c
@@ -3091,6 +3121,8 @@
int ret;
u64 ancestor = 0;
+ ASSERT(sctx->phase != SEND_PHASE_COMPUTE_DATA_SIZE);
+
name = fs_path_alloc();
from_path = fs_path_alloc();
if (!name || !from_path) {
I looked around and found nothing that looked similar enough.
Obviously it's an assert, so I can run without it, but my source being
very different from yours just made me want to check that this was most
likely ok to run with 3.14.0.
2) I saw the concerns about protocol incompatibility. Is it an issue if you run without -o
too?
3) Do you have a patch for btrfs-tools so that I can try it, or a git
tree of btrfs-tools with this that I should pull?
4) Can I run btrfs send -o snap1 snap2 >/dev/null to get quick stats
on the changes between the 2 snapshots, or is it still going to walk
through all the data blocks and send them to /dev/null afterwards?
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2014-04-06 0:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 15:20 [RFC PATCH] Btrfs: send, add calculate data size flag to allow for progress estimation Filipe David Borba Manana
2014-04-04 14:52 ` Konstantinos Skarlatos
2014-04-04 15:59 ` Filipe David Manana
2014-04-04 15:53 ` David Sterba
2014-04-04 16:01 ` Filipe David Manana
2014-04-04 16:32 ` David Sterba
2014-04-06 0:18 ` Marc MERLIN [this message]
2014-04-06 16:57 ` Filipe David Manana
2014-04-06 17:20 ` Marc MERLIN
2014-04-07 15:25 ` Josef Bacik
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=20140406001838.GA9485@merlins.org \
--to=marc@merlins.org \
--cc=fdmanana@gmail.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).