From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: Generalise GPU activity tracking
Date: Thu, 31 Jan 2019 11:40:25 +0000 [thread overview]
Message-ID: <96830fb4-12ba-8865-c8a9-6358fa30f3a7@linux.intel.com> (raw)
In-Reply-To: <154893435207.14784.17343157252087384042@skylake-alporthouse-com>
On 31/01/2019 11:32, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2019-01-31 11:25:10)
>>
>> On 30/01/2019 20:50, Chris Wilson wrote:
>>> We currently track GPU memory usage inside VMA, such that we never
>>> release memory used by the GPU until after it has finished accessing it.
>>> However, we may want to track other resources aside from VMA, or we may
>>> want to split a VMA into multiple independent regions and track each
>>> separately. For this purpose, generalise our request tracking (akin to
>>> struct reservation_object) so that we can embed it into other objects.
>>>
>>
>> Changelog where art thou?
>
> The changes are patches 2 & 3!
>
> This patch is just about moving code, we haven't come up with a new name
> so nothing to change here yet. But I wanted to discuss to the idea of
> immediately parking and using global slabs.
There's a new GEM_BUG_ON! ;)
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-01-31 11:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 20:50 [PATCH 1/3] drm/i915: Generalise GPU activity tracking Chris Wilson
2019-01-30 20:50 ` [PATCH 2/3] drm/i915: Release the active tracker tree upon idling Chris Wilson
2019-01-31 11:33 ` Tvrtko Ursulin
2019-01-30 20:50 ` [PATCH 3/3] drm/i915: Allocate active tracking nodes from a slabcache Chris Wilson
2019-01-31 9:39 ` kbuild test robot
2019-01-31 9:50 ` kbuild test robot
2019-01-31 11:39 ` Tvrtko Ursulin
2019-01-31 11:41 ` Chris Wilson
2019-01-30 22:56 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915: Generalise GPU activity tracking Patchwork
2019-01-30 22:58 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-30 23:19 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-31 9:06 ` ✓ Fi.CI.IGT: " Patchwork
2019-01-31 11:25 ` [PATCH 1/3] " Tvrtko Ursulin
2019-01-31 11:32 ` Chris Wilson
2019-01-31 11:40 ` Tvrtko Ursulin [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=96830fb4-12ba-8865-c8a9-6358fa30f3a7@linux.intel.com \
--to=tvrtko.ursulin@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