public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: intel-gfx@lists.freedesktop.org
Subject: GEM shrinker and vm.overcommit_memory=2
Date: Thu, 06 Jun 2019 11:54:48 +0200	[thread overview]
Message-ID: <87y32fqbrr.fsf@oldenburg2.str.redhat.com> (raw)

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

                 reply	other threads:[~2019-06-06  9:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y32fqbrr.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox