From: Marat Khalili <mkh@rqc.ru>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [RFC] Improve subvolume usability for a normal user
Date: Thu, 7 Dec 2017 10:32:21 +0300 [thread overview]
Message-ID: <47becabf-e362-c552-1b19-44d30e5c4e62@rqc.ru> (raw)
In-Reply-To: <9aa28872-5a44-5a81-d954-656b2f956033@gmx.com>
On 07/12/17 08:27, Qu Wenruo wrote:
> When doing snapshot, btrfs only needs to increase reference of 2nd
> highest level tree blocks of original snapshot, other than "walking the
> tree".
> (If tree root level is 2, then level 2 node is copied, while all
> reference of level 1 tree blocks get increased)
Out of curiosity, how does it interacts with nocow files? Does every
write to these files involves backref walk?
--
With Best Regards,
Marat Khalili
next prev parent reply other threads:[~2017-12-07 7:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 8:25 [RFC] Improve subvolume usability for a normal user Misono, Tomohiro
2017-12-05 8:43 ` Qu Wenruo
2017-12-05 12:41 ` Austin S. Hemmelgarn
2017-12-05 15:42 ` Graham Cobb
2017-12-05 18:01 ` Goffredo Baroncelli
2017-12-05 18:46 ` Graham Cobb
2017-12-05 19:09 ` Goffredo Baroncelli
2017-12-05 20:17 ` Austin S. Hemmelgarn
2017-12-05 22:08 ` Goffredo Baroncelli
2017-12-06 12:25 ` Austin S. Hemmelgarn
2017-12-06 4:52 ` Misono, Tomohiro
2017-12-06 12:39 ` Austin S. Hemmelgarn
2017-12-07 2:56 ` Duncan
2017-12-07 7:15 ` Misono, Tomohiro
2017-12-07 11:55 ` Duncan
2017-12-07 12:21 ` Austin S. Hemmelgarn
2017-12-07 13:45 ` Hugo Mills
2017-12-07 5:27 ` Qu Wenruo
2017-12-07 7:32 ` Marat Khalili [this message]
2017-12-07 7:59 ` Qu Wenruo
2017-12-05 18:24 ` Goffredo Baroncelli
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=47becabf-e362-c552-1b19-44d30e5c4e62@rqc.ru \
--to=mkh@rqc.ru \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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.