Date: Mon, 12 Dec 2005 04:22:41 +0100 From: Johan Bucht <bucht@acc.umu.se> To: Jason Evans <jasone@canonware.com> Cc: current@freebsd.org Subject: Re: New libc malloc patch Message-ID: <439CED01.9050108@acc.umu.se> In-Reply-To: <439CEB74.9080505@acc.umu.se> References: <20051212014852.GA8775@shaka.acc.umu.se> <9FAD2B4B-C167-42D7-A8E7-BE03F4C07543@canonware.com> <439CEB74.9080505@acc.umu.se>
next in thread | previous in thread | raw e-mail | index | archive | help
Johan Bucht wrote: >>> * Fork safety functions >>> Nice to have for all allocators and is something I missed having. >>> Would >>> like to have them regardless if your malloc becomes standard or not. >> >> >> >> I think that the implementation is currently fork-safe. The threads >> libraries call _malloc_prefork() and _malloc_postfork() in order to >> avoid locking issues. >> > Hmm, I meant that the _malloc_prefork() functions are independent from > your malloc allocation and I would like them committed regardless as > they make the life easier for other malloc implementation. Bah, the libc bits not the actual functions of course. =) Should probably go to sleep instead of writing semi-understandable sentences. /Johan Bucht
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?439CED01.9050108>