From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3] btrfs: Delay block group auto removal to avoid interfering qgroups
Date: Tue, 29 May 2018 18:17:35 +0200 [thread overview]
Message-ID: <20180529161735.GD4325@twin.jikos.cz> (raw)
In-Reply-To: <20180528092009.32562-1-wqu@suse.com>
On Mon, May 28, 2018 at 05:20:06PM +0800, Qu Wenruo wrote:
> The patchset can be fetched from github:
> https://github.com/adam900710/linux/tree/delayed_bg_removal
>
> It's based on v4.17-rc5 branch.
Please refresh the patches on top of today's misc-next. The patch 2/3
has been there already and now is deleted as it conflicts with 1/3, so
I'm going to apply them in the order as they are in this pathset.
Patch 3/3 is nontrivial and I'd like to have a closer look at the bg
tracking and locking, 1 and 2 can go to misc-next now.
next prev parent reply other threads:[~2018-05-29 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 9:20 [PATCH 0/3] btrfs: Delay block group auto removal to avoid interfering qgroups Qu Wenruo
2018-05-28 9:20 ` [PATCH 1/3] btrfs: trace: Add trace points for unused block groups Qu Wenruo
2018-05-28 9:20 ` [PATCH 2/3] btrfs: Use btrfs_mark_bg_unused() to replace open code Qu Wenruo
2018-05-28 21:45 ` Nikolay Borisov
2018-05-28 9:20 ` [PATCH 3/3] btrfs: Delayed empty block group auto removal to next transaction Qu Wenruo
2018-05-29 6:20 ` Nikolay Borisov
2018-05-29 6:30 ` Qu Wenruo
2018-05-29 16:17 ` David Sterba [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-28 6:58 [PATCH 0/3] btrfs: Delay block group auto removal to avoid interfering qgroups Qu Wenruo
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=20180529161735.GD4325@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@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 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.