* GEM shrinker and vm.overcommit_memory=2
@ 2019-06-06 9:54 Florian Weimer
0 siblings, 0 replies; only message in thread
From: Florian Weimer @ 2019-06-06 9:54 UTC (permalink / raw)
To: intel-gfx
In fairly recent past, it was not possible to run desktop systems using
vm.overcommit_memory=2 if they used Intel graphics because without the
OOM killer, the shrinker would never run. Instead, regular memory
allocations would fail eventually.
In addition, the i915 Mesa driver assumed malloc would never fail. So
eventually, the whole desktop infrastructure would crash with a NULL
pointer dereference somewhere in Mesa.
Is running with vm.overcommit_memory=2 a supported configuration? I
expect that vm.overcommit_memory=2 mode could be an interesting
operating mode for OpenCL workloads.
Thanks,
Florian
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-06-06 9:54 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-06 9:54 GEM shrinker and vm.overcommit_memory=2 Florian Weimer
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.