reserving VRAM for page tables

Christian König christian.koenig at
Thu Dec 5 17:09:36 UTC 2019

Yeah, but we should try to unify the memory management.

I mean we must have a common rational on how much memory page tables are 
going to use.

If we allow applications to oversubscribe or not is a completely 
different topic.


Am 05.12.19 um 18:05 schrieb Felix Kuehling:
> I don't think this should go into amdgpu_vram_mgr. KFD tries to avoid 
> running out of VRAM for page tables because we cannot oversubscribe 
> memory within a process and we want to avoid compute processes 
> evicting each other because that would mean thrashing. Those 
> limitation don't apply to graphics contexts.
> Regards,
>   Felix
> On 2019-12-05 5:50 a.m., Christian König wrote:
>> Sorry, just forgot to add the mailing list.
>> Am 05.12.19 um 11:49 schrieb Christian König:
>>> Hi guys,
>>> I've seen some patches flying by to change how much VRAM is reserved 
>>> for page tables in the KFD.
>>> Would it make sense to fully move that into amdgpu_vram_mgr.c?
>>> Regards,
>>> Christian.

More information about the amd-gfx mailing list