From: Wang Shilong <wangshilong1991@gmail.com>
To: Josef Bacik <jbacik@fb.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2] Btrfs: do not use extent commit root for sending
Date: Tue, 28 Jan 2014 23:04:59 +0800 [thread overview]
Message-ID: <E11CE2B5-DBA8-470F-9929-2C2E6FBCDB59@gmail.com> (raw)
In-Reply-To: <52E7C09D.4020808@fb.com>
Hello Josef,
>
> On 01/14/2014 11:26 AM, Wang Shilong wrote:
>> From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
>>
>> Now we have kicked off transaction from btrfs send, it is not safe
>> that we use extent commit root to search.
>>
>> I happended to catch this problem when running sending and snapshot
>> in my desktop.
>
> I'm confused about this, we are searching a read only snapshot, why isn't looking at the commit root ok? Thanks,
I sent a patch to remove transaction outsize before.
http://git.kernel.org/cgit/linux/kernel/git/mason/linux-btrfs.git/commit/?h=integration&id=e0cbfccf3d518f1fb6f8e10932a67d75df2a4380
Previously, we can search extent commit root, it is because we are protected by join and end transaction, since this patch, we can not.
A further question is now we still have to join transaction actually, only the transaction protection range is smaller, but we may encounter
extent root's lock contention. I don't know which approach is better, the url's patch have been pushed into chris's integration branch before
i realized it would caused other problems.
Maybe a better a approach is to join and end transaction outsize of find_extent_clone(), and then we still can use extent commit
root for sending.^_^
Thanks,
Wang
>
> Josef
prev parent reply other threads:[~2014-01-28 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 16:26 [PATCH v2] Btrfs: do not use extent commit root for sending Wang Shilong
2014-01-14 16:26 ` [PATCH] Btrfs: fix wrong search path initialization before searching tree root Wang Shilong
2014-01-28 14:37 ` [PATCH v2] Btrfs: do not use extent commit root for sending Josef Bacik
2014-01-28 15:04 ` Wang Shilong [this message]
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=E11CE2B5-DBA8-470F-9929-2C2E6FBCDB59@gmail.com \
--to=wangshilong1991@gmail.com \
--cc=jbacik@fb.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).