From: Chris Mason <clm@fb.com>
To: Mark Fasheh <mfasheh@suse.de>
Cc: Stefan Priebe <s.priebe@profihost.ag>,
Qu Wenruo <quwenruo@cn.fujitsu.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
<jbacik@fb.com>
Subject: Re: Regression in: [PATCH 4/4] btrfs: qgroup: account shared subtree during snapshot delete
Date: Tue, 3 Nov 2015 21:22:10 -0500 [thread overview]
Message-ID: <20151104022210.GB16166@ret.masoncoding.com> (raw)
In-Reply-To: <20151103233115.GF15575@wotan.suse.de>
On Tue, Nov 03, 2015 at 03:31:15PM -0800, Mark Fasheh wrote:
> On Tue, Nov 03, 2015 at 08:42:33PM +0100, Stefan Priebe wrote:
> > Sorry don't know much about the btrfs internals.
> >
> > I just can reproduce this. Switching to a kernel with this patch and
> > without. With it takes ages - without it's super fast. I prooved
> > this several times by just rebooting to the other kernel.
>
> That's fine, disregard my previous e-mail - I just saw the mail Qu sent me.
> There's a problem in the code that the patch calls which is causing your
> performance issues. I'll CC you when I put out a fix.
Thanks Mark (and Qu), I'll get the fixed version into integration once
it is out.
-chris
next prev parent reply other threads:[~2015-11-04 2:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 20:49 Regression in: [PATCH 4/4] btrfs: qgroup: account shared subtree during snapshot delete Stefan Priebe
2015-11-01 22:57 ` Duncan
2015-11-02 1:34 ` Qu Wenruo
2015-11-02 5:46 ` Stefan Priebe
2015-11-03 19:15 ` Mark Fasheh
2015-11-03 19:26 ` Mark Fasheh
2015-11-03 19:42 ` Stefan Priebe
2015-11-03 23:31 ` Mark Fasheh
2015-11-04 2:22 ` Chris Mason [this message]
2015-11-04 1:01 ` Qu Wenruo
2015-11-05 19:23 ` Mark Fasheh
2015-11-06 1:02 ` Qu Wenruo
2015-11-06 3:15 ` Mark Fasheh
2015-11-06 3:25 ` 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=20151104022210.GB16166@ret.masoncoding.com \
--to=clm@fb.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mfasheh@suse.de \
--cc=quwenruo@cn.fujitsu.com \
--cc=s.priebe@profihost.ag \
/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).