[PATCH] drm: increase drm mmap_range size to 1TB

Christian König ckoenig.leichtzumerken at gmail.com
Thu Apr 18 08:30:15 UTC 2019


Am 18.04.19 um 09:32 schrieb Chris Wilson:
> Quoting Thomas Zimmermann (2019-04-18 08:29:39)
>> Hi
>>
>> Am 18.04.19 um 00:16 schrieb Kuehling, Felix:
>>> Adding dri-devel
>>>
>>> On 2019-04-17 6:15 p.m., Yang, Philip wrote:
>>>> After patch "drm: Use the same mmap-range offset and size for GEM and
>>>> TTM", application failed to create bo of system memory because drm
>>>> mmap_range size decrease to 64GB from original 1TB. This is not big
>>>> enough for applications. Increase the drm mmap_range size to 1TB.
>> That change in size was accidental. Thanks for restoring the original
>> value. The fix will affect GEM as well. If that is not a problem then
>>
> Why even have an artificial restriction?

Well one possible explanation is that we somewhere need to allocate 
memory to handle all that address space. E.g. when it is managed with a 
radix or similar.

But as far as I remember there are only lists and r/b trees involved 
here, so yeah doesn't make to much sense.

Anyway that is not the topic of this patch and it is Reviewed-by: 
Christian König <christian.koenig at amd.com> for now.

Regards,
Christian.

> -Chris
> _______________________________________________
> dri-devel mailing list
> dri-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel



More information about the dri-devel mailing list