[Mesa-dev] [PATCH 2/5] mesa: implement GL_NVX_gpu_memory_info

Marek Olšák maraeo at gmail.com
Tue Feb 2 20:21:20 UTC 2016


On Tue, Feb 2, 2016 at 9:18 PM, Roland Scheidegger <sroland at vmware.com> wrote:
> Am 02.02.2016 um 20:41 schrieb Marek Olšák:
>> On Tue, Feb 2, 2016 at 4:02 PM, Roland Scheidegger <sroland at vmware.com> wrote:
>>> Does anyone use these extensions?
>>> I suppose maybe to get the total amount of video memory?
>>> From the dynamic counts, I would have thought the eviction one would be
>>> the most interesting, but this one isn't implemented. Ah well I guess a
>>> sloppily implemented extension is better than none.
>>
>> I know from personal experience that Unreal Engine 3 uses one of them
>> (or maybe both), because it crashed when I had a bug there. I've heard
>> the Source engine uses them too.
>>
>> The use case for modern games is to support texture paging, i.e.
>> loading texture pages on demand based on on-screen visibility of
>> textures and available memory.
>
> But do they really use available memory or just total memory? Anyway, I
> guess if it's used that's ok, I'm just not a fan of odd fringe vendor
> specific extensions.

They use both. The ATI extension only returns the available memory,
not total memory.

Marek


More information about the mesa-dev mailing list