mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	lkml <linux-kernel@vger.kernel.org>,
	Clark Williams <williams@redhat.com>,
	John Kacur <jkacur@redhat.com>
Subject: Re: Nick's vfs-scalability patches ported to 2.6.33-rt
Date: Tue, 09 Mar 2010 18:51:02 -0800	[thread overview]
Message-ID: <1268189462.3339.12.camel@localhost.localdomain> (raw)
In-Reply-To: <1267675511.4317.78.camel@localhost.localdomain>

On Wed, 2010-03-03 at 20:05 -0800, john stultz wrote:
> Thomas:  I ran a number of kernel-bench and dbench stress tests on this
> today and I've not seen any issues, so unless Nick has other issues, I
> think it should be ok to pull into -rt.
> 
> You can grab the full patchset that builds ontop of 2.6.33-rt4 here:
> http://sr71.net/~jstultz/dbench-scalability/patches/2.6.33-rt4/vfs-scale.33-rt.tar.bz2

Oh, and another interesting data point!

The ext2 performance numbers with this patch set are scaling better then
the 2.6.31-rt-vfs set earlier tested!

http://sr71.net/~jstultz/dbench-scalability/graphs/2.6.33/ext2-dbench.png

Its not perfect, but its closing the gap. More interestingly, where as
we were still seeing path lookup contention in 2.6.31, its not showing
up in the perf logs with 2.6.33. Instead, the contention is on the ext2
group_adjust_blocks function.

And replacing the statvfs call in dbench with statfs pushes the results
past mainline:
http://sr71.net/~jstultz/dbench-scalability/graphs/2.6.33/ext2-dbench-statfs.png


So this all means that with Nick's patch set, we're no longer getting
bogged down in the vfs (at least at 8-way) at all. All the contention is
in the actual filesystem (ext2 in group_adjust_blocks, and ext3 in the
journal and block allocation code).

So again, kudos to Nick!

thanks
-john


  reply	other threads:[~2010-03-10  2:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26  5:53 john stultz
2010-02-26  6:01 ` Nick Piggin
2010-03-03 23:31   ` john stultz
2010-03-04  3:33     ` Nick Piggin
2010-03-04  4:05       ` john stultz
2010-03-10  2:51         ` john stultz [this message]
2010-03-10  9:01           ` Christoph Hellwig
2010-03-12  3:08             ` john stultz
2010-03-12  4:41               ` Dave Chinner
2010-03-15 16:15                 ` Nick Piggin

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=1268189462.3339.12.camel@localhost.localdomain \
    --to=johnstul@us.ibm.com \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --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®