<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [ILK/HSW]igt/gem_tiled_swapping randomly causes OOM killer"
href="https://bugs.freedesktop.org/show_bug.cgi?id=72742#c97">Comment # 97</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [ILK/HSW]igt/gem_tiled_swapping randomly causes OOM killer"
href="https://bugs.freedesktop.org/show_bug.cgi?id=72742">bug 72742</a>
from <span class="vcard"><a class="email" href="mailto:dave@sr71.net" title="Dave Hansen <dave@sr71.net>"> <span class="fn">Dave Hansen</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=72742#c95">comment #95</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=72742#c94">comment #94</a>)
> > We died with over 1.3GiB of pending writeback which exceeds the amount of
> > memory we left spare during the test.
>
> Do we need to resurrect the writeback harder hacks?</span >
The problem isn't the number of writeback pages, the problem is that the pages
are not on a path to being freed. Even with a large amount of writeback, the
VM will notice that _some_ of it is getting written out, and will resist OOMing
until progress stops being made. The reason for the OOM here is that lack of
progress. Waiting on writeback will, of course, reduce the number of pages
under writeback, but it just delays the inevitable when overall reclaim
progress isn't being made.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<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>