From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Drop the unbound page cache upon idling
Date: Thu, 16 Nov 2017 12:11:16 +0200 [thread overview]
Message-ID: <1510827076.5503.1.camel@linux.intel.com> (raw)
In-Reply-To: <20171114191135.26205-1-chris@chris-wilson.co.uk>
On Tue, 2017-11-14 at 19:11 +0000, Chris Wilson wrote:
> When the GPU is idle, we can take a breather and release our hold on our
> many caches. One such cache is that we keep objects pinned in memory
> even when they are no longer accessible by the GPU, that cache is held
> until the system comes under memory pressure. As we are idle, we can be
> reasonably confident that the pages will not be used again in the near
> future, so let the system know it can recover the memory for its own
> purposes.
>
> Suggested-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> 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
prev parent reply other threads:[~2017-11-16 10:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 19:11 [PATCH 1/2] drm/i915: Drop the unbound page cache upon idling Chris Wilson
2017-11-14 19:11 ` [PATCH 2/2] drm/i915: Remove temporary allocation of dma addresses when rotating Chris Wilson
2017-11-16 10:43 ` Joonas Lahtinen
2017-11-16 11:17 ` Chris Wilson
2017-11-14 19:50 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Drop the unbound page cache upon idling Patchwork
2017-11-14 22:44 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-11-16 10:11 ` Joonas Lahtinen [this message]
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=1510827076.5503.1.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 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.