Date: Fri, 15 Aug 2025 17:16:09 -0600 From: Warner Losh <imp@bsdimp.com> To: Konstantin Belousov <kostikbel@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD Release Engineering Team <re@freebsd.org> Subject: Re: jemalloc 5.3.0 upgrade Message-ID: <CANCZdfpunskYWYFqcNcm6zrtR6ej-Jzp%2BQ9Wr_T8VSgVb-ECsw@mail.gmail.com> In-Reply-To: <aJ-6XKWQpuwaY1j6@kib.kiev.ua> References: <CANCZdfrYrboDRQqmzrX2YSpwHUcn0gCLtuoxamcyvruNMG5shQ@mail.gmail.com> <aJ-6XKWQpuwaY1j6@kib.kiev.ua>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Fri, Aug 15, 2025, 4:53 PM Konstantin Belousov <kostikbel@gmail.com> wrote: > 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? > Not on purpose. Can you? Warner [-- Attachment #2 --] <div dir="auto"><div><br><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, Aug 15, 2025, 4:53 PM Konstantin Belousov <<a href="mailto:kostikbel@gmail.com">kostikbel@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Aug 15, 2025 at 03:56:05PM -0600, Warner Losh wrote:<br> > After much delay, I've landed jemalloc 5.3.0 into main.<br> > <br> > This is likely the last update of jemalloc since the upstream is, at best,<br> > in turmoil, and at worst dead.<br> > <br> > I tried to completely automate all the details of the upgrade, but only got<br> > so far. I did the rest of the upgrade by hand (described in<br> > FREEBSD-upgrade). I'd held off landing this until I had that, but once it<br> > was clear this was likely the last time we'd need this, I just did the last<br> > few steps by hand. I did this to make it easier to audit to ensure that the<br> > pull request we got for this (which I redid, but compared to the original)<br> > didn't sneak something in. Others can audit me as well.<br> > <br> > I've run this with a netflix workload and my developer workload with no<br> > regressions.<br> <br> Did you tested new malloc with LA57 enabled on amd64?<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Not on purpose. Can you?</div><div dir="auto"><br></div><div dir="auto">Warner</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> </blockquote></div></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpunskYWYFqcNcm6zrtR6ej-Jzp%2BQ9Wr_T8VSgVb-ECsw>