diff options
| author | Daniel Vetter <[email protected]> | 2021-07-21 20:32:29 +0200 |
|---|---|---|
| committer | Daniel Vetter <[email protected]> | 2021-07-22 11:14:14 +0200 |
| commit | 4f62a7e0d3338771261a945ceb87182e911a4f71 (patch) | |
| tree | d3b2f028b67ef9b9a187e31e0ee36f9fdf31d226 /tools/perf/scripts/python | |
| parent | 6b73a7f380a3f1a9599bc802cf78febeb77f42db (diff) | |
drm/i915: Ditch i915 globals shrink infrastructure
This essentially reverts
commit 84a1074920523430f9dc30ff907f4801b4820072
Author: Chris Wilson <[email protected]>
Date: Wed Jan 24 11:36:08 2018 +0000
drm/i915: Shrink the GEM kmem_caches upon idling
mm/vmscan.c:do_shrink_slab() is a thing, if there's an issue with it
then we need to fix that there, not hand-roll our own slab shrinking
code in i915.
Also when this was added there was only one other caller of
kmem_cache_shrink (added 2005 to the acpi code). Now there's a 2nd one
outside of i915 code in a kunit test, which seems legit since that
wants to very carefully control what's in the kmem_cache. This out of
a total of over 500 calls to kmem_cache_create. This alone should have
been warning sign enough that we're doing something silly.
Noticed while reviewing a patch set from Jason to fix up some issues
in our i915_init() and i915_exit() module load/cleanup code. Now that
i915_globals.c isn't any different than normal init/exit functions, we
should convert them over to one unified table and remove
i915_globals.[hc] entirely.
v2: Improve commit message (Jason)
Reviewed-by: Jason Ekstrand <[email protected]>
Cc: David Airlie <[email protected]>
Cc: Jason Ekstrand <[email protected]>
Signed-off-by: Daniel Vetter <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions