On 11/22/2013 10:30 AM, Eric Anholt wrote:
Kenneth Graunke writes:
On 11/22/2013 12:21 AM, Eric Anholt wrote:
The canary is basically just to give a better debugging message when you
ralloc_free() something that wasn't rallocated. Reduces maximum memory
usage of apitrace replay of the dota2
Kenneth Graunke writes:
> On 11/22/2013 12:21 AM, Eric Anholt wrote:
>> The canary is basically just to give a better debugging message when you
>> ralloc_free() something that wasn't rallocated. Reduces maximum memory
>> usage of apitrace replay of the dota2 demo by 60MB on my 64-bit system (so
On 11/22/2013 12:21 AM, Eric Anholt wrote:
> The canary is basically just to give a better debugging message when you
> ralloc_free() something that wasn't rallocated. Reduces maximum memory
> usage of apitrace replay of the dota2 demo by 60MB on my 64-bit system (so
> half that on a real 32-bit d
On 11/22/2013 12:21 AM, Eric Anholt wrote:
> The canary is basically just to give a better debugging message when you
> ralloc_free() something that wasn't rallocated. Reduces maximum memory
> usage of apitrace replay of the dota2 demo by 60MB on my 64-bit system (so
> half that on a real 32-bit d
The canary is basically just to give a better debugging message when you
ralloc_free() something that wasn't rallocated. Reduces maximum memory
usage of apitrace replay of the dota2 demo by 60MB on my 64-bit system (so
half that on a real 32-bit dota2 environment).
---
src/glsl/ralloc.c | 6 +
