Date: Sat, 16 Aug 2025 01:53:16 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Warner Losh <imp@bsdimp.com> Cc: FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD Release Engineering Team <re@freebsd.org> Subject: Re: jemalloc 5.3.0 upgrade Message-ID: <aJ-6XKWQpuwaY1j6@kib.kiev.ua> In-Reply-To: <CANCZdfrYrboDRQqmzrX2YSpwHUcn0gCLtuoxamcyvruNMG5shQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Fri, Aug 15, 2025 at 03:56:05PM -0600, Warner Losh wrote: > After much delay, I've landed jemalloc 5.3.0 into main. > > This is likely the last update of jemalloc since the upstream is, at best, > in turmoil, and at worst dead. > > I tried to completely automate all the details of the upgrade, but only got > so far. I did the rest of the upgrade by hand (described in > FREEBSD-upgrade). I'd held off landing this until I had that, but once it > was clear this was likely the last time we'd need this, I just did the last > few steps by hand. I did this to make it easier to audit to ensure that the > pull request we got for this (which I redid, but compared to the original) > didn't sneak something in. Others can audit me as well. > > I've run this with a netflix workload and my developer workload with no > regressions. Did you tested new malloc with LA57 enabled on amd64?home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aJ-6XKWQpuwaY1j6>