From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v3 5/6] drm/i915/ttm: Implement asynchronous TTM moves
Date: Tue, 16 Nov 2021 08:20:48 +0100 [thread overview]
Message-ID: <e5e1eb39-10d1-ef24-e307-89342d28ede3@linux.intel.com> (raw)
In-Reply-To: <12fa8629-d05f-908c-d127-5fe53bc45c1d@intel.com>
On 11/15/21 18:16, Matthew Auld wrote:
Thanks for reviewing, Matthew,
I'll take a look at the comments.
/Thomas
> On 14/11/2021 11:12, Thomas Hellström wrote:
>> Don't wait sync while migrating, but rather make the GPU blit await the
>> dependencies and add a moving fence to the object.
>>
>> This also enables asynchronous VRAM management in that on eviction,
>> rather than waiting for the moving fence to expire before freeing VRAM,
>> it is freed immediately and the fence is stored with the VRAM manager
>> and
>> handed out to newly allocated objects to await before clears and
>> swapins,
>> or for kernel objects before setting up gpu vmas or mapping.
>>
>> To collect dependencies before migrating, add a set of utilities that
>> coalesce these to a single dma_fence.
>>
>> What is still missing for fully asynchronous operation is
>> asynchronous vma
>> unbinding, which is still to be implemented.
>>
>> This commit substantially reduces execution time in the
>> gem_lmem_swapping
>> test.
>>
>> v2:
>> - Make a couple of functions static.
WARNING: multiple messages have this Message-ID (diff)
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 5/6] drm/i915/ttm: Implement asynchronous TTM moves
Date: Tue, 16 Nov 2021 08:20:48 +0100 [thread overview]
Message-ID: <e5e1eb39-10d1-ef24-e307-89342d28ede3@linux.intel.com> (raw)
In-Reply-To: <12fa8629-d05f-908c-d127-5fe53bc45c1d@intel.com>
On 11/15/21 18:16, Matthew Auld wrote:
Thanks for reviewing, Matthew,
I'll take a look at the comments.
/Thomas
> On 14/11/2021 11:12, Thomas Hellström wrote:
>> Don't wait sync while migrating, but rather make the GPU blit await the
>> dependencies and add a moving fence to the object.
>>
>> This also enables asynchronous VRAM management in that on eviction,
>> rather than waiting for the moving fence to expire before freeing VRAM,
>> it is freed immediately and the fence is stored with the VRAM manager
>> and
>> handed out to newly allocated objects to await before clears and
>> swapins,
>> or for kernel objects before setting up gpu vmas or mapping.
>>
>> To collect dependencies before migrating, add a set of utilities that
>> coalesce these to a single dma_fence.
>>
>> What is still missing for fully asynchronous operation is
>> asynchronous vma
>> unbinding, which is still to be implemented.
>>
>> This commit substantially reduces execution time in the
>> gem_lmem_swapping
>> test.
>>
>> v2:
>> - Make a couple of functions static.
next prev parent reply other threads:[~2021-11-16 7:20 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 11:12 [Intel-gfx] [PATCH v3 0/6] drm/i915/ttm: Async migration Thomas Hellström
2021-11-14 11:12 ` Thomas Hellström
2021-11-14 11:12 ` [Intel-gfx] [PATCH v3 1/6] drm/i915: Add functions to set/get moving fence Thomas Hellström
2021-11-14 11:12 ` Thomas Hellström
2021-11-15 12:39 ` [Intel-gfx] " Matthew Auld
2021-11-15 12:39 ` Matthew Auld
2021-11-15 12:44 ` [Intel-gfx] " Thomas Hellström
2021-11-15 12:44 ` Thomas Hellström
2021-11-14 11:12 ` [Intel-gfx] [PATCH v3 2/6] drm/i915: Add support for asynchronous moving fence waiting Thomas Hellström
2021-11-14 11:12 ` Thomas Hellström
2021-11-15 12:36 ` [Intel-gfx] " Matthew Auld
2021-11-15 12:36 ` Matthew Auld
2021-11-15 12:42 ` [Intel-gfx] " Thomas Hellström
2021-11-15 12:42 ` Thomas Hellström
2021-11-15 13:13 ` [Intel-gfx] " Matthew Auld
2021-11-15 13:13 ` Matthew Auld
2021-11-15 13:29 ` [Intel-gfx] " Thomas Hellström
2021-11-15 13:29 ` Thomas Hellström
2021-11-14 11:12 ` [Intel-gfx] [PATCH v3 3/6] drm/i915/ttm: Move the i915_gem_obj_copy_ttm() function Thomas Hellström
2021-11-14 11:12 ` Thomas Hellström
2021-11-15 10:42 ` [Intel-gfx] " Matthew Auld
2021-11-15 10:42 ` Matthew Auld
2021-11-14 11:12 ` [Intel-gfx] [PATCH v3 4/6] drm/i915/ttm: Break refcounting loops at device region unref time Thomas Hellström
2021-11-14 11:12 ` Thomas Hellström
2021-11-15 10:49 ` [Intel-gfx] " Matthew Auld
2021-11-15 10:49 ` Matthew Auld
2021-11-14 11:12 ` [Intel-gfx] [PATCH v3 5/6] drm/i915/ttm: Implement asynchronous TTM moves Thomas Hellström
2021-11-14 11:12 ` Thomas Hellström
2021-11-15 17:16 ` [Intel-gfx] " Matthew Auld
2021-11-15 17:16 ` Matthew Auld
2021-11-16 7:20 ` Thomas Hellström [this message]
2021-11-16 7:20 ` Thomas Hellström
2021-11-18 7:13 ` [Intel-gfx] " Thomas Hellström
2021-11-18 7:13 ` Thomas Hellström
2021-11-14 11:12 ` [Intel-gfx] [PATCH v3 6/6] drm/i915/ttm: Update i915_gem_obj_copy_ttm() to be asynchronous Thomas Hellström
2021-11-14 11:12 ` Thomas Hellström
2021-11-14 11:25 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/ttm: Async migration (rev4) Patchwork
2021-11-14 11:28 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2021-11-14 11:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-11-14 13:32 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=e5e1eb39-10d1-ef24-e307-89342d28ede3@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--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.