From: Marek Ol??k
The statistics are:
- VRAM usage in bytes
- GTT usage in bytes
- number of bytes moved by TTM
The last one is actually a counter, so you need to sample it before and after
command submission and take the difference.
This is useful for finding performance
Dammit. I renamed the RADEON_INFO definitions for the new queries to
0xd, e, f in the kernel tree, but I forgot to update the Mesa code,
which used 0xc, d, e. Sorry.
Marek
On Wed, Feb 26, 2014 at 7:26 PM, Christian K?nig
wrote:
> Am 26.02.2014 18:56, schrieb Marek Ol??k:
>
>> On Mon, Feb 24,
Am 26.02.2014 18:56, schrieb Marek Ol??k:
> On Mon, Feb 24, 2014 at 5:20 PM, Christian K?nig
> wrote:
>> Am 24.02.2014 16:20, schrieb Marek Ol??k:
>>
>>> From: Marek Ol??k
>>>
>>> The statistics are:
>>> - VRAM usage in bytes
>>> - GTT usage in bytes
>>> - number of bytes moved by TTM
>>>
>>>
From: Marek Ol??k
The statistics are:
- VRAM usage in bytes
- GTT usage in bytes
- number of bytes moved by TTM
The last one is actually a counter, so you need to sample it before and after
command submission and take the difference.
This is useful for finding performance
On Mon, Feb 24, 2014 at 5:20 PM, Christian K?nig
wrote:
> Am 24.02.2014 16:20, schrieb Marek Ol??k:
>
>> From: Marek Ol??k
>>
>> The statistics are:
>> - VRAM usage in bytes
>> - GTT usage in bytes
>> - number of bytes moved by TTM
>>
>> The last one is actually a counter, so you need to sample
Am 24.02.2014 16:20, schrieb Marek Ol??k:
> From: Marek Ol??k
>
> The statistics are:
> - VRAM usage in bytes
> - GTT usage in bytes
> - number of bytes moved by TTM
>
> The last one is actually a counter, so you need to sample it before and after
> command submission and take the difference.
>
>
From: Marek Ol??k
The statistics are:
- VRAM usage in bytes
- GTT usage in bytes
- number of bytes moved by TTM
The last one is actually a counter, so you need to sample it before and after
command submission and take the difference.
This is useful for finding performance