Date: Fri, 21 Nov 1997 15:56:25 -0600 (CST) From: Alex Nash <nash@Mcs.Net> To: Curtis Bray <cbray@best.com> Cc: freebsd-hackers@freebsd.org Subject: Re: malloc() problems in children after using rfork() Message-ID: <Pine.BSF.3.95.971121155158.2450K-100000@Jupiter.Mcs.Net> In-Reply-To: <Pine.BSF.3.96.971121133610.10841A-100000@shell5.ba.best.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 21 Nov 1997, Curtis Bray wrote: > From what I'd seen in the mail list archives, it appears the rfork() > method may work better for these IO bound applications. I was assuming > that once the RFMEM flag was set, then the VM system would respect > multiple children sharing the same address space. That's what I've > gotten from the man pages anyway: The problem is not with the VM system, but with the C library's malloc() routine (lib/libc/stdlib/malloc.c). The malloc routines have several critical sections within them which are unprotected when using the single threaded library. Alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.971121155158.2450K-100000>