<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][SHARDS] igt@gem_tiled_swapping@non-threaded - dmesg-warn - page allocation failure"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108686#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][SHARDS] igt@gem_tiled_swapping@non-threaded - dmesg-warn - page allocation failure"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108686">bug 108686</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>We already do a couple of allocation passes before we hit the failure message,
and the allocation itself will do a couple of attempts before warning. We know
we have plenty of memory available, and we know most of it is tied up in GPU
buffers, so we know we can do better -- it's just trying to ensure we never run
out of kernel reserves that we fail at.
Mostly trying to say it's not a new problem, nor is an easy problem; but it is
a real problem in how the kernel + i915 handles mempressure.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>