Github user jpeach commented on the pull request:
https://github.com/apache/trafficserver/pull/489#issuecomment-187322502
> What do you mean by duplicates the memory tracking that is already done?
I just meant that the malloc implementation is already tracking the
allocation size.
> Do you know what the overhead is on malloc_usable_size()?
The space overhead will be smaller, since malloc can know things that you
don't and optimize away the need to carry the size with every allocation. For
example, it can know that pointers within a certain range always point to 8
byte chunks.
I expect the time overhead on ``malloc_usable_size`` would be the same or
better.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
