mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: john stultz <johnstul@us.ibm.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>,
	Darren Hart <dvhltc@us.ibm.com>,
	Clark Williams <williams@redhat.com>,
	"Paul E. McKenney" <paulmck@us.ibm.com>,
	Dinakar Guniguntala <dino@in.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	cmm@us.ibm.com
Subject: Re: -rt dbench scalabiltiy issue
Date: Thu, 26 Nov 2009 07:20:20 +0100	[thread overview]
Message-ID: <20091126062020.GH17484@wotan.suse.de> (raw)
In-Reply-To: <1259187633.3585.31.camel@localhost.localdomain>

On Wed, Nov 25, 2009 at 02:20:33PM -0800, john stultz wrote:
> On Wed, 2009-11-25 at 08:18 +0100, Nick Piggin wrote:
> > If you're using acls or something on ext2 then lock free path walk
> > might fail more often.
> 
> CC'ed Ted and Mingming as they might be interested:
> 
> Got ext4 data up:
> http://sr71.net/~jstultz/dbench-scalability/graphs/ext4-scalability.png

Ahh, looks much nicer than ext3, at least on non-rt. -rt seems to
be running into journal lock contention.

 
> Looks pretty similar to ext2. I'm also seeing path_get contention as
> well with your patch on ext4 in the perflogs:
> http://sr71.net/~jstultz/dbench-scalability/perflogs/2.6.32-rc7-nick.ext4.perflog

That's *all* coming from reading /proc/mounts by the looks. I don't
think we're going to bother trying to make d_path incredibly scalable,
the fix is to fix glibc's statvfs call.

As I said, you can work around this by changing dbench's statvfs call
to statfs.

After that, the same journal locks look like they might hit next, but
it should get quite a lot further.


> > Anyway, I think all these problems should largely go away when path
> > walk fall back is improved.
> 
> Great, let me know when you have a rough shot at it ready for testing.

Will do

  reply	other threads:[~2009-11-26  6:20 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
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 [this message]
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=20091126062020.GH17484@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=cmm@us.ibm.com \
    --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@us.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=tytso@mit.edu \
    --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®