drm/vmwgfx: Remove usage of MOBFMT_RANGE

Browse source

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

...

This commit is contained in:

Zack Rusin 2021-12-06 12:26:19 -05:00

parent bf625870b8

commit 9ca476acd5

3 changed files with 0 additions and 19 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

1

drivers/gpu/drm/vmwgfx/vmwgfx_drv.h

View file

6

drivers/gpu/drm/vmwgfx/vmwgfx_mob.c

View file

12

drivers/gpu/drm/vmwgfx/vmwgfx_ttm_buffer.c

View file