linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miao Xie <miaox@cn.fujitsu.com>
To: dsterba@suse.cz, chris.mason@fusionio.com,
	Stefan Behrens <sbehrens@giantdisaster.de>,
	linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: allocate the free space by the existed max extent size when ENOSPC
Date: Wed, 18 Sep 2013 12:04:30 +0800	[thread overview]
Message-ID: <5239264E.9080904@cn.fujitsu.com> (raw)
In-Reply-To: <20130917131312.GY6810@twin.jikos.cz>

On Tue, 17 Sep 2013 15:13:12 +0200, David Sterba wrote:
> On Mon, Sep 09, 2013 at 02:21:58PM +0800, Miao Xie wrote:
>> On fri, 06 Sep 2013 15:47:08 +0200, Stefan Behrens wrote:
>>> This patch makes the xfstest generic/256 lock up. It's quite
>>> reliably reproducible on one of my test boxes, and not at all
>>> visible on a second test box.
>>>
>>> And yes, I'm using the V2 patch although you haven't tagged it as V2
>>> in the subject line of the mail :)
>>
>> According to my debug, the machine was not locked up, it seems the
>> patch makes the test run very slow(90s ->850s on my machine).
> 
> The massive slowdown is present in current 3.12-rc code, which means V3
> did not make it into the pull.
> 
> Miao please send an incremental fix for rc2.

This patch has not been merged into 3.12-rc, so the above problem should be
introduced by other patch.

Thanks
Miao

> 
> thanks,
> david
> 


  reply	other threads:[~2013-09-18  4:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 10:35 [PATCH] Btrfs: allocate the free space by the existed max extent size when ENOSPC Miao Xie
2013-09-06 13:47 ` Stefan Behrens
2013-09-09  6:21   ` Miao Xie
2013-09-09  9:06     ` Stefan Behrens
2013-09-17 13:13     ` David Sterba
2013-09-18  4:04       ` Miao Xie [this message]
2013-09-20  9:25         ` David Sterba
2013-09-09  5:19 ` [PATCH v3] " Miao Xie
  -- strict thread matches above, loose matches on Subject: below --
2013-08-29  5:47 [PATCH] " Miao Xie
2013-08-29 12:45 ` David Sterba
2013-08-30 10:58   ` Miao Xie
2013-08-29 19:34 ` Josef Bacik

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=5239264E.9080904@cn.fujitsu.com \
    --to=miaox@cn.fujitsu.com \
    --cc=chris.mason@fusionio.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sbehrens@giantdisaster.de \
    /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).