diff options
| author |   Michael S. Tsirkin <mst@redhat.com> | 2013-11-04 22:36:25 +0200 |
|---|---|---|
| committer |   Gleb Natapov <gleb@redhat.com> | 2013-11-06 09:32:31 +0200 |
| commit | 01b71917b55d28c09ade9fb8c683cf0d2aad1858 (patch) | |
| tree | 5ec0842876cd80c754c486dac1a810850d98ecd6 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | srcu: API for barrier after srcu read unlock (diff) | |
| download | linux-dev-01b71917b55d28c09ade9fb8c683cf0d2aad1858.tar.xz linux-dev-01b71917b55d28c09ade9fb8c683cf0d2aad1858.zip | |
kvm: optimize out smp_mb after srcu_read_unlock
I noticed that srcu_read_lock/unlock both have a memory barrier,
so just by moving srcu_read_unlock earlier we can get rid of
one call to smp_mb() using smp_mb__after_srcu_read_unlock instead.
Unsurprisingly, the gain is small but measureable using the unit test
microbenchmark:
before
vmcall in the ballpark of 1410 cycles
after
vmcall in the ballpark of 1360 cycles
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Gleb Natapov <gleb@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions