Age | Commit message (Collapse) | Author | Files | Lines |
|
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)
|
|
metze
(This used to be commit 84ebb6cac224cabf3856a632de80a8a9c687329b)
|
|
(This used to be commit c676a971142d7176fd5dbf21405fca14515a0a76)
|
|
(This used to be commit 1b78cace504f60c0f525765fbf59d9cc6506cd4d)
|
|
metze
(This used to be commit 86c510e3198e03ed6efa61b27530bbb008f6802b)
|
|
metze
(This used to be commit 7fab12b34a818f029f4285a59d6e49768b7f8e79)
|
|
(This used to be commit ced12bd6d8c95a103cb2c84166a64f9a21bd32ad)
|
|
(This used to be commit 65e1500ae6b5ca6334a63f4a18272568202bc048)
|
|
- fix bug 4078
- talloc_free(talloc_autofree_context()); should not result
in a SIGABORT on exit
- add a test for this, but this test can also pass in the standalone build
and samba3, as samba4 uses talloc_autofree_context()
metze
(This used to be commit f5b0924f975f58bba3c13a53388ea25af51d3bc8)
|
|
to make mergeing easier.
metze
(This used to be commit d49ffbc19b29f7620e427de133ffab74721f37e8)
|