<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#c6">Comment # 6</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#c5">comment #5</a>) > What of this do you think could be implemented on user-space??? > Parsing these sysfs files (which contain gem object allocation and free space in the gtt): /sys/kernel/debug/dri/0/i915_gem_gtt /sys/kernel/debug/dri/0/i915_gem_objects Could be enough for a userspace client to basically "guesstimate" and manage how much GPU memory it requests for itself? Note that from a GPU context POV, it is allowed access to entire 2 tebibytes of virtual address space. I guess by design kernel won't get in the way and give it as much as it wants until physical backing pages are no more.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>