On Wed, 2012-02-15 at 09:28 +0100, Pavel Březina wrote: > - if we change the parent of a child of talloc pool to a parent that is > outside of this pool, the whole pool memory will not be freed until > the child is freed.
This part makes me REALLY nervous. We do a LOT of talloc stealing all over the place (in the case of the provider lookups, we often steal request memory onto long-running responder contexts). Using pools could very easily result in our ending up with a significantly larger memory footprint. I think we want to be VERY careful about how we use this, if at all. Jan's comments about using a pool to handle realloc() loops are interesting, but it would still require us to have a good sense of how large a pool we needed in the average case (otherwise it will just end up resorting to using standard contexts anyway, negating our advantages).
signature.asc
Description: This is a digitally signed message part
_______________________________________________ sssd-devel mailing list [email protected] https://fedorahosted.org/mailman/listinfo/sssd-devel
