<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - per-process/context memory usage accounting for i915" href="https://bugs.freedesktop.org/show_bug.cgi?id=106136#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - per-process/context memory usage accounting for i915" href="https://bugs.freedesktop.org/show_bug.cgi?id=106136">bug 106136</a> from <a class="email" href="mailto:abdiel.janulgue@linux.intel.com" title="Abdiel Janulgue <abdiel.janulgue@linux.intel.com>"> Abdiel Janulgue</a> <pre>(In reply to Eero Tamminen from <a href="show_bug.cgi?id=106136#c7">comment #7</a>) > > > 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...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>