From: David Sterba <dsterba@suse.cz>
To: Mark Fasheh <mfasheh@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3] Relocation/backref cache cleanups
Date: Wed, 2 Oct 2019 14:58:55 +0200 [thread overview]
Message-ID: <20191002125855.GM2751@twin.jikos.cz> (raw)
In-Reply-To: <20190906171533.618-1-mfasheh@suse.com>
On Fri, Sep 06, 2019 at 10:15:30AM -0700, Mark Fasheh wrote:
> Hi,
>
> Relocation caches extent backrefs in an rbtree (the 'backref cache'). The
> following patches move the backref cache code out of relocation.c and into
> it's own file. We then do a straight-forward cleanup the main backref cache
> function, build_backref_tree(). No functionality is changed in these
> patches.
>
> These patches are part of a larger series I have, which speeds up qgroup
> accounting by using the same backref cache facility. That series is not
> quite ready, however I wanted to see about getting these cleanup patches
> upstreamed as they are nicely self contained and benefit the readability of
> the code.
Patches 1-3 moved to misc-next.
next prev parent reply other threads:[~2019-10-02 12:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 17:15 [PATCH 0/3] Relocation/backref cache cleanups Mark Fasheh
2019-09-06 17:15 ` [PATCH 1/3] btrfs: Move backref cache code out of relocation.c Mark Fasheh
2019-09-11 16:08 ` Josef Bacik
2019-09-27 14:43 ` David Sterba
2019-09-06 17:15 ` [PATCH 2/3] btrfs: move ref finding machinery out of build_backref_tree() Mark Fasheh
2019-09-11 16:09 ` Josef Bacik
2019-09-24 14:49 ` David Sterba
2019-09-26 11:07 ` Josef Bacik
2019-09-06 17:15 ` [PATCH 3/3] btrfs: move useless node processing out of build_backref_cache Mark Fasheh
2019-09-11 16:11 ` Josef Bacik
2019-10-02 12:58 ` David Sterba [this message]
2019-10-07 15:18 ` [PATCH 0/3] Relocation/backref cache cleanups David Sterba
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=20191002125855.GM2751@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=mfasheh@suse.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).