From nobody Tue Jun 10 15:40:43 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 4bGtLK18FHz5xq3V for ; Tue, 10 Jun 2025 15:41:13 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: from mail-yw1-f174.google.com (mail-yw1-f174.google.com [209.85.128.174]) (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 4bGtLJ3QN1z3WDg for ; Tue, 10 Jun 2025 15:41:12 +0000 (UTC) (envelope-from 6yearold@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-f174.google.com with SMTP id 00721157ae682-70e4043c5b7so47648787b3.1 for ; Tue, 10 Jun 2025 08:41:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749570071; x=1750174871; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=MnQ/0sec0AY0c3GG4bktPK3g8h5pFQBCVwBPGDaX2p0=; b=FGB2ETCN7oyQvB/J4iiYF9tXaEFZPQkuUpIanLRMwX3xzb0JD3mn08K/pFwUrb2DAq T5yranpM6NrayxLpKCc8S92a8W8kFf3cgfa1pvyJQZEllDLkyIro+9MFQ5AYzNcWu35K yiZCjaYnQFLM5xRIsmhUUSu3jO6kCd+CTylJLbvs3InUp5JNj5BgnSX0d+XuUeActUbX JuWWVSy602UoQfiu+NJKBfgc9l2YvFrw8Q8RGOia/47g7UlkgVdGNYftmhBwRvt6PcZQ cTS+kqu3cdxmHnZf8lKw4vMB+1ZCimAxGG73R/0kEDRGd8sY5TYl2XsccWkJhRaJ/hY+ dlgw== X-Gm-Message-State: AOJu0YxCXOWxShBxPPbGGV1ygbwWDlacXPSw5leBnMpbFF/iUupvkBZL YErvBhFDzmT0pAMPFNrQr22KUvp6WcMxD6GzUGTgNj93hdNR2GpTZeuxCEYBDU8T X-Gm-Gg: ASbGnct38avR7mFiGN9ct3PXcNtxL7okjRlfqwHgwcqXye5XkC6V0H3E6Q3TPMjeX8L 92fqDT2WdL5W7e9LBcSevIueAHINGmOQwbJnwHH2b73SEODB9WnVpKeT3NcMGVtnmF+quYmM0Cn 7lxv3Xjg2R8Usgi3UKDDMivCX4xLcVEW0vjI1l0u8q2m2XQAXkiMSkmjDZH7ktzW4Dawgb2Hqva mhZ9Op8TDa9xHJiC5NvpVuvibJdT+lOSwecfcSJ3Q3aw/NwrWjGkSxqgSuIJEcU2zfDiytAMD78 x5FdeLE/9Szo74kf1NvzfS8fjeiDZN3pfHLEEjhhJpGgqoCFa18wWoe4bgjFCx0NLX/YvpeRYgp hzvrjOuRMqyDJq3nleiNUz2x6aA== X-Google-Smtp-Source: AGHT+IEUbnMvyxZM7C+cFiuV2PdDUshgAAtB35n+8udTYWVMneyOAzRp1L3nELX4koPDh0xaQnroow== X-Received: by 2002:a05:690c:6e07:b0:70e:7882:ea91 with SMTP id 00721157ae682-710f77360e7mr262777047b3.35.1749570071409; Tue, 10 Jun 2025 08:41:11 -0700 (PDT) Received: from mail-yb1-f173.google.com (mail-yb1-f173.google.com. [209.85.219.173]) by smtp.gmail.com with ESMTPSA id 00721157ae682-710f99e8c63sm16543497b3.60.2025.06.10.08.41.11 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 10 Jun 2025 08:41:11 -0700 (PDT) Received: by mail-yb1-f173.google.com with SMTP id 3f1490d57ef6-e812c817de0so5023291276.0 for ; Tue, 10 Jun 2025 08:41:11 -0700 (PDT) X-Received: by 2002:a05:6902:72e:b0:e81:78f7:5521 with SMTP id 3f1490d57ef6-e81fd92a3f2mr110527276.6.1749570071005; Tue, 10 Jun 2025 08:41:11 -0700 (PDT) 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 References: In-Reply-To: From: Gleb Popov Date: Tue, 10 Jun 2025 18:40:43 +0300 X-Gmail-Original-Message-ID: X-Gm-Features: AX0GCFvpvcLYMSW1JKq2GjEUGARATGbLG2IZq0MCjxnlW-jOTudJUkc6mLlAL14 Message-ID: Subject: Re: Future of jemalloc on FreeBSD after archive To: Minsoo Choo Cc: FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4bGtLJ3QN1z3WDg 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:209.85.128.0/17, country:US] On Mon, Jun 9, 2025 at 11:08=E2=80=AFPM 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.