From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx@lists.freedesktop.org, "Vetter,
Daniel" <daniel.vetter@intel.com>
Subject: Re: [PATCH] drm/i915: Prefer to report ENOMEM rather than incur the oom for gfx allocations
Date: Wed, 22 Mar 2017 15:11:58 +0200 [thread overview]
Message-ID: <1490188318.2802.50.camel@linux.intel.com> (raw)
In-Reply-To: <20170322110521.29930-1-chris@chris-wilson.co.uk>
On ke, 2017-03-22 at 11:05 +0000, Chris Wilson wrote:
> Since gfx allocations tend to be large, unmovable and disposable, report
> the allocation failure back to userspace as an ENOMEM rather than incur
> the oomkiller. We have already tried to make room by purging our own
> cached gfx objects, and the oomkiller doesn't attribute ownership of gfx
> objects so will likely pick the wrong candidate. Instead, let userspace
> see the ENOMEM.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
A-b from Daniel.
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-03-22 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 11:05 [PATCH] drm/i915: Prefer to report ENOMEM rather than incur the oom for gfx allocations Chris Wilson
2017-03-22 11:23 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-03-22 13:11 ` Joonas Lahtinen [this message]
2017-03-22 13:24 ` [PATCH] " Daniel Vetter
2017-03-22 19:35 ` Chris Wilson
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=1490188318.2802.50.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@intel.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 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.