summaryrefslogtreecommitdiff
path: root/source3/Makefile.in
diff options
context:
space:
mode:
authorVolker Lendecke <vl@samba.org>2008-01-05 18:26:54 +0100
committerJeremy Allison <jra@samba.org>2008-01-09 17:05:19 -0800
commit1ed4fcb271b7885c274bd88bafed8116779d8eb6 (patch)
tree11a2bf2be3acbd22e866abdf3001746bf69ba80d /source3/Makefile.in
parent6a1022288217304ebf4f3a3e59a1efa472ff2c5b (diff)
downloadsamba-1ed4fcb271b7885c274bd88bafed8116779d8eb6.tar.gz
samba-1ed4fcb271b7885c274bd88bafed8116779d8eb6.tar.bz2
samba-1ed4fcb271b7885c274bd88bafed8116779d8eb6.zip
Implement talloc_pool()
A talloc pool is a chunk of memory that can be used as a context for further talloc calls. Allocations with the pool as the parent just chew from that memory by incrementing a pointer. If the talloc pool is full, then we fall back to the normal system-level malloc(3) to get memory. The use case for talloc pools is the transient memory that is used for handling a single SMB request. Incrementing a pointer will be way faster than any malloc implementation. There is a downside of this: If you use talloc_steal() to move something out of the pool, the whole pool memory is kept around until the last object inside the pool is freed. So if you talloc_free() the pool, it might happen that the memory is freed later. So don't hang anything off a talloc pool that should live long. Volker (This used to be commit 287e29d988813007eeebc0c2bef3b46ab8bedee9)
Diffstat (limited to 'source3/Makefile.in')
0 files changed, 0 insertions, 0 deletions