From: Nick Piggin <npiggin@suse.de>
To: john stultz <johnstul@us.ibm.com>
Cc: paulmck@linux.vnet.ibm.com, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Darren Hart <dvhltc@us.ibm.com>,
Clark Williams <williams@redhat.com>,
Dinakar Guniguntala <dino@in.ibm.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: -rt dbench scalabiltiy issue
Date: Sun, 18 Oct 2009 01:06:54 +0200 [thread overview]
Message-ID: <20091017230654.GC29439@wotan.suse.de> (raw)
In-Reply-To: <1255743456.5135.162.camel@localhost.localdomain>
On Fri, Oct 16, 2009 at 06:37:36PM -0700, john stultz wrote:
> Additionally looking at the perf data, it does seem the dcache_lock is
> the contention point w/ ext2 on -rt13, but with Nick's patch, the
> contention still stays mostly in the dput/path_get functions. So it
> seems its just been moved rather then eased with _my port_ of Nick's
> patch (emphasis on "my port", since with nick's patch against mainline
> there is no regression at all.. I don't want to drag Nick's patches
> through the mud here :)
No there is nothing to suggest you've done the wrong thing. The dentry
refcounting issue was always a known one, and yes looking at the ext3
profiles, ext3/jbd is adding to the refcounting load so it is not
surprising that it has slowed down. Also -rt probably has more trouble
than mainline when you start hitting spinlock contention.
But before turning it back into an atomic, we need to see how far
the lock free path walking stuff goes (and that is not finished
yet either).
next prev parent reply other threads:[~2009-10-17 23:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 20:05 john stultz
2009-10-17 0:45 ` Paul E. McKenney
2009-10-17 1:03 ` john stultz
2009-10-17 1:37 ` john stultz
2009-10-17 23:06 ` Nick Piggin [this message]
2009-10-17 22:39 ` Nick Piggin
2009-11-18 1:28 ` john stultz
2009-11-18 4:25 ` Nick Piggin
2009-11-18 10:19 ` Thomas Gleixner
2009-11-18 10:52 ` Nick Piggin
2009-11-20 2:22 ` john stultz
2009-11-23 9:06 ` Nick Piggin
2009-11-25 2:16 ` john stultz
2009-11-25 7:18 ` Nick Piggin
2009-11-25 22:20 ` john stultz
2009-11-26 6:20 ` Nick Piggin
2009-12-02 1:53 ` john stultz
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=20091017230654.GC29439@wotan.suse.de \
--to=npiggin@suse.de \
--cc=dino@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=williams@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
all inboxes | Powered by JetHome®