diff options
author | Chris Wilson <[email protected]> | 2016-01-08 09:55:33 +0000 |
---|---|---|
committer | Thomas Gleixner <[email protected]> | 2016-01-08 19:27:39 +0100 |
commit | 1f1a89ac05f6e88aa341e86e57435fdbb1177c0c (patch) | |
tree | f2ccbc5afe94040c6ba411038e91c63d1ea90101 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 2039e6acaf94d83ec6b6d9f3d0bce7ea1f099918 (diff) |
x86/mm: Micro-optimise clflush_cache_range()
Whilst inspecting the asm for clflush_cache_range() and some perf profiles
that required extensive flushing of single cachelines (from part of the
intel-gpu-tools GPU benchmarks), we noticed that gcc was reloading
boot_cpu_data.x86_clflush_size on every iteration of the loop. We can
manually hoist that read which perf regarded as taking ~25% of the
function time for a single cacheline flush.
Signed-off-by: Chris Wilson <[email protected]>
Reviewed-by: Ross Zwisler <[email protected]>
Acked-by: "H. Peter Anvin" <[email protected]>
Cc: Toshi Kani <[email protected]>
Cc: Borislav Petkov <[email protected]>
Cc: Luis R. Rodriguez <[email protected]>
Cc: Stephen Rothwell <[email protected]>
Cc: Sai Praneeth <[email protected]>
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Thomas Gleixner <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions