Date: Wed, 4 Mar 2026 18:04:39 +0900 From: dikshie <dikshie@gmail.com> To: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: jemalloc 5.3.0 upgrade Message-ID: <CAA1TSu_61d4f2%2BcoWWYqqxcvSNRcBO%2BsAMsJqRx_sZF8ATTRoA@mail.gmail.com> In-Reply-To: <ouy5xeom8hi.fsf@panix3.panix.com> References: <CANCZdfrYrboDRQqmzrX2YSpwHUcn0gCLtuoxamcyvruNMG5shQ@mail.gmail.com> <ouy5xeom8hi.fsf@panix3.panix.com>
index | next in thread | previous in thread | raw e-mail
replying to an old thread. On Sat, Aug 16, 2025 at 9:11 AM Carl Shapiro <cshapiro@panix.com> wrote: > > Warner Losh <imp@bsdimp.com> writes: > > > This is likely the last update of jemalloc since the upstream is, at best, in > > turmoil, and at worst dead. > > Most of the jemalloc development over the past few years has been done > by engineers at Meta. Development actively continues in this repository > > https://github.com/facebook/jemalloc/ Now, Facebook has unarchived the original jemalloc. I just read the announcement in facebook's blog: https://engineering.fb.com/2026/03/02/data-infrastructure/investing-in-infrastructure-metas-renewed-commitment-to-jemalloc/ > The intention, even prior to the archiving, has been to do a major > release after HPA improvements have landed. In all likelihood, the > release will happen in the fork. Best Regards, -- -dikshie-home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAA1TSu_61d4f2%2BcoWWYqqxcvSNRcBO%2BsAMsJqRx_sZF8ATTRoA>