Quoting Andrew Morton (2018-11-06 18:12:11)
> On Tue, 6 Nov 2018 13:23:24 + Chris Wilson
> wrote:
>
> > From: Kuo-Hsin Yang
> >
> > The i915 driver uses shmemfs to allocate backing storage for gem
> > objects. These shmemfs pages can be pinned (increased ref count) by
> > shmem_read_mappi
On Tue, 6 Nov 2018 13:23:24 + Chris Wilson
wrote:
> From: Kuo-Hsin Yang
>
> The i915 driver uses shmemfs to allocate backing storage for gem
> objects. These shmemfs pages can be pinned (increased ref count) by
> shmem_read_mapping_page_gfp(). When a lot of pages are pinned, vmscan
> wast
On 11/6/18 5:23 AM, Chris Wilson wrote:
> + (3) By the i915 driver to mark pinned address space until it's unpinned. The
> + amount of unevictable memory marked by i915 driver is roughly the
> bounded
> + object size in debugfs/dri/0/i915_gem_objects.
Thanks for adding this. Feel free to
On Tue, Nov 6, 2018 at 9:23 PM Chris Wilson wrote:
> Cc: Chris Wilson
> Cc: Joonas Lahtinen
> Cc: Peter Zijlstra
> Cc: Andrew Morton
> Cc: Dave Hansen
> Signed-off-by: Kuo-Hsin Yang
> Acked-by: Michal Hocko # mm part
> Reviewed-by: Chris Wilson
Thanks for your fixes and review.
__
From: Kuo-Hsin Yang
The i915 driver uses shmemfs to allocate backing storage for gem
objects. These shmemfs pages can be pinned (increased ref count) by
shmem_read_mapping_page_gfp(). When a lot of pages are pinned, vmscan
wastes a lot of time scanning these pinned pages. In some extreme case,
al
