From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Matthew Auld <matthew.auld@intel.com>
Subject: Re: [PATCH] drm/i915: Allow internal page allocations to fail
Date: Fri, 15 Dec 2017 12:51:41 +0200 [thread overview]
Message-ID: <1513335101.3617.28.camel@linux.intel.com> (raw)
In-Reply-To: <20171215101753.1519-1-chris@chris-wilson.co.uk>
On Fri, 2017-12-15 at 10:17 +0000, Chris Wilson wrote:
> Internal objects consistent of scratch pages not subject to the
> persistence guarantees of user facing objects. They are used for
> example, in ring buffers where they are only required for temporary
> storage of commands that will be rewritten every time. As they are
> temporary constructs, quietly report -ENOMEM back along the callchain
> rather than subject the system to oomkiller if an allocation fails.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Matthew Auld <matthew.auld@intel.com>
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-12-15 10:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 10:17 [PATCH] drm/i915: Allow internal page allocations to fail Chris Wilson
2017-12-15 10:51 ` Joonas Lahtinen [this message]
2017-12-15 10:52 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-12-15 12:39 ` ✗ Fi.CI.IGT: warning " Patchwork
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=1513335101.3617.28.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
/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.