diff options
author | Nick Piggin <npiggin@kernel.dk> | 2011-01-07 07:50:09 +0100 |
---|---|---|
committer | Nick Piggin <npiggin@kernel.dk> | 2011-01-07 07:50:32 +0100 |
commit | 9d55c369bb5e695e629bc35cba2ef607755b3bee (patch) | |
tree | d97cd498a67f1f7987d4403ef90e399516a3b8c9 /crypto/cts.c | |
parent | fs: prefetch inode data in dcache lookup (diff) | |
download | linux-9d55c369bb5e695e629bc35cba2ef607755b3bee.tar.xz linux-9d55c369bb5e695e629bc35cba2ef607755b3bee.zip |
fs: implement faster dentry memcmp
The standard memcmp function on a Westmere system shows up hot in
profiles in the `git diff` workload (both parallel and single threaded),
and it is likely due to the costs associated with trapping into
microcode, and little opportunity to improve memory access (dentry
name is not likely to take up more than a cacheline).
So replace it with an open-coded byte comparison. This increases code
size by 8 bytes in the critical __d_lookup_rcu function, but the
speedup is huge, averaging 10 runs of each:
git diff st user sys elapsed CPU
before 1.15 2.57 3.82 97.1
after 1.14 2.35 3.61 96.8
git diff mt user sys elapsed CPU
before 1.27 3.85 1.46 349
after 1.26 3.54 1.43 333
Elapsed time for single threaded git diff at 95.0% confidence:
-0.21 +/- 0.01
-5.45% +/- 0.24%
It's -0.66% +/- 0.06% elapsed time on my Opteron, so rep cmp costs on the
fam10h seem to be relatively smaller, but there is still a win.
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Diffstat (limited to 'crypto/cts.c')
0 files changed, 0 insertions, 0 deletions