Reviewed-by: Marek Olšák
Marek
On Thu, Jan 31, 2013 at 4:38 PM, wrote:
> From: Jerome Glisse
>
> We are now seing cs that can go over the vram+gtt size to avoid
> failing flush early cs that goes over 70% (gtt+vram) usage. 70%
> is use to allow some fragmentation.
>
> The idea is to compute a
On Thu, Jan 31, 2013 at 4:29 PM, Jerome Glisse wrote:
> On Wed, Jan 30, 2013 at 10:35 PM, Marek Olšák wrote:
>> On Wed, Jan 30, 2013 at 6:14 PM, wrote:
>>> From: Jerome Glisse
>>>
>>> We are now seing cs that can go over the vram+gtt size to avoid
>>> failing flush early cs that goes over 70%
From: Jerome Glisse
We are now seing cs that can go over the vram+gtt size to avoid
failing flush early cs that goes over 70% (gtt+vram) usage. 70%
is use to allow some fragmentation.
The idea is to compute a gross estimate of memory requirement of
each draw call. After each draw call, memory wi
On Wed, Jan 30, 2013 at 10:35 PM, Marek Olšák wrote:
> On Wed, Jan 30, 2013 at 6:14 PM, wrote:
>> From: Jerome Glisse
>>
>> We are now seing cs that can go over the vram+gtt size to avoid
>> failing flush early cs that goes over 70% (gtt+vram) usage. 70%
>> is use to allow some fragmentation.
>
On Wed, Jan 30, 2013 at 6:14 PM, wrote:
> From: Jerome Glisse
>
> We are now seing cs that can go over the vram+gtt size to avoid
> failing flush early cs that goes over 70% (gtt+vram) usage. 70%
> is use to allow some fragmentation.
>
> Signed-off-by: Jerome Glisse
> ---
> src/gallium/drivers
From: Jerome Glisse
We are now seing cs that can go over the vram+gtt size to avoid
failing flush early cs that goes over 70% (gtt+vram) usage. 70%
is use to allow some fragmentation.
Signed-off-by: Jerome Glisse
---
src/gallium/drivers/r600/evergreen_state.c| 4
src/gallium/drivers/
