[Bug 106136] per-process/context memory usage accounting for i915

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon May 7 12:28:56 UTC 2018


https://bugs.freedesktop.org/show_bug.cgi?id=106136

--- Comment #9 from Abdiel Janulgue <abdiel.janulgue at linux.intel.com> ---
(In reply to Eero Tamminen from comment #7)

> 
> > Note that from a GPU context POV, it is allowed access to entire 2 tebibytes
> > of virtual address space. 

Sorry for the typo. This is actually 256 TiB (48-bit addressing)

> 
> Yep.  If GEM object is requested, it's also likely to be written to, i.e.
> it's dirty.  If process leaks such object, it's not anymore used, and kernel
> will just swap it out when more RAM is needed. When swap runs out, device is
> in OOM crash-fest until swap filling process happens to terminate or get
> killed.

This is the "lazy" optimization feature in the kernel where we defer removing
BOs from the GTTs, in the hope they get reused. One (possibly horrible?)
solution for this is to introduce a hook to force clear the objects from the
GTT...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180507/54922fa1/attachment.html>


More information about the intel-gfx-bugs mailing list