All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.william.auld@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/gtt: Allow pagedirectory allocations to fail
Date: Tue, 22 May 2018 10:44:06 +0100	[thread overview]
Message-ID: <CAM0jSHPkdASHQCTjfs0ECmxA18mmz99yoX7Z+UfyxmWc7Sg+5w@mail.gmail.com> (raw)
In-Reply-To: <20180522083643.29601-1-chris@chris-wilson.co.uk>

On 22 May 2018 at 09:36, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> As we handle the allocation failure of the page directory and tables by
> propagating the failure back to userspace, allow it to fail if direct
> reclaim is unable to satisfy the request (i.e. disable the oomkiller).
> The premise being that if we are unable to allocate a single page for
> the pagetable, we will not be able to handle the multitude of pages
> required for the gfx operation and we should back off to allow the
> system to recover.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=106609
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Matthew Auld <matthew.william.auld@gmail.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Reviewed-by: Matthew Auld <matthew.william.auld@gmail.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-05-22  9:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22  8:36 [PATCH] drm/i915/gtt: Allow pagedirectory allocations to fail Chris Wilson
2018-05-22  9:30 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-05-22  9:44 ` Matthew Auld [this message]
2018-05-22 11:09   ` [PATCH] " Chris Wilson
2018-05-22 11:08 ` ✓ Fi.CI.IGT: success for " 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=CAM0jSHPkdASHQCTjfs0ECmxA18mmz99yoX7Z+UfyxmWc7Sg+5w@mail.gmail.com \
    --to=matthew.william.auld@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --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.