On 05/30/2014 05:52 PM, Kenneth Graunke wrote: > On Friday, May 30, 2014 11:07:03 AM Eric Anholt wrote: >> Ian Romanick <i...@freedesktop.org> writes: >>> This series reduces the memory usage of ir_variable quite significantly. >>> >>> The first couple patches add a mechanism to determine the amount of >>> memory used by any kind of IR object. This is used to collect the data >>> that is shown in the commit messages through the series. > > I think that talloc can give you this type of information for basically free > - > I'd rather see an implementation of the ralloc API atop talloc, and then just > turn the memory debugging on. This is quite a bit of code, and incomplete...
It could give some of the same information, but not quite all. For example, if I want to know how much memory is used by ir_dereference_record, I want to know how much is used by the ir_dereference_record objects and the ir_dereference_record::name allocations too. Since everything in the IR gets (eventually) reparented to the IR list, I don't see a way to get that information from just the talloc tracking. You were a lot deeper in the guts of talloc, so you may well know things about it that I do not. :)
signature.asc
Description: OpenPGP digital signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev