From nobody Tue Jun 10 16:24:57 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4bGvJp4vkpz5xtVS for ; Tue, 10 Jun 2025 16:24:58 +0000 (UTC) (envelope-from brooks@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bGvJp4R1Gz3gQZ; Tue, 10 Jun 2025 16:24:58 +0000 (UTC) (envelope-from brooks@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1749572698; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Jco+dcsHYD5wsvkqqxQn5HHC4aF2F4WPyEwuliEKt8A=; b=FcZGnxZsC2zC6QyNWEEefH3RGRezfqBLj1FtA4MZIIkLD3ENhz2tJ4pmSX8Bo0HTqBu+jy CqihrDxG04CoRFNBlrBWoDRiGMudeQU3Ck6NV7C4IeuahJx17Pbw8x4sHlvq5xVTcY+Q7b xvc+sjLSx66OKMeQ44pKKB7MmKDGEIoSPvYNz2T7Su1HSRlyyUvZEf50jER2wkjgkdKlUf WXNP/67MGShIYzVOuhGsLJ3eJ07gWO7/ughS9KAIjXj9FM72G9xKs6mw8atUELMjvrvRbY oPWcamB1Sptx7GZIDtPH11JWZBVOFOd61adib1jgQ1OIsWWECOl1ZcIsF5xVhg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1749572698; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Jco+dcsHYD5wsvkqqxQn5HHC4aF2F4WPyEwuliEKt8A=; b=P/uSUG6EcFYAGodaQwCXj4STa4S87au1A5yLexz8URX2MWZsQXdixOOsjG2sDUQ3OrABcD 1qu+gIMtiGhcyFfzgkInhrVBsTVVt7uy1BxoSz+ohIgJw+V+skzPk+06Y7nwt31lrVphbN 2VveIn4sy46tMGGN7F4n12VZvr8ErKd/IWxTkZTM1y+d12Id/8f3LPqdvErHvedhfq+xcD sy2zl20XEFVNZ72Tv//IKotDAK3TvRz+wKgNcccxeEehaRjoszGZ8dTxhWNIosABYMhGKz Pa/3CRZhz9JsAmWf/aPWf8fIQjGwQ+6U5Em1x1p0DuHN15kMTyT397z3BM81vg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1749572698; a=rsa-sha256; cv=none; b=arYDywrw8XXRwoG21T2N+MGNQd1in+2uVItO8JTzKZ5XCjc8Ru55XOr5Glhw9pbDLedvUK bCfkXp7m1zLOtnkSK0Mw1I9uBL3AYm3RP086O5EO6v/oEFWGNCAdc/M5wfNJDGwjSyOj6C wRRMLkOLu5CAHAQxeOF7n4epwi9TCA7clICajRMZhfWblRgYZD3Wl5dH2vulo4tq2xHrLK /vsq8CnX2tF6oOnIpnLSkcdikmCqK5o54XONVvmO7ksh76w7cW0XscsS6hhhlwojwUfbPX bizjlU4J7mQH7mCYEu9WSf6PUVLdgT+GEScRxAZYsGoeBJL+wMKV8y9XWmBOGQ== Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: brooks/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4bGvJp3YVbzJcc; Tue, 10 Jun 2025 16:24:58 +0000 (UTC) (envelope-from brooks@freebsd.org) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id E03E13C01A0; Tue, 10 Jun 2025 16:24:57 +0000 (UTC) Date: Tue, 10 Jun 2025 16:24:57 +0000 From: Brooks Davis To: Bakul Shah Cc: Gleb Popov , Minsoo Choo , FreeBSD Current Subject: Re: Future of jemalloc on FreeBSD after archive Message-ID: References: <19F76966-2365-4598-9E9F-FC37133D980B@iitbombay.org> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <19F76966-2365-4598-9E9F-FC37133D980B@iitbombay.org> On Tue, Jun 10, 2025 at 09:02:37AM -0700, Bakul Shah wrote: > On Jun 10, 2025, at 8:40???AM, Gleb Popov wrote: > > > > On Mon, Jun 9, 2025 at 11:08???PM Minsoo Choo wrote: > >> > >> As of June 2, 2025, jemalloc repository on Github has been archived. [1] > > > > Is there any explanation why it got archived? It feels surprising as I > > recently heard news that Qt added some code to take advantage of > > jemalloc-specific functions. > > From https://x.com/nateberkopec/status/1930010446410723533 & followups: > > jemalloc mystery resolved: jemalloc has moved to the official Facebook github organization > > context: for the last 2+ years the primary maintainers of jemalloc have been FB employees. this just formalizes Evans' stepping off the project. > > jemalloc???s not dead ! The Meta fork is the new home, ???still actively developing here??? but issues now have to go in discussions https://github.com/facebook/jemalloc/discussions/7#discussioncomment-13394532 > > Contributor commit info shows pretty abrupt handoff from Jason Evans to Qi Wang (interwq) and David Goldblatt in 2017, so I presume this ???small team??? was primarily these 2. Note Qi Wang???s contributions tapering off, David stopped post-pandemic: LinkedIn says he left Meta in 2024 It's been maintained by Facebook forever so that's not a change. Why not move the repo or break the fork so issues work? This feels like flailing around without understanding how github works and does not inspire confidence. -- Brooks