Malcolm Rowe wrote:
> On Wed, Jan 10, 2007 at 09:05:25AM -0800, firstname.lastname@example.org wrote:
>> Use a subpool for copy and move operations. If the copy or move fails, and the
>> *_as_child flag is set, we try again. By adding this subpool, we make sure
>> that the memory from the first try (as well as the second) is cleared.
> That's not a typical use of a subpool, unless we have reason to believe
> that the setup_copy() operation will allocate a significant amount of
I don't have any figures, and I'm not sure what the threshold is for "a
significant amount", but my feeling is that the amount of memory isn't
If this is wrong, though, I'm happy to revert.
Received on Wed Jan 10 18:28:27 2007