Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Mark Fasheh <mfasheh@suse.de>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.com>,
	Josef Bacik <jbacik@fb.com>
Subject: Re: [PATCH] Improve balance performance when qgroups are turned on
Date: Tue, 31 May 2016 22:38:00 -0700	[thread overview]
Message-ID: <20160601053800.GE7633@wotan.suse.de> (raw)
In-Reply-To: <32fe4f1d-0ad8-da6f-ccca-becd551b4bee@cn.fujitsu.com>

On Wed, Jun 01, 2016 at 09:31:14AM +0800, Qu Wenruo wrote:
> Thanks for the test case.
> It would be better if you could submit a test case for it.

Yeah I'll handle this.


> Reproduced the problem. I'll track it down.
> Seems to be related with metadata.

Thanks, please CC me on any patches.
	--Mark

--
Mark Fasheh

      reply	other threads:[~2016-06-01  5:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-27  0:18 [PATCH] Improve balance performance when qgroups are turned on Mark Fasheh
2016-05-30  7:48 ` Qu Wenruo
2016-06-01  0:50   ` Mark Fasheh
2016-06-01  1:31     ` Qu Wenruo
2016-06-01  5:38       ` Mark Fasheh [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=20160601053800.GE7633@wotan.suse.de \
    --to=mfasheh@suse.de \
    --cc=dsterba@suse.com \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo@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