From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Call cond_resched() before repeating i915_gem_evict_something()
Date: Wed, 25 Oct 2017 12:25:17 +0300 [thread overview]
Message-ID: <1508923517.13538.0.camel@linux.intel.com> (raw)
In-Reply-To: <20171024205053.7845-1-chris@chris-wilson.co.uk>
On Tue, 2017-10-24 at 21:50 +0100, Chris Wilson wrote:
> Insert a breakpoint, a chance to escape back to the scheduler and run
> something else for a bit, if we find that the GGTT is full and needs to
> be idled in order to make some room. In practice, this should only be an
> issue in stress tests as the wait itself will normally give the chance
> for the scheduler to intervene and make progress.
>
> References: https://bugs.freedesktop.org/show_bug.cgi?id=103438
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.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-10-25 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 20:50 [PATCH] drm/i915: Call cond_resched() before repeating i915_gem_evict_something() Chris Wilson
2017-10-24 21:23 ` ✗ Fi.CI.BAT: warning for " Patchwork
2017-10-25 9:25 ` Joonas Lahtinen [this message]
2017-10-25 13:18 ` ✗ Fi.CI.BAT: failure " 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=1508923517.13538.0.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox