All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: Nick Piggin <npiggin@suse.de>,
	andi.kleen@intel.com, alexs.shi@intel.com, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: scalability investigation: Where can I get your latest patches?
Date: Thu, 5 Aug 2010 20:55:34 +1000	[thread overview]
Message-ID: <20100805105534.GA5683@amd> (raw)
In-Reply-To: <1280883843.2125.20.camel@ymzhang.sh.intel.com>

On Wed, Aug 04, 2010 at 09:04:03AM +0800, Zhang, Yanmin wrote:
> On Tue, 2010-07-20 at 13:12 +1000, Nick Piggin wrote:
> > On Thu, Jul 08, 2010 at 04:56:27PM +0800, Zhang, Yanmin wrote:
> > > Nick,
> > > 
> > > I work with Andi Kleen and Tim to investigate some scalability issues.
> > > 
> > > Andi gave me a pointer at:
> > > http://thread.gmane.org/gmane.linux.kernel/1002380/focus=42284
> > > 
> > > Where can I get your latest patches? It's better if I could get patch tarball.
> > > 
> > > Thanks,
> > > Yanmin
> > > 
> > 
> > Hi Yanmin,
> > 
> > Sorry for the delay. I have a git tree now, and it has been through
> > some tress testing.
> > 
> > http://git.kernel.org/?p=linux/kernel/git/npiggin/linux-npiggin.git
> > 
> > I would be very interested to know if you encounter problems or are
> > able to generate any benchmark numbers.
> Nick,
> 
> We ran lots of benchmarks on many machines. Below is something to
> share with you.

Great, thanks for doing this!

 
> Improvement:
> 1) We get about 30% improvement with kbuild workload on Nehalem
> machines. It's hard to improve kbuild performance. Your tree does.

Well that's nice. What size of machine is this? Did you run it on an
ACL enabled filesystem?


> Issues:
> 1) Compiling fails on a couple of file systems, such like CONFIG_ISO9660_FS=y.

Yes there are a couple that broke, which I still need to fix up.


> 2) dbenchthreads has about 50% regression. We connect a JBOD of 12 disks to
> a machine. Start 4 dbench threads per disk.  We run the workload under
> a regular user account. If we run it under root account, we get 22%
> improvement instead of regression.  The root cause is ACL checking.
> With your patch, do_path_lookup firstly goes through rcu steps which
> including a exec permission checking. With ACL, the __exec_permission
> always fails. Then a later nameidata_drop_rcu often fails as
> dentry->d_seq is changed.
> 
> With root account, it doesn't happen. We mount the working devices
> under /mnt/stp/XXX.  /mnt is of root user. So the exec permission
> check is ok.

Yes if running with root, this should have the same effect as the
rcu-walk aware ACL patch. BTW. dbench has a nasty call to statvfs()
which is a huge cost (which should be fixed in future versions of
kernel+glibc). You can try switching the statvfs(2) call in fileio.c
to statfs(2) and see if performance improves.

Are you disk bound or CPU bound at this point?

> I remount all file systems on the testing path with noacl option, and
> get the similar results like under root account.
> 
> 3) aim7 has about 40% regression on Nehalem EX 4-socket machine. The
> root cause is the same thing like 2).
 
Thanks for subsequently porting and testing the ACL patch. I saw some
performance gains on reaim on 2 socket 8 core machine, although it
would depend on the workfile used.

Thanks,
Nick

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2010-08-05 10:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1278579387.2096.889.camel@ymzhang.sh.intel.com>
     [not found] ` <20100720031201.GC21274@amd>
2010-08-04  1:04   ` scalability investigation: Where can I get your latest patches? Zhang, Yanmin
2010-08-04  1:04     ` Zhang, Yanmin
2010-08-04  7:21     ` Kleen, Andi
2010-08-04  7:21       ` Kleen, Andi
2010-08-04  7:58       ` Zhang, Yanmin
2010-08-04  7:58         ` Zhang, Yanmin
2010-08-04  8:06         ` Kleen, Andi
2010-08-04  8:50           ` Zhang, Yanmin
2010-08-04  8:50             ` Zhang, Yanmin
2010-08-05 10:57             ` Nick Piggin
2010-08-05 10:57               ` Nick Piggin
2010-08-05 10:55     ` Nick Piggin [this message]
2010-08-09  2:11       ` Zhang, Yanmin
2010-08-09  2:11         ` Zhang, Yanmin
2010-08-09  3:20       ` Zhang, Yanmin
2010-08-09  3:20         ` Zhang, Yanmin
2010-08-05 11:44     ` Nick Piggin
2010-08-05 11:44       ` Nick Piggin
2010-08-09  2:36       ` Zhang, Yanmin
2010-08-09  2:36         ` Zhang, Yanmin

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=20100805105534.GA5683@amd \
    --to=npiggin@suse.de \
    --cc=alexs.shi@intel.com \
    --cc=andi.kleen@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=yanmin_zhang@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.