Date: Mon, 9 Jun 2025 17:17:10 -0600 From: Warner Losh <imp@bsdimp.com> To: Minsoo Choo <minsoochoo0122@proton.me> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: Future of jemalloc on FreeBSD after archive Message-ID: <CANCZdfpgLQD0sC3Hsuy542b1K%2BSpNA8xLGZ96XoOZhhLc1%2Buhg@mail.gmail.com> In-Reply-To: <sLUPmdWvgjaNJL3ly0NC29emSncHWcPnwkuqJ_v_T2_OsBK9BtdJcm17AeGD-2VBZp7gLEpMis-PiJG7zOueEcBhfVIlIpSVNKWfEgmKFn4=@proton.me>
index | next in thread | previous in thread | raw e-mail
I still think it would be useful to import the version that Minsoo started (I've re-created the import he did in a way I (or anybody) can 100% audit).. I've not had the couple of adjacent days to get this in... It's >< close. I'm unsure what to do in the future. What are all the cool kids using today? Warner On Mon, Jun 9, 2025 at 2:08 PM Minsoo Choo <minsoochoo0122@proton.me> wrote: > > As of June 2, 2025, jemalloc repository on Github has been archived. [1] > I have a differential revision open for jemalloc 5.3.0 [2], but have no idea how we will fix bugs and improve jemalloc on FreeBSD after the archive. > > We could fork the repository to freebsd/jemalloc and continue to develop by ourselves. Then, we need to build our own CI systems for jemalloc to test on macOS/Linux as well. > > I CC'ed Warner as he guided me for D41421, so I'm seeking for his advice this time as well. > > [1] https://github.com/jemalloc/jemalloc > [2] https://reviews.freebsd.org/D41421help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpgLQD0sC3Hsuy542b1K%2BSpNA8xLGZ96XoOZhhLc1%2Buhg>
