Date: Mon, 14 May 2007 16:12:24 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Jason Evans <jasone@freebsd.org> Cc: Robert Watson <rwatson@FreeBSD.org>, freebsd-arch@freebsd.org Subject: Re: Multiple malloc(3)s (was Re: HEADS DOWN) Message-ID: <20070514201224.GA5386@xor.obsecurity.org> In-Reply-To: <4648B65A.2040803@freebsd.org> References: <20070512153532.GQ21795@elvis.mu.org> <63984.1178992555@critter.freebsd.dk> <f25m78$ik$2@sea.gmane.org> <20070513215442.GZ21795@elvis.mu.org> <46478C9A.9050807@fer.hr> <20070514132901.X24765@fledge.watson.org> <4648B65A.2040803@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 14, 2007 at 12:19:54PM -0700, Jason Evans wrote: > Robert Watson wrote: > >I have to admit, > >however, that I do wish we'd retained an easy switch to let us go back > >and forth between phkmalloc and jemalloc for comparison purposes. > > It is pretty easy to go back and forth for comparison purposes, because > revision 1.92 of src/lib/libc/stdlib/malloc.c is a source-compatible > version of phkmalloc. You can update just that one file and get a libc > with phkmalloc instead of jemalloc. I continue to make use of this for > performance testing purposes, and it remains a sound strategy for > diagnosing possible regressions. I can confirm how trivial this is to do - it is indeed only one file that needs to be reverted, and you can even install it as a separate libc (e.g. in /tmp) and use LD_LIBRARY_PATH, libmap.conf, etc to direct access to it on a per-application basis. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070514201224.GA5386>