From: Nick Piggin <npiggin@kernel.dk>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [announce] rcu-walk and dcache scaling tree update
Date: Wed, 15 Dec 2010 21:22:26 +1100 [thread overview]
Message-ID: <20101215102226.GA9093@amd> (raw)
I'm rebasing the tree, because I don't expect anybody to be basing
downstream work on it, I hope that doesn't cause anybody pain.
Git tree is here:
git://git.kernel.org/pub/scm/linux/kernel/git/npiggin/linux-npiggin.git
Branch is:
vfs-scale-working
Changes since last posting:
* Added mntget/mntput scaling patch. I think this is important for
testers because it significantly increases parallelism through the
dcache and path walk. So both performance and races will get better
test coverage.
* Missing vfs.txt documentation for new _rcu dentry and inode ops.
* Large improvements to Documentation/filesystems/path-walk.txt
* Improved some changelogs
* Added AMD fam10h numbers to ``memcmp optimisation'' changelog, and
Westmere numbers to ``prefetch inode'' optimisation changelog. The
AMD doesn't get such a big boost as the Intel CPU when avoiding rep
cmp, but does get a small improvement.
Thanks,
Nick
reply other threads:[~2010-12-16 2:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20101215102226.GA9093@amd \
--to=npiggin@kernel.dk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).