From: Greg KH <gregkh@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Nick Piggin <npiggin@kernel.dk>,
Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
David Miller <davem@davemloft.net>
Subject: Re: Quick merge window note..
Date: Sat, 8 Jan 2011 15:56:08 -0800 [thread overview]
Message-ID: <20110108235608.GA4470@suse.de> (raw)
In-Reply-To: <AANLkTi=eNucM5d=+zq5euz3dZirJEhPaH9f9ZXuHymEM@mail.gmail.com>
On Fri, Jan 07, 2011 at 05:32:46PM -0800, Linus Torvalds wrote:
> But it's rather impressive and I really wanted to merge it, because
> some of the performance numbers are pretty stunning. For example, a
> hot-cache "find . -size" on my home directory (which basically just
> does name lookups to get the stat information for every file
> recursively) became 35% faster. And that's the _unthreaded_ case. Not
> some odd high-end scalability thing, and not some recompiled binary
> taking advantage of new facilities. Pathname lookup is just simply
> faster.
>
> On the scary side, it's worth noticing that if you see any problems,
> and you think it might be due to the new rcu lookup, rather than
> bisect _everything_ (the merge window has already brought in 3700+
> commits), it may be worth just checking the VFS scale tip itself.
> That's fairly easy, because it's based on plain 2.6.37 (which if it
> isn't stable for you, we have bigger problems than the RCU lookup),
> and is just 57 commits up until commit b3e19d924b6e ("fs: scale
> mntget/mntput").
Thanks for the heads up. In some initial testing here, it all looks
good to me.
greg k-h
prev parent reply other threads:[~2011-01-09 0:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 1:32 Quick merge window note Linus Torvalds
2011-01-08 23:56 ` Greg KH [this message]
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=20110108235608.GA4470@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@kernel.dk \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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