<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI] igt@gem_ctx_create@basic-files - dmesg-warn - gem_ctx_create: page allocation failure" href="https://bugs.freedesktop.org/show_bug.cgi?id=106954#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI] igt@gem_ctx_create@basic-files - dmesg-warn - gem_ctx_create: page allocation failure" href="https://bugs.freedesktop.org/show_bug.cgi?id=106954">bug 106954</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>Just one of the usual lack-of-reclaim faux pas. There are a lot of shmem objects there that we would expect to be able to swap out and load a new object. However, since we are using MAYFAIL in this case, we purposely don't try very hard. It would be justifiable to remove the warning as the ENOMEM goes straight back to userspace, but on the other hand we need to improve the shrinker for this case as well. The prudent course of action would be to create a test that reproduces this MAYFAIL reliably; although the ability of the shrinker to reclaim memory will be dependent on the type of objects and workload, so definitely will not be a one-test-fits-all.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>