Use proper object allocators for unknown object nodes too
commit2c1cbec1e2f0bd7b15fe5e921d287babfd91c7d3
authorLinus Torvalds <torvalds@linux-foundation.org>
Tue, 17 Apr 2007 05:10:19 +0000 (16 22:10 -0700)
committerJunio C Hamano <junkio@cox.net>
Tue, 17 Apr 2007 06:36:11 +0000 (16 23:36 -0700)
treeee149f21b7fe1a53ced6a4051e10268608d14d54
parentf948792990f82a35bf0c98510e7511ef8acb9cd3
Use proper object allocators for unknown object nodes too

We used to use a different allocator scheme for when we didn't know the
object type.  That meant that objects that were created without any
up-front knowledge of the type would not go through the same allocation
paths as normal object allocations, and would miss out on the statistics.

But perhaps more importantly than the statistics (that are useful when
looking at memory usage but not much else), if we want to make the
object hash tables use a denser object pointer representation, we need
to make sure that they all go through the same blocking allocator.

Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
alloc.c
cache.h
object.c