From: Chris Mason <chris.mason@oracle.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: 2.6.32-rc1: btrfs hugs
Date: Fri, 2 Oct 2009 14:37:48 -0400 [thread overview]
Message-ID: <20091002183748.GJ2881@think> (raw)
In-Reply-To: <a4423d670910020418w4de348c7x763bb7d548d927ef@mail.gmail.com>
On Fri, Oct 02, 2009 at 03:18:41PM +0400, Alexander Beregalov wrote:
> Hi
> The kernel is 2.6.32-rc2-00196-g0efe5e3
> SMP, 4cpus
>
> I tested dbench with 150 threads on 120G partition.
>
>
> device fsid b467c30bdb79768-7e6f9a05192ee4b5 devid 1 transid 7 /dev/sda3
> thread pool is 6
I think I've tracked this down to the helper threads getting stuck
waiting for ram to start more helper threads. I've got a fixed version
here that I'm testing and should push out for 2.6.32-rc3.
-chris
prev parent reply other threads:[~2009-10-02 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 11:18 2.6.32-rc1: btrfs hugs Alexander Beregalov
2009-10-02 18:37 ` Chris Mason [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=20091002183748.GJ2881@think \
--to=chris.mason@oracle.com \
--cc=a.beregalov@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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