From: Chris Mason <chris.mason@oracle.com>
To: rwheeler@redhat.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: still see locking issues...
Date: Thu, 31 Jul 2008 10:11:16 -0400 [thread overview]
Message-ID: <1217513476.20239.47.camel@think.oraclecorp.com> (raw)
In-Reply-To: <4891C236.3000604@redhat.com>
On Thu, 2008-07-31 at 09:46 -0400, Ric Wheeler wrote:
> Not sure if this is just an 8-way, multithreaded test, but my run of the
> latest unstable tree ground to a halt with lock messages (see the
> attached, compressed log for details ;-)) On the good news side, it did
> run for around 8 hours before the first message was logged.
I just merged Yan's missing hunks that might help explain this. At
least for fs_mark, you shouldn't really be hitting the throttling code
very often.
But, until I fully thread the allocator I can't completely get rid of
the stalls. That's one of the first things on my list for after v0.16
One of your procs is stuck in generic_unplug_device, and that one didn't
come from me ;) Sounds like the IO subsystem might be taking short
breaks as well.
-chris
next prev parent reply other threads:[~2008-07-31 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 19:29 [PATCH] initial version of reference cache Yan Zheng
2008-07-25 23:38 ` Chris Mason
2008-07-26 14:26 ` Yan Zheng
2008-07-28 15:09 ` Chris Mason
[not found] ` <f058a9c30807280952m2386aad4pa8a08ffaf930c370@mail.gmail.com>
2008-07-28 16:53 ` Miguel Sousa Filipe
2008-07-29 0:25 ` Chris Mason
[not found] ` <4891C236.3000604@redhat.com>
2008-07-31 14:11 ` Chris Mason [this message]
2008-07-31 14:37 ` still see locking issues Chris Mason
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=1217513476.20239.47.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rwheeler@redhat.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