Date: Tue, 10 Jun 2025 12:47:26 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: David Chisnall <theraven@FreeBSD.org> Cc: Warner Losh <imp@bsdimp.com>, Minsoo Choo <minsoochoo0122@proton.me>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: Future of jemalloc on FreeBSD after archive Message-ID: <202506101247.55AClQIF030588@critter.freebsd.dk> In-Reply-To: <44DDF236-0911-4CE8-AD30-5E1AB5CB25EB@FreeBSD.org> References: <sLUPmdWvgjaNJL3ly0NC29emSncHWcPnwkuqJ_v_T2_OsBK9BtdJcm17AeGD-2VBZp7gLEpMis-PiJG7zOueEcBhfVIlIpSVNKWfEgmKFn4=@proton.me> <CANCZdfpgLQD0sC3Hsuy542b1K%2BSpNA8xLGZ96XoOZhhLc1%2Buhg@mail.gmail.com> <44DDF236-0911-4CE8-AD30-5E1AB5CB25EB@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
-------- David Chisnall writes: > I've replaced jemalloc with snmalloc (to which I am a contributor) It looks interesting, but rather than all of us having to do our own homework, can you give us the "elevator pitch" for it ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202506101247.55AClQIF030588>