dnsperf and BIND memory consumption
JINMEI Tatuya / 神明達哉
Jinmei_Tatuya at isc.org
Mon Jan 5 21:58:23 UTC 2009
At Thu, 01 Jan 2009 00:04:49 -0500,
Danny Mayer <mayer at gis.net> wrote:
> Personally, I'm not convinced that it will make a difference outside of
> Windows. The fix is to make sure a lock gets destroyed when done and the
> function exits. On Windows the lock gets created and memory is allocated
> for it outside of the function using it and needs to be explicitly
> destroyed, but my understanding of pthreads was that this worked
> differently on Unix and the lock structure would be automatically
> destroyed when the function is exited since the lock was local to the
> function.
The pthread implementation of FreeBSD I tested allocated memory for a
lock. That was the reason for the leak, and that was why the
"Windows-specific" fix also helps FreeBSD (that happens to use pthread
locks instead of atomic operations).
---
JINMEI, Tatuya
Internet Systems Consortium, Inc.
More information about the bind-users
mailing list