diff options
author | Zack Rusin <zackr@vmware.com> | 2021-12-06 12:26:19 -0500 |
---|---|---|
committer | Zack Rusin <zackr@vmware.com> | 2021-12-09 13:16:34 -0500 |
commit | 9ca476acd5e8725706c6ef3b0d94d3005836ffdc (patch) | |
tree | 05364cba1f94396ecd4992ff5a91cfbba0a826d0 /tools/perf/scripts/python/stackcollapse.py | |
parent | bf625870b8309b4af75f9c19d287d0c9230634d3 (diff) |
drm/vmwgfx: Remove usage of MOBFMT_RANGE
Using MOBFMT_RANGE in the early days of guest backed objects was a major
performance win but that has changed a lot since. There's no more
a performance reason to use MOBFMT_RANGE. The device can/will still
profit from the pages being contiguous but marking them as MOBFMT_RANGE
no longer matters.
Benchmarks (e.g. heaven, valley) show that creating page tables
for mob memory is actually faster than using mobfmt ranges.
Signed-off-by: Zack Rusin <zackr@vmware.com>
Reviewed-by: Martin Krastev <krastevm@vmware.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20211206172620.3139754-12-zack@kde.org
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions