From nobody Tue Jun 10 16:53:39 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 4bGvy95ycjz5xwfj for ; Tue, 10 Jun 2025 16:53:53 +0000 (UTC) (envelope-from bakul@iitbombay.org) Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bGvy945zRz3m0d for ; Tue, 10 Jun 2025 16:53:53 +0000 (UTC) (envelope-from bakul@iitbombay.org) Authentication-Results: mx1.freebsd.org; none Received: by mail-pf1-x42f.google.com with SMTP id d2e1a72fcca58-748269b1076so293257b3a.3 for ; Tue, 10 Jun 2025 09:53:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iitbombay.org; s=google; t=1749574431; x=1750179231; darn=freebsd.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=DqavlESkrhy8OSOVuBNCKFdKMOBkUkYwN5p9bF52KLA=; b=C3apRVhrf169v/PrFuWN29KQMRGGgvaVe8Qj2NfoVYcRi1GxChEbfT/BNQriNE5X5C sc9B+o/0jDq12+OJmUZS49yCJDwUPZmagqKPnpshSVIU2EecULynCeVlZV2K9Htvf7Tu A6+3qDmwmTF8SP8iIOeMQYD8pwwZAhC2GE1cQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749574431; x=1750179231; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=DqavlESkrhy8OSOVuBNCKFdKMOBkUkYwN5p9bF52KLA=; b=TMW/+FmTHlwzcXq2VCJde8dsWLrmbRHlJKsSWuFjm0W3OO9QOacH4+qCONjddcdE/i 1vOjtOtjB7bhOQ8Mt/P+bWCPbzqRwBhMotonjGLLLj/zC+zHvGFGLZnoX4HgJXGv0jyz NuhKcej6seklor3qD/i2llk/Lx41fpNAV7KbdN8s2bygOIE6HT8RDd+JWhyn081adDXz Eua0Y1Io+ifrAuo3hAiNFyzE/NxwOSnM5Kc9IRZECLR1GvVKR4Ewjh6cEB/tjfDFBV0/ /i2vfo0N/AUHtDr8HeqCRLtRzB7sRoYZYfn8BOtHtAoTZN5yNmQ445AERCwhV3Qkxfo7 5HOQ== X-Forwarded-Encrypted: i=1; AJvYcCXg1jZ4B7TU0H4eflZTniU3Tmt7bfOufgQZqaeS95LNZxRKalmxgTtytX0akNPG1EcsC6W3GRtSN5vGQRHMziA=@freebsd.org X-Gm-Message-State: AOJu0Yw8jntZj6N3kv2/QcpMBvrg7wVlQOUvaTzahh+94hGorRK81UCE CXn1I/OmfKD25LV/nEr7d9A49G9LJ06mEArRDW9gV7gSflI/Mg/5/MZAQey3jvfFwA== X-Gm-Gg: ASbGncvm7+TE0Rh9aHvpFn7xhCVcPOiuXFFeaGlUmlsiAFFpt1fgcgULfYvsBL0MLFu BTeESNGEuhqMifngcC8h9RI2EvPUHOelf/D9+f3GS3xibX9I2eEsOC95dtcfY5Z0su9yPdQNZjw 4TESZjwjkR3wf9y3WDCD4gcFEF9A2Oo4zEdUxt9wrfrHN4xxzNg7D0QT+oqVmF0AUu4msi3CqHm 6vh77ccqHRTkVmK03bnLuwn91vJLy4VcyBGeLE/hIY8NFrRk8b50xXL0555jApsumR41u/+VKL7 g7cBHUpt/HJAwZWOYu7wUKdeSCs293RUedOpvbE7k5YutdDc663zvuM5gfzuaMe1vX7/llofnnm jL3WWQhaE6XhaHfRdFNNk6DHRu7odoZuyNLJUseqbdljvJ9SOf8mmBIa01y0= X-Google-Smtp-Source: AGHT+IGJ5ISQ4JbISnPcS5ICl3PQDQ6xqVSDK+QLA75ulMWKQPix2L7ympLg2bobsU1xJZ83bncY1A== X-Received: by 2002:a05:6a00:855:b0:748:3089:5265 with SMTP id d2e1a72fcca58-7486ce17e7bmr119841b3a.5.1749574431072; Tue, 10 Jun 2025 09:53:51 -0700 (PDT) Received: from smtpclient.apple (107-215-223-229.lightspeed.sntcca.sbcglobal.net. [107.215.223.229]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-7482b0ea29csm7625888b3a.152.2025.06.10.09.53.50 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Jun 2025 09:53:50 -0700 (PDT) Content-Type: text/plain; charset=utf-8 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 (Mac OS X Mail 16.0 \(3826.600.51.1.1\)) Subject: Re: Future of jemalloc on FreeBSD after archive From: Bakul Shah In-Reply-To: Date: Tue, 10 Jun 2025 09:53:39 -0700 Cc: Gleb Popov , Minsoo Choo , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: References: <19F76966-2365-4598-9E9F-FC37133D980B@iitbombay.org> To: Brooks Davis X-Mailer: Apple Mail (2.3826.600.51.1.1) X-Rspamd-Queue-Id: 4bGvy945zRz3m0d X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] On Jun 10, 2025, at 9:24=E2=80=AFAM, Brooks Davis = wrote: >=20 > On Tue, Jun 10, 2025 at 09:02:37AM -0700, Bakul Shah wrote: >> On Jun 10, 2025, at 8:40???AM, Gleb Popov wrote: >>>=20 >>> On Mon, Jun 9, 2025 at 11:08???PM Minsoo Choo = wrote: >>>>=20 >>>> As of June 2, 2025, jemalloc repository on Github has been = archived. [1] >>>=20 >>> 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. >>=20 >> =46rom https://x.com/nateberkopec/status/1930010446410723533 & = followups: >>=20 >> jemalloc mystery resolved: jemalloc has moved to the official = Facebook github organization >>=20 >> context: for the last 2+ years the primary maintainers of jemalloc = have been FB employees. this just formalizes Evans' stepping off the = project. >>=20 >> 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-13394= 532 >>=20 >> 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 >=20 > It's been maintained by Facebook forever so that's not a change. The change is it becomes the primary repo. > 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. My guess is, the "move" might not be possible if they already had a fork. AIUI, issues don't get transferred to a fork. But no idea really why they did what they did. I was just answering Gleb's question!=