From: Josef Bacik <jbacik@fb.com>
To: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: separate out the extent root update
Date: Tue, 16 Dec 2014 15:16:33 -0500 [thread overview]
Message-ID: <54909321.3050000@fb.com> (raw)
In-Reply-To: <1418418077-1223-1-git-send-email-jbacik@fb.com>
On 12/12/2014 04:01 PM, Josef Bacik wrote:
> Depending on where the extent root shows up in the dirty list we could end up
> recowing the extent root a few times during commit. This is inefficient, so
> instead only track the other COW only roots and update them all at once, and
> then do the extent root/block group update loop by itself to try and reduce the
> amount of churn we do at commit time. Thanks,
>
Killing this one as well. Thanks,
Josef
prev parent reply other threads:[~2014-12-16 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 21:01 [PATCH] Btrfs: separate out the extent root update Josef Bacik
2014-12-16 20:16 ` Josef Bacik [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=54909321.3050000@fb.com \
--to=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 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.