diff options
| author |   Chris Wilson <chris@chris-wilson.co.uk> | 2017-10-13 21:26:18 +0100 |
|---|---|---|
| committer | Chris Wilson <chris@chris-wilson.co.uk> | 2017-10-16 20:44:19 +0100 |
| commit | 4e773c3a8a693e5abc248c5be26973b868466dde (patch) | |
| tree | 61ca3c2295d12f60cbe3bad9454746bf1b21b819 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | drm/i915: Move dev_priv->mm.[un]bound_list to its own lock (diff) | |
| download | linux-dev-4e773c3a8a693e5abc248c5be26973b868466dde.tar.xz linux-dev-4e773c3a8a693e5abc248c5be26973b868466dde.zip | |
drm/i915: Wire up shrinkctl->nr_scanned
shrink_slab() allows us to report back the number of objects we
successfully scanned (out of the target shrinkctl->nr_to_scan). As
report the number of pages owned by each GEM object as a separate item
to the shrinker, we cannot precisely control the number of shrinker
objects we scan on each pass; and indeed may free more than requested.
If we fail to tell the shrinker about the number of objects we process,
it will continue to hold a grudge against us as any objects left
unscanned are added to the next reclaim -- and so we will keep on
"unfairly" shrinking our own slab in comparison to other slabs.
v2: fixup the misplaced addition, we want to count everything we scan
(to match the number we reported earlier) not just the objects we
successfully validated and freed.
References: 912d572d63b8 ("drm/i915: wire up shrinkctl->nr_scanned")
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20171013202621.7276-6-chris@chris-wilson.co.uk
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions