Date: Mon, 06 Aug 2012 21:56:44 -0500 From: Bryan Drewery <bdrewery@freebsd.org> To: Peter Jeremy <peter@rulingia.com> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r302135 - in head/devel: . lockfree-malloc Message-ID: <502083EC.1050305@FreeBSD.org> In-Reply-To: <20120807012458.GB25854@server.rulingia.com> References: <201208052051.q75Kpl6E025458@svn.freebsd.org> <20120807012458.GB25854@server.rulingia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/6/2012 8:24 PM, Peter Jeremy wrote: > On 2012-Aug-05 20:51:47 +0000, Bryan Drewery <bdrewery@freebsd.org> wrote: >> Log: >> lockfree-malloc is a scalable drop-in replacement for malloc/free. >> >> * It's thread-friendly. It supports a practically-unlimited number of >> concurrent threads, without locking or performance degradation. >> * It's efficient, especially in a multi-threaded environment. Compared to >> a stock libc allocator, we see a significant performance boost. >> * It does NOT fragment or leak memory, unlike a stock libc allocator. >> * It wastes less memory. For small objects (less than 8kb in size), the >> overhead is around 0 bytes. (!) > > Are these claims relative to the FreeBSD base malloc (jemalloc) or > some other malloc (presumably the one in glibc)? I suspect the > latter but as currently written, it implies they are shortcomings > in the former. > I believe the claims are directed at glibc malloc. It's was designed for Linux usage and ported over to FreeBSD. -- Regards, Bryan Drewery bdrewery@freenode/EFNet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?502083EC.1050305>