From: Mike Galbraith <efault@gmx.de>
To: Chris Mason <chris.mason@fusionio.com>
Cc: "Chris L. Mason" <clmason@fusionio.com>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: 3.4.4-rt13: btrfs + xfstests 006 = BOOM.. and a bonus rt_mutex deadlock report for absolutely free!
Date: Mon, 16 Jul 2012 18:16:47 +0200 [thread overview]
Message-ID: <1342455407.7659.86.camel@marge.simpson.net> (raw)
In-Reply-To: <20120716154304.GG25961@shiny.int.fusionio.com>
On Mon, 2012-07-16 at 11:43 -0400, Chris Mason wrote:
> On Mon, Jul 16, 2012 at 04:55:44AM -0600, Mike Galbraith wrote:
> > Seems btrfs isn't entirely convinced either.
> >
> > [ 2292.336229] use_block_rsv: 1810 callbacks suppressed
> > [ 2292.336231] ------------[ cut here ]------------
> > [ 2292.336255] WARNING: at fs/btrfs/extent-tree.c:6344 use_block_rsv+0x17d/0x190 [btrfs]()
> > [ 2292.336257] Hardware name: System x3550 M3 -[7944K3G]-
> > [ 2292.336259] btrfs: block rsv returned -28
>
> This is unrelated. You got far enough into the benchmark to hit an
> ENOSPC warning. This can be ignored (I just deleted it when we used 3.0
> for oracle).
Ah great, thanks. I'll whack it in my tree as well then.
> re: dbench performance. dbench tends to penalize fairness. I can
> imagine RT making it slower in general.
It seems to work just fine for my normal workloads, and cyclictest is
happy, so I'm happy. Zillion threads is 'keep the pieces' to me ;-)
If you think the patch is ok as is, I'll go ahead and submit it after I
let dbench hammer on it overnight at least.
-Mike
next prev parent reply other threads:[~2012-07-16 17:45 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 5:47 Mike Galbraith
2012-07-12 8:44 ` Mike Galbraith
2012-07-12 9:53 ` Mike Galbraith
2012-07-12 11:43 ` Thomas Gleixner
2012-07-12 11:57 ` Mike Galbraith
2012-07-12 13:31 ` Thomas Gleixner
2012-07-12 13:37 ` Mike Galbraith
2012-07-12 13:43 ` Thomas Gleixner
2012-07-12 13:48 ` Mike Galbraith
2012-07-12 13:51 ` Mike Galbraith
2012-07-13 6:31 ` Mike Galbraith
2012-07-13 9:52 ` Thomas Gleixner
2012-07-13 10:14 ` Mike Galbraith
2012-07-13 10:26 ` Thomas Gleixner
2012-07-13 10:47 ` Chris Mason
2012-07-13 12:50 ` Mike Galbraith
2012-07-12 11:07 ` Thomas Gleixner
2012-07-12 17:09 ` Chris Mason
2012-07-13 10:04 ` Thomas Gleixner
2012-07-13 12:50 ` Chris Mason
2012-07-13 14:47 ` Thomas Gleixner
2012-07-14 10:14 ` Mike Galbraith
2012-07-15 17:56 ` Chris Mason
2012-07-16 2:02 ` Mike Galbraith
2012-07-16 16:02 ` Steven Rostedt
2012-07-16 16:26 ` Mike Galbraith
2012-07-16 16:35 ` Chris Mason
2012-07-16 16:36 ` Mike Galbraith
2012-07-16 17:03 ` Steven Rostedt
2012-07-17 4:18 ` Mike Galbraith
2012-07-17 4:27 ` Steven Rostedt
2012-07-17 4:34 ` Steven Rostedt
2012-07-17 4:46 ` Mike Galbraith
2012-07-17 4:44 ` Mike Galbraith
2012-07-17 12:54 ` Mike Galbraith
2012-07-16 10:55 ` Mike Galbraith
2012-07-16 15:43 ` Chris Mason
2012-07-16 16:16 ` Mike Galbraith [this message]
2012-07-14 13:38 ` Mike Galbraith
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=1342455407.7659.86.camel@marge.simpson.net \
--to=efault@gmx.de \
--cc=chris.mason@fusionio.com \
--cc=clmason@fusionio.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.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
Powered by JetHome