From: john stultz <johnstul@us.ibm.com>
To: Nick Piggin <npiggin@suse.de>
Cc: 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>
Subject: Re: -rt dbench scalabiltiy issue
Date: Tue, 24 Nov 2009 18:16:17 -0800 [thread overview]
Message-ID: <1259115377.2115.25.camel@localhost> (raw)
In-Reply-To: <20091123090630.GF5602@wotan.suse.de>
On Mon, 2009-11-23 at 10:06 +0100, Nick Piggin wrote:
> BTW. Have you tested like ext4, xfs and btrfs cases? I don't think ext3
> is likely to see a huge amount of scalability work, and so it will be
> good to give an early heads up to the more active projects...
Yea, I need to give those a shot. I also generated the same numbers as
before with ext2 (all the raw numbers are in dbench-scalability dir):
http://sr71.net/~jstultz/dbench-scalability/graphs/ext2-scalability.png
Again, its similar to ext3, in that all the -rt variants are hitting
some contention issues. But I was a little surprised to see
2.6.32-rc7-nick below 2.6.32-rc7 there, so generated perf data there as
well:
http://sr71.net/~jstultz/dbench-scalability/perflogs/2.6.32-rc7-nick.ext2.perflog
31.91% dbench [kernel] [k] _spin_lock
|
|--44.17%-- dput
| |
| |--50.39%-- __link_path_walk
| | |
| | |--99.88%-- path_walk
| | | |
| | | |--96.18%-- do_path_lookup
| | | | |
| | | | |--51.49%-- user_path_at
| | | | | |
| | | | | |--96.84%-- vfs_fstatat
| | | | | | vfs_stat
| | | | | | sys_newstat
| | | | | | system_call_fastpath
| | | | | | _xstat
| | | | | |
| | | | | --3.16%-- do_utimes
| | | | | sys_utime
| | | | | system_call_fastpath
| | | | | __GI_utime
| | | | |
| | | | |--43.18%-- do_filp_open
| | | | | do_sys_open
| | | | | sys_open
| | | | | system_call_fastpath
| | | | | __GI___open
...
|--39.98%-- path_get
| |
| |--51.19%-- path_init
| | |
| | |--96.40%-- do_path_lookup
| | | |
| | | |--55.12%-- user_path_at
| | | | |
| | | | |--91.47%-- vfs_fstatat
| | | | | vfs_stat
| | | | | sys_newstat
| | | | | system_call_fastpath
| | | | | _xstat
| | | | | |
| | | | | --100.00%-- 0x7478742e746e65
| | | | |
So I'm a little confused here. Why is dput/path_get showing up in ext2
when it all but disappeared with ramfs? Does ramfs have some sort of
vfs_stat shortcut that avoids whatever is catching us here?
thanks
-john
next prev parent reply other threads:[~2009-11-25 2:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 20:05 -rt dbench scalabiltiy issue 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 [this message]
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=1259115377.2115.25.camel@localhost \
--to=johnstul@us.ibm.com \
--cc=dino@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=paulmck@us.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