From: tytso@mit.edu
To: "Chen, Tim C" <tim.c.chen@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
john stultz <johnstul@us.ibm.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Mingming Cao <cmm@us.ibm.com>,
keith maanthey <kmannth@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Darren Hart <dvhltc@us.ibm.com>
Subject: Re: ext4 dbench performance with CONFIG_PREEMPT_RT
Date: Sat, 10 Apr 2010 07:58:16 -0400 [thread overview]
Message-ID: <20100410115816.GH1849@thunk.org> (raw)
In-Reply-To: <EA929A9653AAE14F841771FB1DE5A1365FE4FCD4BC@rrsmsx501.amr.corp.intel.com>
On Fri, Apr 09, 2010 at 05:48:23PM -0600, Chen, Tim C wrote:
>
> Your patch did remove the contention on the j_state_lock for dbench
> in my testing with 64 threads. The contention point now
> moves dcache_lock, which is also another tricky bottleneck.
>
> In our other testing with FFSB that creates/rename/remove a lot of directories,
> we found that journal->j_revoke_lock was also heavily contended.
>
Do you have lock_stat reports handy? I'd love to take a look at them.
Thanks,
- Ted
next prev parent reply other threads:[~2010-04-10 11:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 23:21 ext4 dbench performance with CONFIG_PREEMPT_RT john stultz
2010-04-08 3:46 ` tytso
2010-04-08 10:18 ` Theodore Tso
2010-04-08 20:41 ` john stultz
2010-04-08 21:10 ` tytso
2010-04-13 3:52 ` john stultz
2010-04-14 3:04 ` john stultz
2010-04-08 22:37 ` Mingming Cao
2010-04-12 19:46 ` Jan Kara
2010-04-13 14:52 ` tytso
2010-04-13 16:25 ` Darren Hart
2010-06-02 22:35 ` j_state_lock patch data (was: Re: ext4 dbench performance with CONFIG_PREEMPT_RT) Eric Whitney
2010-04-09 15:49 ` ext4 dbench performance with CONFIG_PREEMPT_RT Andi Kleen
2010-04-09 23:33 ` tytso
2010-04-09 23:48 ` Chen, Tim C
2010-04-09 23:57 ` john stultz
2010-04-10 11:58 ` tytso [this message]
2010-04-12 19:54 ` Chen, Tim C
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=20100410115816.GH1849@thunk.org \
--to=tytso@mit.edu \
--cc=andi@firstfloor.org \
--cc=cmm@us.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=johnstul@us.ibm.com \
--cc=kmannth@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@intel.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;
as well as URLs for NNTP newsgroup(s).