From: Phillip Susi <psusi@cfl.rr.com>
To: Liu Bo <liubo2009@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: understanding the tree-log
Date: Fri, 04 Nov 2011 09:35:00 -0400 [thread overview]
Message-ID: <4EB3EA04.3000903@cfl.rr.com> (raw)
In-Reply-To: <4EB3739B.4030204@cn.fujitsu.com>
On 11/4/2011 1:09 AM, Liu Bo wrote:
> Btrfs has an expensive "commit transaction", if we commit a transaction every time we fsync,
> the performance is not that good. Instead of this, we introduce a write-ahead log to make
> our fsync faster.
>
> So if you do fsync for your data, it means your data is safely in the log tree,
> then if a crash takes place, the data can be recovered from log.
How can you write to the log tree without a full commit? The tree of
tree roots has to point to the root node of the log tree, so when you
write out the log tree, that needs updated too, which requires a full
commit doesn't it?
prev parent reply other threads:[~2011-11-04 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 3:21 understanding the tree-log Phillip Susi
2011-11-04 5:09 ` Liu Bo
2011-11-04 13:35 ` Phillip Susi [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=4EB3EA04.3000903@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=liubo2009@cn.fujitsu.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 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).