<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [IGT] gem_shrink subtest mmap-gtt oom"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104327#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [IGT] gem_shrink subtest mmap-gtt oom"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104327">bug 104327</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>The problem here is that we end up with all 128 threads hitting the reclaim
logic; each threading pinning the object it has faulted. Only one thread can
make any progress through the oom-logic, but it can't make progress unless it
is the one holding struct_mutex. Ergo it reports failure and the oom-killer
proceeds without mercy.
There is certainly no quick fix for this.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>