From nobody Mon Jun 9 09:15:21 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 4bG5rx4FQnz5xp2b for ; Mon, 09 Jun 2025 09:16:33 +0000 (UTC) (envelope-from wulf@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 4bG5rx3TYsz3TN7 for ; Mon, 09 Jun 2025 09:16:33 +0000 (UTC) (envelope-from wulf@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1749460593; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=KU39nrJLQpkilThRMAbC0GtzrGorCWHLzC2ZZ55PB48=; b=oGu8O4IjoNJOgMsEHSxwUqGZB9ButRVPPLtqnGPIx0zM8Iqewyy382W0e8FMbrI7JH36/b vly8SGh3QLkig0slu6nDAvUOOX8sAsTpRcwNc3Kkg2mE8Ujj3rTU6ZahpTqCt9zYDfj6fU jypwZJzvpZ4sx+PDd2Kvp4s8mZlI1zfcbUgCiChkJxQZJuPEuFhgBWhdE+FMhuxmqRzEiy ORwu/kcO+xYkY0UWfu9cUzm54TYIEPzFaqzX6L5dAlmPlC+dXipJfz3Ff+LhKwGDvnAnnF v07CGuaowQAw8FZzm/3/GHNwljYo8tRdEymaJxqvMrPgTB2sKQmjaPHgr6QXPg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1749460593; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=KU39nrJLQpkilThRMAbC0GtzrGorCWHLzC2ZZ55PB48=; b=XHgIJ2fZNArAYchZAy2msRp4jSnRkI8elAM3KasMoU+claO6j1bbmy8q2axJOcW+mxJ1ZC 6uu2/035E78vAaR2C5auFnFLUKSi2pVazZi8suuTqH4BlWr2DJgxuLAubgFM91ScYxm5qv d1jefur5r8rhiXjWZvp9q0DpoooomGt6ewvIIIQ2sYY7ZrdKay/WIFh8YLw8za1eBpgbNj fZegURg28TjYm9JXysCDRLDBmX/s4xn/XC6+m6zZXpkFRV0ajiJQ3AziI0lwANA3bOOeLE kNAAezL5GZmpBE5F6QOCUWvHlutXGSgi+qMcH8taa+qqALfLZ6rjotsXZWpbMw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1749460593; a=rsa-sha256; cv=none; b=NR+K49ZEwQtJYPerWmsHPH4ltQV0w5S7TwEwwxeFUBhG0oyvUIJ3EH4IWkKR9Ev9NKZOu9 uyE3/5PAh8OW50DaQp9sdS32B3k6X+HvqUESLsBV5bBh7R4LpH1Q5QSHvkOTUrfT70Iu+r JGFD+4Kr/34bXZDOCvK+O8DV4vo63HQ7faF85jy5c1MIPEY+oT6clspim+x/VHPV4Xu4HF Z7cCItwedSt49KEV7yQrtaHs7f0hVf/tk3cEEwXQ8rmQneP6EDde4WWy67pPNrGFV6qk6z k35x/E/WA+syO6+y3Ak4Sj5pHXCqno017aaYFp3e+Ylg1Wd32jKE8Zy8wtAo2A== Received: from [192.168.0.30] (unknown [94.45.192.132]) (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 did not present a certificate) (Authenticated sender: wulf) by smtp.freebsd.org (Postfix) with ESMTPSA id 4bG5rx0zxCz16Wf for ; Mon, 09 Jun 2025 09:16:32 +0000 (UTC) (envelope-from wulf@FreeBSD.org) Content-Type: multipart/mixed; boundary="------------o7DegHS0FylXrwq8lvGxA2Jq" Message-ID: <914a8f32-3e82-4ec6-bba7-1ae1d812f9ac@FreeBSD.org> Date: Mon, 9 Jun 2025 12:15:21 +0300 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 User-Agent: Mozilla Thunderbird Subject: Re: Adding kqueue to /dev/dsp To: freebsd-current@freebsd.org References: <5a32b28b-97eb-43c1-82e0-e38e22a63822@tilda.center> Content-Language: en-US From: Vladimir Kondratyev In-Reply-To: <5a32b28b-97eb-43c1-82e0-e38e22a63822@tilda.center> This is a multi-part message in MIME format. --------------o7DegHS0FylXrwq8lvGxA2Jq Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 6/4/25 20:01, Goran Mekić wrote: > Hello, > > I already talked to christos@ and he's OK with me adding the support for kqueue > to /dev/dsp, but I never saw any docs on how to implement it in the kernel. > Could somebody advise on how to add kqueue support to existing device? I mean, > if you could point out the simple device code with kqueue support, I would be > glad to follow the logic there and learn, for start. Thank you! > > Regards, > meka > > Hi Goran, See attached patch. It enables kqueue support for psm(4) -- WBR Vladimir Kondratyev --------------o7DegHS0FylXrwq8lvGxA2Jq Content-Type: text/x-patch; charset=UTF-8; name="0001-psm-4-Add-kqueue-support.patch" Content-Disposition: attachment; filename="0001-psm-4-Add-kqueue-support.patch" Content-Transfer-Encoding: base64 RnJvbSAyZDRlZmQyNjViZmVhZWE4ZTQ0YzM0ZWU3OTZiNjlkOTlkM2IxMmM1IE1vbiBTZXAg MTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBWbGFkaW1pciBLb25kcmF0eWV2IDx3dWxmQEZyZWVC U0Qub3JnPgpEYXRlOiBUaHUsIDE1IE1heSAyMDI1IDA3OjUzOjU5ICswMzAwClN1YmplY3Q6 IFtQQVRDSF0gcHNtKDQpOiBBZGQga3F1ZXVlIHN1cHBvcnQKCi0tLQogc3lzL2Rldi9hdGti ZGMvcHNtLmMgfCA0NSArKysrKysrKysrKysrKysrKysrKysrKysrKysrKysrKysrKysrKysr KysrKwogMSBmaWxlIGNoYW5nZWQsIDQ1IGluc2VydGlvbnMoKykKCmRpZmYgLS1naXQgYS9z eXMvZGV2L2F0a2JkYy9wc20uYyBiL3N5cy9kZXYvYXRrYmRjL3BzbS5jCmluZGV4IGZiZDll YjYxZmVlLi5iNDI5Nzc3YTlkMCAxMDA2NDQKLS0tIGEvc3lzL2Rldi9hdGtiZGMvcHNtLmMK KysrIGIvc3lzL2Rldi9hdGtiZGMvcHNtLmMKQEAgLTYxNCw2ICs2MTQsNyBAQCBzdGF0aWMg ZF9yZWFkX3QJCXBzbXJlYWQ7CiBzdGF0aWMgZF93cml0ZV90CXBzbXdyaXRlOwogc3RhdGlj IGRfaW9jdGxfdAlwc21pb2N0bDsKIHN0YXRpYyBkX3BvbGxfdAkJcHNtcG9sbDsKK3N0YXRp YyBkX2txZmlsdGVyX3QJcHNta3FmaWx0ZXI7CiAKIHN0YXRpYyBpbnQJcHNtb3BlbihzdHJ1 Y3QgcHNtX3NvZnRjICopOwogc3RhdGljIGludAlwc21jbG9zZShzdHJ1Y3QgcHNtX3NvZnRj ICopOwpAQCAtNzY2LDYgKzc2Nyw3IEBAIHN0YXRpYyBzdHJ1Y3QgY2RldnN3IHBzbV9jZGV2 c3cgPSB7CiAJLmRfd3JpdGUgPQlwc213cml0ZSwKIAkuZF9pb2N0bCA9CXBzbWlvY3RsLAog CS5kX3BvbGwgPQlwc21wb2xsLAorCS5kX2txZmlsdGVyID0JcHNta3FmaWx0ZXIsCiAJLmRf bmFtZSA9CVBTTV9EUklWRVJfTkFNRSwKIH07CiAKQEAgLTE5NjIsNiArMTk2NCw3IEBAIHBz bWF0dGFjaChkZXZpY2VfdCBkZXYpCiAJc2MtPnN0YXRlID0gUFNNX1ZBTElEOwogCWNhbGxv dXRfaW5pdCgmc2MtPmNhbGxvdXQsIDApOwogCWNhbGxvdXRfaW5pdCgmc2MtPnNvZnRjYWxs b3V0LCAwKTsKKwlrbmxpc3RfaW5pdF9tdHgoJnNjLT5yc2VsLnNpX25vdGUsICZHaWFudCk7 CiAKIAkvKiBTZXR1cCBvdXIgaW50ZXJydXB0IGhhbmRsZXIgKi8KIAlyaWQgPSBLQkRDX1JJ RF9BVVg7CkBAIC0yMDczLDYgKzIwNzYsOCBAQCBwc21kZXRhY2goZGV2aWNlX3QgZGV2KQog CWRlc3Ryb3lfZGV2KHNjLT5jZGV2KTsKIAlkZXN0cm95X2RldihzYy0+YmRldik7CiAKKwlr bmxpc3RfY2xlYXIoJnNjLT5yc2VsLnNpX25vdGUsIDEpOworCWtubGlzdF9kZXN0cm95KCZz Yy0+cnNlbC5zaV9ub3RlKTsKIAljYWxsb3V0X2RyYWluKCZzYy0+Y2FsbG91dCk7CiAJY2Fs bG91dF9kcmFpbigmc2MtPnNvZnRjYWxsb3V0KTsKIApAQCAtNTIyOSw2ICs1MjM0LDcgQEAg cHNtc29mdGludHIodm9pZCAqYXJnKQogCQl3YWtldXAoc2MpOwogCX0KIAlzZWx3YWtldXBw cmkoJnNjLT5yc2VsLCBQWkVSTyk7CisJS05PVEVfTE9DS0VEKCZzYy0+cnNlbC5zaV9ub3Rl LCAwKTsKIAlpZiAoc2MtPmFzeW5jICE9IE5VTEwpIHsKIAkJcGdzaWdpbygmc2MtPmFzeW5j LCBTSUdJTywgMCk7CiAJfQpAQCAtNTI2Niw2ICs1MjcyLDQ1IEBAIHBzbXBvbGwoc3RydWN0 IGNkZXYgKmRldiwgaW50IGV2ZW50cywgc3RydWN0IHRocmVhZCAqdGQpCiAJcmV0dXJuIChy ZXZlbnRzKTsKIH0KIAorc3RhdGljIHZvaWQKK3BzbWZpbHRlcl9kZXRhY2goc3RydWN0IGtu b3RlICprbikKK3sKKwlzdHJ1Y3QgcHNtX3NvZnRjICpzYyA9IGtuLT5rbl9ob29rOworCisJ a25saXN0X3JlbW92ZSgmc2MtPnJzZWwuc2lfbm90ZSwga24sIDApOworfQorCitzdGF0aWMg aW50Citwc21maWx0ZXIoc3RydWN0IGtub3RlICprbiwgbG9uZyBoaW50KQoreworCXN0cnVj dCBwc21fc29mdGMgKnNjID0ga24tPmtuX2hvb2s7CisKKwlHSUFOVF9SRVFVSVJFRDsKKwor CXJldHVybiAoc2MtPnF1ZXVlLmNvdW50ICE9IDAgPyAxIDogMCk7Cit9CisKK3N0YXRpYyBj b25zdCBzdHJ1Y3QgZmlsdGVyb3BzIHBzbWZpbHRvcHMgPSB7CisJLmZfaXNmZCA9IDEsCisJ LmZfZGV0YWNoID0gcHNtZmlsdGVyX2RldGFjaCwKKwkuZl9ldmVudCA9IHBzbWZpbHRlciwK K307CisKK3N0YXRpYyBpbnQKK3BzbWtxZmlsdGVyKHN0cnVjdCBjZGV2ICpkZXYsIHN0cnVj dCBrbm90ZSAqa24pCit7CisJc3RydWN0IHBzbV9zb2Z0YyAqc2MgPSBkZXYtPnNpX2RydjE7 CisKKwlpZiAoa24tPmtuX2ZpbHRlciAhPSBFVkZJTFRfUkVBRCkKKwkJcmV0dXJuKEVPUE5P VFNVUFApOworCisJa24tPmtuX2ZvcCA9ICZwc21maWx0b3BzOworCWtuLT5rbl9ob29rID0g c2M7CisJa25saXN0X2FkZCgmc2MtPnJzZWwuc2lfbm90ZSwga24sIDEpOworCisJcmV0dXJu ICgwKTsKK30KKwogLyogdmVuZG9yL21vZGVsIHNwZWNpZmljIHJvdXRpbmVzICovCiAKIHN0 YXRpYyBpbnQgbW91c2VfaWRfcHJvYzEoS0JEQyBrYmRjLCBpbnQgcmVzLCBpbnQgc2NhbGUs IGludCAqc3RhdHVzKQotLSAKMi40OS4wCgo= --------------o7DegHS0FylXrwq8lvGxA2Jq-- From nobody Mon Jun 9 15:14:29 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 4bGFp83RpFz5yGTt for ; Mon, 09 Jun 2025 15:14:40 +0000 (UTC) (envelope-from meka@tilda.center) Received: from mail.nsd1.sysit.solutions (meka.rs [109.93.255.137]) (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) by mx1.freebsd.org (Postfix) with ESMTPS id 4bGFp70nP5z3gMh for ; Mon, 09 Jun 2025 15:14:39 +0000 (UTC) (envelope-from meka@tilda.center) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of meka@tilda.center designates 109.93.255.137 as permitted sender) smtp.mailfrom=meka@tilda.center; dmarc=pass (policy=reject) header.from=tilda.center Received: from [192.168.111.162] (hal9000.nsd.sysit.solutions [192.168.111.162]) by mail.nsd1.sysit.solutions (Postfix) with ESMTPSA id D68B9226D8 for ; Mon, 09 Jun 2025 15:14:29 +0000 (UTC) Message-ID: <80911279-fdc7-49e9-8f3d-3ff73ffa0785@tilda.center> Date: Mon, 9 Jun 2025 17:14:29 +0200 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 User-Agent: Mozilla Thunderbird Subject: Re: Adding kqueue to /dev/dsp To: freebsd-current@freebsd.org References: <5a32b28b-97eb-43c1-82e0-e38e22a63822@tilda.center> <914a8f32-3e82-4ec6-bba7-1ae1d812f9ac@FreeBSD.org> Content-Language: en-US From: =?UTF-8?Q?Goran_Meki=C4=87?= In-Reply-To: <914a8f32-3e82-4ec6-bba7-1ae1d812f9ac@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [0.98 / 15.00]; NEURAL_SPAM_LONG(1.00)[1.000]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; NEURAL_HAM_SHORT(-0.97)[-0.974]; R_MIXED_CHARSET(0.56)[subject]; DMARC_POLICY_ALLOW(-0.50)[tilda.center,reject]; R_SPF_ALLOW(-0.20)[+mx]; ONCE_RECEIVED(0.20)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:8400, ipnet:109.92.0.0/15, country:RS]; MID_RHS_MATCH_FROM(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4bGFp70nP5z3gMh X-Spamd-Bar: / > Hi Goran, > > See attached patch. It enables kqueue support for psm(4) > Thank you very much! This might be exactly what I needed! Regards, meka From nobody Mon Jun 9 20:08:13 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 4bGNJy50BTz5yQtl for ; Mon, 09 Jun 2025 20:08:18 +0000 (UTC) (envelope-from minsoochoo0122@proton.me) Received: from mail-43166.protonmail.ch (mail-43166.protonmail.ch [185.70.43.166]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits)) (Client CN "protonmail.com", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bGNJw6VWgz442C for ; Mon, 09 Jun 2025 20:08:16 +0000 (UTC) (envelope-from minsoochoo0122@proton.me) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=proton.me header.s=protonmail header.b=AhtX7bw0; spf=pass (mx1.freebsd.org: domain of minsoochoo0122@proton.me designates 185.70.43.166 as permitted sender) smtp.mailfrom=minsoochoo0122@proton.me; dmarc=pass (policy=quarantine) header.from=proton.me DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me; s=protonmail; t=1749499695; x=1749758895; bh=odbRNOny9ziiI19yjaxJyVEX8rydblq4Ys37qC4I5lE=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector: List-Unsubscribe:List-Unsubscribe-Post; b=AhtX7bw0lorDj1amAiwgzAhLyqlL4MMeQkr8CcAJaOw5yoAuk0Q3sfkrBaF+HkZOo hcF1fDNcYfN30cEZ0GLHmUtDmgE+Cx7P+EXCOkS6mzyCgyjsU5d2+qeqmF0900yhEP NIm3UoGySTNXKcCpjxpgVKdKatjG2O/hDJZuwof9F5vrxOzmAvolMyMhv5vW3wOYDt BCz2SQaiSf7s7798xOSwyQFfIcVM7m0TBIq7l0ZscbhMKhwBRJuqV6xKbzpk3My7Cq 9nv/kSp36IWW9TjAAkWKxmAmYy9bDkDdNobCUX5uO6NaZn+iLfEME/uRqvj3UUy4v/ DNIOcgjm1mKkA== Date: Mon, 09 Jun 2025 20:08:13 +0000 To: FreeBSD CURRENT , Warner Losh From: Minsoo Choo Subject: Future of jemalloc on FreeBSD after archive Message-ID: Feedback-ID: 45891198:user:proton X-Pm-Message-ID: ca020407ed3ee4239c2d04277ccb6b4fd2747290 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: multipart/alternative; boundary="b1=_7NCapZflgGGUT9HyaebuhBogan6kDgFPDKxduw4UddA" X-Spamd-Result: default: False [-1.07 / 15.00]; MIME_BASE64_TEXT_BOGUS(1.00)[]; NEURAL_HAM_LONG(-0.85)[-0.854]; NEURAL_SPAM_MEDIUM(0.78)[0.776]; NEURAL_HAM_SHORT(-0.69)[-0.694]; DMARC_POLICY_ALLOW(-0.50)[proton.me,quarantine]; RWL_MAILSPIKE_EXCELLENT(-0.40)[185.70.43.166:from]; R_SPF_ALLOW(-0.20)[+ip4:185.70.43.0/24]; R_DKIM_ALLOW(-0.20)[proton.me:s=protonmail]; MIME_BASE64_TEXT(0.10)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ARC_NA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[185.70.43.166:from]; ASN(0.00)[asn:62371, ipnet:185.70.43.0/24, country:CH]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MISSING_XM_UA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[proton.me:+] X-Rspamd-Queue-Id: 4bGNJw6VWgz442C X-Spamd-Bar: - --b1=_7NCapZflgGGUT9HyaebuhBogan6kDgFPDKxduw4UddA Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 QXMgb2YgSnVuZSAyLCAyMDI1LCBqZW1hbGxvYyByZXBvc2l0b3J5IG9uIEdpdGh1YiBoYXMgYmVl biBhcmNoaXZlZC4gWzFdCkkgaGF2ZSBhIGRpZmZlcmVudGlhbCByZXZpc2lvbiBvcGVuIGZvciBq ZW1hbGxvYyA1LjMuMCBbMl0sIGJ1dCBoYXZlIG5vIGlkZWEgaG93IHdlIHdpbGwgZml4IGJ1Z3Mg YW5kIGltcHJvdmUgamVtYWxsb2Mgb24gRnJlZUJTRCBhZnRlciB0aGUgYXJjaGl2ZS4KCldlIGNv dWxkIGZvcmsgdGhlIHJlcG9zaXRvcnkgdG8gZnJlZWJzZC9qZW1hbGxvYyBhbmQgY29udGludWUg dG8gZGV2ZWxvcCBieSBvdXJzZWx2ZXMuIFRoZW4sIHdlIG5lZWQgdG8gYnVpbGQgb3VyIG93biBD SSBzeXN0ZW1zIGZvciBqZW1hbGxvYyB0byB0ZXN0IG9uIG1hY09TL0xpbnV4IGFzIHdlbGwuCgpJ IENDJ2VkIFdhcm5lciBhcyBoZSBndWlkZWQgbWUgZm9yIEQ0MTQyMSwgc28gSSdtIHNlZWtpbmcg Zm9yIGhpcyBhZHZpY2UgdGhpcyB0aW1lIGFzIHdlbGwuCgpbMV0gaHR0cHM6Ly9naXRodWIuY29t L2plbWFsbG9jL2plbWFsbG9jClsyXSBodHRwczovL3Jldmlld3MuZnJlZWJzZC5vcmcvRDQxNDIx --b1=_7NCapZflgGGUT9HyaebuhBogan6kDgFPDKxduw4UddA Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 PGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6IEFyaWFsLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0 cHg7Ij5BcyBvZiBKdW5lIDIsIDIwMjUsIGplbWFsbG9jIHJlcG9zaXRvcnkgb24gR2l0aHViIGhh cyBiZWVuIGFyY2hpdmVkLiBbMV08L2Rpdj48ZGl2IHN0eWxlPSJmb250LWZhbWlseTogQXJpYWws IHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiPkkgaGF2ZSBhIGRpZmZlcmVudGlhbCByZXZp c2lvbiBvcGVuIGZvciBqZW1hbGxvYyA1LjMuMCBbMl0sIGJ1dCBoYXZlIG5vIGlkZWEgaG93IHdl IHdpbGwgZml4IGJ1Z3MgYW5kIGltcHJvdmUgamVtYWxsb2Mgb24gRnJlZUJTRCBhZnRlciB0aGUg YXJjaGl2ZS48L2Rpdj48ZGl2IHN0eWxlPSJmb250LWZhbWlseTogQXJpYWwsIHNhbnMtc2VyaWY7 IGZvbnQtc2l6ZTogMTRweDsiPjxicj48L2Rpdj48ZGl2IHN0eWxlPSJmb250LWZhbWlseTogQXJp YWwsIHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiPldlIGNvdWxkIGZvcmsgdGhlIHJlcG9z aXRvcnkgdG8gZnJlZWJzZC9qZW1hbGxvYyBhbmQgY29udGludWUgdG8gZGV2ZWxvcCBieSBvdXJz ZWx2ZXMuIFRoZW4sIHdlIG5lZWQgdG8gYnVpbGQgb3VyIG93biBDSSBzeXN0ZW1zIGZvciBqZW1h bGxvYyB0byB0ZXN0IG9uIG1hY09TL0xpbnV4IGFzIHdlbGwuPC9kaXY+PGRpdiBzdHlsZT0iZm9u dC1mYW1pbHk6IEFyaWFsLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0cHg7Ij48YnI+PC9kaXY+ PGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6IEFyaWFsLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0 cHg7Ij5JIENDJ2VkIFdhcm5lciBhcyBoZSBndWlkZWQgbWUgZm9yIEQ0MTQyMSwgc28gSSdtIHNl ZWtpbmcgZm9yIGhpcyBhZHZpY2UgdGhpcyB0aW1lIGFzIHdlbGwuPC9kaXY+PGRpdiBzdHlsZT0i Zm9udC1mYW1pbHk6IEFyaWFsLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0cHg7Ij48YnI+PC9k aXY+PGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6IEFyaWFsLCBzYW5zLXNlcmlmOyBmb250LXNpemU6 IDE0cHg7Ij5bMV0mbmJzcDs8c3Bhbj48YSB0YXJnZXQ9Il9ibGFuayIgcmVsPSJub3JlZmVycmVy IG5vZm9sbG93IG5vb3BlbmVyIiBocmVmPSJodHRwczovL2dpdGh1Yi5jb20vamVtYWxsb2MvamVt YWxsb2MiPmh0dHBzOi8vZ2l0aHViLmNvbS9qZW1hbGxvYy9qZW1hbGxvYzwvYT48L3NwYW4+PC9k aXY+PGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6IEFyaWFsLCBzYW5zLXNlcmlmOyBmb250LXNpemU6 IDE0cHg7Ij5bMl0mbmJzcDs8c3Bhbj48YSB0YXJnZXQ9Il9ibGFuayIgcmVsPSJub3JlZmVycmVy IG5vZm9sbG93IG5vb3BlbmVyIiBocmVmPSJodHRwczovL3Jldmlld3MuZnJlZWJzZC5vcmcvRDQx NDIxIj5odHRwczovL3Jldmlld3MuZnJlZWJzZC5vcmcvRDQxNDIxPC9hPjwvc3Bhbj48L2Rpdj48 ZGl2IGNsYXNzPSJwcm90b25tYWlsX3NpZ25hdHVyZV9ibG9jayIgc3R5bGU9ImZvbnQtZmFtaWx5 OiBBcmlhbCwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyI+DQo8L2Rpdj4NCg== --b1=_7NCapZflgGGUT9HyaebuhBogan6kDgFPDKxduw4UddA-- From nobody Mon Jun 9 21:29:10 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 4bGQ6M5Wl8z5yWlM for ; Mon, 09 Jun 2025 21:29:15 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (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) by mx1.freebsd.org (Postfix) with ESMTPS id 4bGQ6L2dVlz42h4 for ; Mon, 09 Jun 2025 21:29:13 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Authentication-Results: mx1.freebsd.org; dkim=none ("invalid DKIM record") header.d=troutmask.apl.washington.edu header.s=troutmask header.b=NGzNlY1O; spf=none (mx1.freebsd.org: domain of sgk@troutmask.apl.washington.edu has no SPF policy when checking 128.95.76.21) smtp.mailfrom=sgk@troutmask.apl.washington.edu; dmarc=fail reason="No valid SPF" header.from=washington.edu (policy=none) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.18.1/8.18.1) with ESMTP id 559LTBuc078673; Mon, 9 Jun 2025 14:29:11 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) DKIM-Filter: OpenDKIM Filter v2.10.3 troutmask.apl.washington.edu 559LTBuc078673 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=troutmask.apl.washington.edu; s=troutmask; t=1749504551; bh=tZTk4gRwmvyJKI+Sv3DSZ9eS1BocbXdVsS5sX6TlUrw=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To:From; b=NGzNlY1OEE4x2VmX9tRGcuzfAvujlgbDQlC59ga4lJkMV2dx85dqTA0Xnmq9tDZGa /NVkJs55fWRm9yYqISNw0cmwhXjx442Njbf8p6l6wN2n5VFprA4iyabzPe/9znQAVB tv05BlQzxfko32ju5dZCkfWbHrGbkD6zcwy5jzSmykv0vTgA48dk53lvBhIdDK88j/ 86iOUk0ls4Bo8f6z8oMKSPC6UQKFj2/zLlPv17sQWzKlz02a8CJP2Gc4nvH0Z4YFdH u0gMlMEp5Iq69JtMj1EhWsfLGJlnYIPAdQ8m7V0ijxv8SOcnFVckoWgWi7leD8IpVz 5ST1gDF8Q2mkA== Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.18.1/8.18.1/Submit) id 559LTBCp078672; Mon, 9 Jun 2025 14:29:11 -0700 (PDT) (envelope-from sgk) Date: Mon, 9 Jun 2025 14:29:10 -0700 From: Steve Kargl To: Steve Kargl Cc: freebsd-current@freebsd.org Subject: Re: drm panic after new world Message-ID: Reply-To: sgk@troutmask.apl.washington.edu References: <4699f48c-f042-46fe-8f9a-419e86d51f58@comcast.net> <8605cb6d-4121-4733-bc5f-c66c6358ea04@comcast.net> <1qr36rs2-149o-574s-sp5o-8sno8o600o94@serrofq.bet> 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: X-Spamd-Result: default: False [-3.06 / 15.00]; NEURAL_HAM_MEDIUM(-0.98)[-0.982]; NEURAL_HAM_LONG(-0.95)[-0.950]; NEURAL_HAM_SHORT(-0.93)[-0.928]; RCVD_IN_DNSWL_MED(-0.20)[128.95.76.21:from]; MIME_GOOD(-0.10)[text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[washington.edu : No valid SPF,none]; REPLYTO_DOM_NEQ_TO_DOM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[no SPF record]; R_DKIM_PERMFAIL(0.00)[troutmask.apl.washington.edu:s=troutmask]; FREEMAIL_TO(0.00)[comcast.net]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[troutmask.apl.washington.edu:~]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; REPLYTO_ADDR_EQ_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; HAS_REPLYTO(0.00)[sgk@troutmask.apl.washington.edu] X-Rspamd-Queue-Id: 4bGQ6L2dVlz42h4 X-Spamd-Bar: --- On Fri, Jun 06, 2025 at 07:29:27PM -0700, Steve Kargl wrote: > > I've narrowed the range to > > Good: 2025-04-24 9b2a503a1179 - main - e6000sw: add support for 88E6190X > Bad: 2025-04-29 6c3a4b5f9b7b - main - alloca.3: move to share/man/man3 > > Good means boots and startx does not panic. dump_stack() in evergreen.c > reports one initialization event. > > Bad means boots and startx panics. dump_stack() in evergreen.c shows that > radeon is trying to initialized twice. > > The commit 28efbf9d2f67 is within this range, but I've run out of time > until monday. > Coming full circle. Comment #19 from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287165 I found it. It's markj's commit about jiffies. The four consecutive commits are 4fa275a5f357 -main- queue(3): Add simple tests for... Olivier Certner 325aa4dbd10d -main- linuxkpi: Introduce a properly typed jiffies Mark Johnston 901256f6ea3c -main- mlx5: jiffies is unsigned long Mark Johnston 87e57632bf88 -main- ofed: jiffies is unsigned long Mark Johnston 4fa275a boots, I can kldload radeonkms.ko, and startx brings up my desktop. In fact, I'm typing this in firefox at the moment. There is only dump_stack() message from evergreen.c 87e5763 boots, I can kldload radeonkmd.ko, and startx causes a panic. My custom kernel uses neither mlx5 nor ofed. That leaves 325aa4d as the commit causing an issue. There are two dump_stack() message from evergreen.c in /var/crash/core.txt.3 -- Steve From nobody Mon Jun 9 23:17:10 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 4bGSW90T4Kz5yfP7 for ; Mon, 09 Jun 2025 23:17:25 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (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 4bGSW86xgRz3xgn for ; Mon, 09 Jun 2025 23:17:24 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x1031.google.com with SMTP id 98e67ed59e1d1-311d27eb8bdso2971107a91.0 for ; Mon, 09 Jun 2025 16:17:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1749511042; x=1750115842; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=9jVN4xYBy5bYu8MYzAiHN4mx4H+g9u6xwo7H0SWV8Oc=; b=P9Np6DFT+MdqgOB7WM5rmGzQMNhvJreSOdxUeVEHvEpGnwaVNX6I73VWfhyZ7mMHrD amjIR4nEtX7y76fsZZKf3M+nkLS+ro/OBHRFJpn6SEZnwPeGHLfD2nFkOY8xA2ySbtXB G3DmeNeCOMaCDZ3uZFpwCo4EAGICUU420Hc0TJZXO3gBji2oAzaGkalgfr5+hPrWPn4Z yt0IR7Nb4DKslJ18R+nxEbBQD4ZwQtWcx2roLL39wU8GGPgWzobAIePHl+PhhPyPddXq gYNhKBL8HaZfXfDnUO2VrvE2qcEdxkmqH6/99uTR8NjgtvTcfPSWA3CRqpsNOpkoBVDs ThAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749511042; x=1750115842; 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=9jVN4xYBy5bYu8MYzAiHN4mx4H+g9u6xwo7H0SWV8Oc=; b=n6byqQO5TuJh4O6Y5uY5IyDtKPcEFq6OSpBMpMy5o2LaMVYELVC5JC84BJbGE6jAyG AvsV1mSCMcUQu13bO5XaXBeqlOOP69x09AZ5BahEnJy1DrByv/5Qe/8iiH2ADGMaG9uT FTcLofs7xHoNeYsGTJvURXpAQtn44238FvQ6f/VxR3U3isTtRh+dfehxBkUQhrfAfQWR KA7elJ8HK2zCUv6RKKQPoC0uwMfs/JI5kxGWVoO3zK/JM2LX+v1h51zndyDPRkusC2Pk HUl5aE6ZtlE01YZ8VjfVa9mDkg+M9fKIPTs5lPnF6NVYQ3H94Obh0z2tU+Sp96+iuapG jfNw== X-Gm-Message-State: AOJu0YyGhetCAh36ujkrzj2qUnewIBhgzukYRT4YXi2DauGxiKOgpzyG rTR7k4N7N6csMNOCkX0gYneRi4gzh+XAuSkJGBFzXS90Mzv42dxaMCLd19UDJvEWdyzvQFluWe+ 0OBTf21Vv+VdhTZd8svt39DeyGsaeKsEi0VaFAEGbfH1/G7PuShAmkmw= X-Gm-Gg: ASbGncvoIPAPeHbijfJghTMnpTuYJPpkW9tu3Y1aGKU6Ww+4zQQzFtYVx3g7pujEFwf kM0hHdrsIaiFZETV5suaNpZZGaO7nxKpG11XbbBeR9oCHauPjOC49twIusjiWCweqBtZuLYp2BZ yrVJgIRmH+oFDS/O5F7FOmOtCC4n8/+79BOkjV/DbqATggA7V4ekWa4Q== X-Google-Smtp-Source: AGHT+IFEJFVyThoJVkKIwGasDEgJ5qaDM4lsAStOY3aI8WbsIFB2sD3lK8ZnfM+MVX2Yiwi9O7ZgEKVVga++NCfVxV8= X-Received: by 2002:a17:90b:1d46:b0:312:1508:fb4d with SMTP id 98e67ed59e1d1-313a16faa81mr488102a91.33.1749511042178; Mon, 09 Jun 2025 16:17:22 -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: Warner Losh Date: Mon, 9 Jun 2025 17:17:10 -0600 X-Gm-Features: AX0GCFtBlMwmjHgIrVHJqXlzRsdH2Ro-Lx7CcevgCv-_yOVhgT9P9-Um1e2eM-o 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: 4bGSW86xgRz3xgn 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] 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=E2=80=AFPM Minsoo Choo 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 i= dea 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 tes= t 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/D41421 From nobody Tue Jun 10 07:15:02 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 4bGg6R5SKXz60FmD for ; Tue, 10 Jun 2025 07:15:11 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 4bGg6R3mbPz3Lmg; Tue, 10 Jun 2025 07:15:11 +0000 (UTC) (envelope-from theraven@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1749539711; 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=Bok184Mm7qstoG2FhvusVFhaTB4Aj3AU1IXwPexrvOs=; b=e5IgMbvH/KkEvkwSZcL65MRTdJcu1lPec4uLYTuSAb8/4FDSGJJhdY30gtF1bzpGjeuTVk CK4pYJuJFfxvMcIDMU6b1kr5wT5k3hxsQwzxhGR6YqGi8hPxZSM3qHf2cnjSWYkRJdHzBQ Z6AB8SHY7SM2bHb+0oIrTjIb6BvlBHOgqnBc1rkpZWI+jKOXfkKEz032qH0RaUylvSpNrF Q1ccKHgDFBo2L4G9xNhETMmPguMQTx7++bj7wOuwgIGzfyGtDiCtcyqD6CUvFrymRhIT2V mm/5LDQA8oN3gen0kzDJty4+aeaVImkkZVZ82xXJuMDFUmfceur3sda1Cvb5Qg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1749539711; 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=Bok184Mm7qstoG2FhvusVFhaTB4Aj3AU1IXwPexrvOs=; b=kYP+5VHEO4TvgCq2SY0inSkeCytYzVtCsPf3ANBef/K6fhR1NVtL0YQ3IdA8lLo1U/QB3G 67QHKSe98e8iRXgr0X/h0RfRwyDkXd02s6Wi4wPJPthgAZwIxaDvQhVH52VHu80JoNFsLT Jap6a3KrwcXN2VFDzhCnuFrQCCIMAUw7lZQz53ZWBvYdWXMcwDpizYinREiD10gei28PX/ 33kbq2CcgRVK/60JHAN4rzO3VVIiOG7dFCx4XgfIrmQStzkw5+bKhZMCtplHy4OBD/Xknp dL812/R0aRwo+h5kNr2k65Z35hdA3waebLJNGvIjfCEZFo9DuQiXUmNiez4vQg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1749539711; a=rsa-sha256; cv=none; b=Mrqq9JOl0Z8gSiduz+rUS/Bmf+BrFdRLvYveCcGlq4Gfi7XT8SjtmDo7Kdi43hcx78QZiZ KOC5CBKbT2Uo14ruPuG/7HAyp6qvqyeY9KAh5+sKv+e8F9s6Z2l9oYJnWc54cHmEVBr2kU H0ne30VJfniBEN379LkSZIrgiBakKMCRIaKwO+4dpC3k2WXXkL1KW8QB1+0wGfSwBvD4zT lFmxD3E19JfCnr+DE9JsDizQ+eT3nE4AyWycVjrqnVgwkg8nF4ke1uFdG3rrSAY8zycnNv jbhr5YfzrRj/DTAQkVyz5cSFKmRujVw1GoDckFsLcxeCbdsTH6y2F5QspB+ZHA== Received: from smtp.theravensnest.org (smtp.theravensnest.org [45.77.103.195]) (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: theraven) by smtp.freebsd.org (Postfix) with ESMTPSA id 4bGg6R1nrwz6Tn; Tue, 10 Jun 2025 07:15:11 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtpclient.apple (host86-143-41-189.range86-143.btcentralplus.com [86.143.41.189]) by smtp.theravensnest.org (Postfix) with ESMTPSA id 9D0A5110DB; Tue, 10 Jun 2025 08:15:10 +0100 (BST) From: David Chisnall Message-Id: <44DDF236-0911-4CE8-AD30-5E1AB5CB25EB@FreeBSD.org> Content-Type: multipart/alternative; boundary="Apple-Mail=_C41C6228-FC4D-43CC-AB37-68FC85CE7B7A" 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 \(3776.700.51.11.1\)) Subject: Re: Future of jemalloc on FreeBSD after archive Date: Tue, 10 Jun 2025 08:15:02 +0100 In-Reply-To: Cc: Minsoo Choo , FreeBSD CURRENT To: Warner Losh References: X-Mailer: Apple Mail (2.3776.700.51.11.1) --Apple-Mail=_C41C6228-FC4D-43CC-AB37-68FC85CE7B7A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On 10 Jun 2025, at 00:17, Warner Losh wrote: >=20 > I'm unsure what to do in the future. What are all the cool kids using = today? I=E2=80=99ve replaced jemalloc with snmalloc (to which I am a = contributor) in libc about five years ago and have been using that on a = few places. I believe Brooks imported a cleaned-up version of my = patches to CheriBSD and was planning on upstreaming them as an option. - For building llvm, snmalloc was around 2% faster. I didn=E2=80=99t = do much benchmarking because I was mostly on VMs but across SPEC on = Linux (where we did more benchmarking) we were typically faster than = jemalloc. - The libc binary is around 500 KiB smaller. - The HAL supports FreeBSD upstream (there=E2=80=99s also a HAL for = running snmalloc in the kernel too, but it is bitrotted). It=E2=80=99s = easy to tune things for performance or memory overhead. - It makes it easy to do fun things like allocate across trust = boundaries. We use this in the verona-sandbox project to easily = compartmentalise libraries with capsicum. We built snmalloc as a set of = tools to build allocators, rather than as a malloc. The same code can = be used to build specialised allocators. - It makes it easy to find the start and end of allocations. My = version has checks on memcpy and an older prototype did bounds checks on = things like sprintf and so on. These have around a 2% performance = overhead with checks on writes. I have some ifunc magic to dynamically = switch between the two versions for memcpy. Not that I=E2=80=99m biased or anything... David --Apple-Mail=_C41C6228-FC4D-43CC-AB37-68FC85CE7B7A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 On 10 Jun = 2025, at 00:17, Warner Losh <imp@bsdimp.com> = wrote:

I'm unsure what to do in the future. What = are all the cool kids using today?

I=E2=80=99ve replaced jemalloc = with snmalloc (to which I am a contributor) in libc about five years ago = and have been using that on a few places.  I believe Brooks = imported a cleaned-up version of my patches to CheriBSD and was planning = on upstreaming them as an option.

 - For = building llvm, snmalloc was around 2% faster.  I didn=E2=80=99t do = much benchmarking because I was mostly on VMs but across SPEC on Linux = (where we did more benchmarking) we were typically faster than = jemalloc.
 - The libc binary is around 500 KiB = smaller.
 - The HAL supports FreeBSD upstream (there=E2=80=99= s also a HAL for running snmalloc in the kernel too, but it is = bitrotted).  It=E2=80=99s easy to tune things for performance or = memory overhead.
 - It makes it easy to do fun things = like allocate across trust boundaries.  We use this in the = verona-sandbox project to easily compartmentalise libraries with = capsicum.  We built snmalloc as a set of tools to build allocators, = rather than as a malloc.  The same code can be used to build = specialised allocators.
 - It makes it easy to find the = start and end of allocations.  My version has checks on memcpy and = an older prototype did bounds checks on things like sprintf and so on. =  These have around a 2% performance overhead with checks on writes. =  I have some ifunc magic to dynamically switch between the two = versions for memcpy.

Not that I=E2=80=99m = biased or = anything...

David

= --Apple-Mail=_C41C6228-FC4D-43CC-AB37-68FC85CE7B7A-- From nobody Tue Jun 10 12:47:26 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 4bGpV03fHRz5xJgJ for ; Tue, 10 Jun 2025 12:47:36 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (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) by mx1.freebsd.org (Postfix) with ESMTPS id 4bGpTz5Ndyz4BFr; Tue, 10 Jun 2025 12:47:35 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Authentication-Results: mx1.freebsd.org; none Received: from critter.freebsd.dk (unknown [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id A9CDCB0A1A; Tue, 10 Jun 2025 12:47:27 +0000 (UTC) Received: (from phk@localhost) by critter.freebsd.dk (8.18.1/8.16.1/Submit) id 55AClQIF030588; Tue, 10 Jun 2025 12:47:26 GMT (envelope-from phk) Message-Id: <202506101247.55AClQIF030588@critter.freebsd.dk> To: David Chisnall cc: Warner Losh , Minsoo Choo , FreeBSD CURRENT Subject: Re: Future of jemalloc on FreeBSD after archive In-reply-to: <44DDF236-0911-4CE8-AD30-5E1AB5CB25EB@FreeBSD.org> From: "Poul-Henning Kamp" References: <44DDF236-0911-4CE8-AD30-5E1AB5CB25EB@FreeBSD.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-ID: <30586.1749559646.1@critter.freebsd.dk> Date: Tue, 10 Jun 2025 12:47:26 +0000 X-Rspamd-Queue-Id: 4bGpTz5Ndyz4BFr 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:1835, ipnet:130.225.0.0/16, country:EU] -------- David Chisnall writes: > I've replaced jemalloc with snmalloc (to which I am a contributor) It looks interesting, but rather than all of us having to do our own homework, can you give us the "elevator pitch" for it ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From nobody Tue Jun 10 12:53:30 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 4bGpcq5X78z5xJvW for ; Tue, 10 Jun 2025 12:53:31 +0000 (UTC) (envelope-from brooks@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 4bGpcq4rqXz4DjR; Tue, 10 Jun 2025 12:53:31 +0000 (UTC) (envelope-from brooks@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1749560011; 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=eFcTQ/b152Yda6HS4gdvKVzXhQ4BPZT43DtWJq191e8=; b=eqfSnnTVAnDgp76/14eVcW2BD9lXwJEr/YKWdkKPZC5Vw0CHgd2LlhEixYdDG9uJJLQDtU aiEn/WQ2khWkhR1NEqaPigImLSbwFjU8mTjqDHj9Mmv5ysFKapmFktUh6UbnOzNiAqlslF ff6ITxI+YqO9Jdc3GQOCRSUXwmpSZtsKtfpbMJzuUUXYosTlHlTObgR5gHcQvJ7fD3aRYO VjKXE5Nyo4bj3F+1Mi2VIDrm8ytEvAMyn2LvWxSlFAG6wyWXtcA6gPhBe8Ikdr/anD/6Dz +NgzwRIlLzRHbogsLImRPwafviMnJoE/1gR3DU6BFLgUji5UwsqY3NcLLgUX+A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1749560011; 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=eFcTQ/b152Yda6HS4gdvKVzXhQ4BPZT43DtWJq191e8=; b=vnM7J7Gqj1SJu7ekEhNaMRF95OJpBG07ThouH47nGGqr15tjcycmiKsipGL4LZEW7u0k99 cjINPhio1fVifTzDcn2aG4UbG4snRGTAntaxWh2s/VA0FJf1x4AbXyz2FZ0AVw27p+zcrT EwAHpl7vTwQi96wEb7DwlUGXKQFvEjKW2VxMSCZjGY6TWft9PjqrF/9F18XbizpoiNXEUM PgAFQrRtWjt23CqvsM+RfPgVdBHR6XetMJ2hZQO53fkmpiIsqmxttp7o162PayyyQta76K fr45jfRD/LkzJQVXzp0qbGxM0Hon8rzdIx09ZzcjJlzYTnPodVcHkIpsmvxw0A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1749560011; a=rsa-sha256; cv=none; b=JjAZYr1Sgq2PNEOUyiE6xIRYZWbJQ2klmy3W3fwzCig5jpiJbFKMO7PpIK7eOSs9d/ic3R xBF/cvk2Q4Si0vP/rofrTA6uqNpWGKhWcx8FfzEWDsdc3v6buAewPYPXAukShEZJppobqY tuKH0F34CLEfwj0eymiSXfzpQSVVzRlVskDkiNrwaMw618zAwjCTKFO2OggvXIHxpalKNK vEMZNc8yorEkJ5Cm1ZZTvpWCKdk9bsOLscVvseUyZ3DUkvfbXVkEgQnD037yRXJgMIlnLN xurNdvCMXJx4LV1vLyha3/Eg/fAbYy0LAlDaWITlkRnzJJgxa5VtrCI+veQgMA== 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 4bGpcq3lXCzDnZ; Tue, 10 Jun 2025 12:53:31 +0000 (UTC) (envelope-from brooks@freebsd.org) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id ED0803C01A0; Tue, 10 Jun 2025 12:53:30 +0000 (UTC) Date: Tue, 10 Jun 2025 12:53:30 +0000 From: Brooks Davis To: David Chisnall Cc: Warner Losh , Minsoo Choo , FreeBSD CURRENT Subject: Re: Future of jemalloc on FreeBSD after archive Message-ID: References: <44DDF236-0911-4CE8-AD30-5E1AB5CB25EB@FreeBSD.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: <44DDF236-0911-4CE8-AD30-5E1AB5CB25EB@FreeBSD.org> On Tue, Jun 10, 2025 at 08:15:02AM +0100, David Chisnall wrote: > On 10 Jun 2025, at 00:17, Warner Losh wrote: > > > > I'm unsure what to do in the future. What are all the cool kids using today? > > I???ve replaced jemalloc with snmalloc (to which I am a contributor) in libc about five years ago and have been using that on a few places. I believe Brooks imported a cleaned-up version of my patches to CheriBSD and was planning on upstreaming them as an option. > I've been doing infrastructure work for this as a background task due to a decision to switch back to a wrapped jemalloc for CheriBSD heap temporal safety work (at the time we were debugging too many different things at once and decided that wrapping jemalloc meant we were debugging fewer things). I think we should ship 15.0 with jemalloc, ideally updated to at least 5.3.0. I'd also like to deprecate all the jemalloc specific symbols for 15 by removing default versions. I've got a patch to do so, but probably need an exprun for it and maybe a shim library to allow linkage with those symbols. Longer term, pivoting to a malloc with better hardening is certainly the right thing to do and snmalloc is a candidate. -- Brooks From nobody Tue Jun 10 15:20:19 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 4bGstZ5713z5xn16 for ; Tue, 10 Jun 2025 15:20:38 +0000 (UTC) (envelope-from bakul@iitbombay.org) Received: from mail-pg1-x52b.google.com (mail-pg1-x52b.google.com [IPv6:2607:f8b0:4864:20::52b]) (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 4bGstY2m54z3RGY for ; Tue, 10 Jun 2025 15:20:37 +0000 (UTC) (envelope-from bakul@iitbombay.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=iitbombay.org header.s=google header.b=YqruY9zV; spf=pass (mx1.freebsd.org: domain of bakul@iitbombay.org designates 2607:f8b0:4864:20::52b as permitted sender) smtp.mailfrom=bakul@iitbombay.org; dmarc=pass (policy=quarantine) header.from=iitbombay.org Received: by mail-pg1-x52b.google.com with SMTP id 41be03b00d2f7-b2c43cbce41so582428a12.2 for ; Tue, 10 Jun 2025 08:20:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iitbombay.org; s=google; t=1749568831; x=1750173631; darn=freebsd.org; h=to:cc:date:message-id:subject:mime-version:from :content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=cimEinq69J6A4Il7bje7DF8Vw6KZQEtioJw6ApHZbpo=; b=YqruY9zVmnVl2i1l8E6ZovJ7QeCugpNr1SQ5qbRt8VGC3+KM1T7LVNg9PMH7qgWRkb 5XdsDYIkeCCgONyClyqbgWwqErFRJU3d3celpCh0btEXUiSmQ8GUzM53wUu9COPdPXvm 2tQcrbA9XAiggBOT1FH0bKsho1z/HEgAX3QkU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749568831; x=1750173631; h=to:cc:date:message-id:subject:mime-version:from :content-transfer-encoding:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=cimEinq69J6A4Il7bje7DF8Vw6KZQEtioJw6ApHZbpo=; b=n+mihSC9hh5Ti2NTKUMp5PYJXRHH/ws82oG3+Ek8iYa3XxHJtDlOnZ8i38lQKckMGC WWI+XsVYQRV9OdnxWREBb9CTe4jux3nMePB7N9nAXH7uwZnujGVUV6CYJ07ZWcpTncl4 N0gB/qCwlyqNrAfrWrg2omyC6vV/bkS4hdQvo9zvv3lhqK2ZfIIMzdiqLUwOta+RGCbb xKidfAakRiNnQdUnCa5YCHyXqtAL3kpRYcZtoj66HOvGO9YDrTjGVn94ZtF/vrk6uJcA qyIdoJ0+9p/8gh4PWsIMKH12E5eToHKnciq0L+Hl+HKKHJbCSEtdlxPnpjCD+Ivybme1 R2yQ== X-Forwarded-Encrypted: i=1; AJvYcCUfStB2yY82eoyh9pmguLVWssKX7KYN5VohizbYqx/DQ9/ocXzlrrKSkf61oTekesrVGbUoMR2sW+rR4CyA+14=@freebsd.org X-Gm-Message-State: AOJu0Yx88KByCjNULQtm9EupbTYMb97WQMQuw60tWRLONfKebD1Q0xxC dOr9I2j/JJuuER2G9UpmoPRk3SE6D8TXed8Suld0XQtHniLGwpeTqnf17ahrwMgLqHMQj4ujK7N mnIg= X-Gm-Gg: ASbGncvJ47T1Ojb0U6H9QOeDnGkn8yWkbu0P6xBoZSzEu3HdZN2eVAMwbkG8tN7sC1T x2JZfEBtvQDfPOCyyeLAOS9yq9X3iuBV5SzDnTwnwfjYe5vouJpjVZjXcbJldgDGUBOsPEU2sFe uQmwnMWGGft9nbd/i7+ncUFBP2V8+Oa004ZaNcoywV2YWmXEwVn9+cujlXGzJCbtEnrQR+pfsvd l3aNrJNsY50hDXURrMuI9vBnsdlP6t5Was+Smj/uB7f2llUBmeNwqakJFNvf5RZQwzkWh/YBSDL +BTti7GsPtfB5O9VEY70TbjTAAJ0U+pa6rf732QXPaT+WTVHR8XeMsbSKa/Zr65H+9+U+C6RB82 GBKS74EmY4ATLyGMpJ/oUPwu1FGZNY3+472KcrwT4QQP+i3PsK5YxTNAfQvQ= X-Google-Smtp-Source: AGHT+IFxle3kca2oOaijtOS0+3a8BHjBdJJ5s2HBY5MWuR8Wt8592I/1A+c/vUZzUxyf77hZllpHrw== X-Received: by 2002:aa7:9303:0:b0:730:915c:b70 with SMTP id d2e1a72fcca58-7486ca87bfemr18805b3a.0.1749568831084; Tue, 10 Jun 2025 08:20:31 -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-7482af7ab1fsm7784279b3a.54.2025.06.10.08.20.30 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 10 Jun 2025 08:20:30 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Bakul Shah 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 (1.0) Subject: Re: Future of jemalloc on FreeBSD after archive Message-Id: <584301BC-9EC6-4205-AB23-41C0EDF8F478@iitbombay.org> Date: Tue, 10 Jun 2025 08:20:19 -0700 Cc: Minsoo Choo , FreeBSD Current To: Warner Losh X-Mailer: iPad Mail (22F76) X-Spamd-Result: default: False [-2.98 / 15.00]; FAKE_REPLY(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; NEURAL_HAM_SHORT(-0.98)[-0.985]; DMARC_POLICY_ALLOW(-0.50)[iitbombay.org,quarantine]; R_DKIM_ALLOW(-0.20)[iitbombay.org:s=google]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[text/plain]; DKIM_TRACE(0.00)[iitbombay.org:+]; RCPT_COUNT_THREE(0.00)[3]; RCVD_COUNT_TWO(0.00)[2]; TO_DN_ALL(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; FREEFALL_USER(0.00)[bakul]; APPLE_IOS_MAILER_COMMON(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[FreeBSD-current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::52b:from] X-Rspamd-Queue-Id: 4bGstY2m54z3RGY X-Spamd-Bar: -- =EF=BB=BFLooks like there is https://github.com/facebook/Jemalloc See https://x.com/permutans/status/1931398314924150814 > On Jun 9, 2025, at 4:17=E2=80=AFPM, Warner Losh wrote: >=20 > 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. >=20 > I'm unsure what to do in the future. What are all the cool kids using toda= y? >=20 > Warner >=20 > On Mon, Jun 9, 2025 at 2:08=E2=80=AFPM Minsoo Choo wrote: >>=20 >> 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 i= dea how we will fix bugs and improve jemalloc on FreeBSD after the archive. >>=20 >> We could fork the repository to freebsd/jemalloc and continue to develop b= y ourselves. Then, we need to build our own CI systems for jemalloc to test o= n macOS/Linux as well. >>=20 >> I CC'ed Warner as he guided me for D41421, so I'm seeking for his advice t= his time as well. >>=20 >> [1] https://github.com/jemalloc/jemalloc >> [2] https://reviews.freebsd.org/D41421 From nobody Tue Jun 10 15:22:04 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 4bGswQ1XHqz5xnHw for ; Tue, 10 Jun 2025 15:22:14 +0000 (UTC) (envelope-from minsoochoo0122@proton.me) Received: from mail-43167.protonmail.ch (mail-43167.protonmail.ch [185.70.43.167]) (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 "protonmail.com", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bGswP6ZjYz3SGB for ; Tue, 10 Jun 2025 15:22:13 +0000 (UTC) (envelope-from minsoochoo0122@proton.me) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me; s=protonmail; t=1749568930; x=1749828130; bh=xeZwXCMlNXbHMqSFhXMOtCxo+CZepZjjZuWDVRu5pLE=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=P8kJc18eDYf7AZHQAjCzOunGyYklMoTAjyT9fSG9Nhxh6KufGZkkLiXgfIITQ6Rfg rn11X5fCz6BMRoWEvjMy8Zj/kqZFRoD3CDBQirdBWED81lrhN2B9G+GHClXfHTvv9k 4MrGmjFLUGZhjPuxunuqxn5kiPj4De0WmDlx8SimtpBrE9wbS3Wa3s6mP3nYikP9up PtLjwnvIsofL1VIOnFHn9XIaFPpuA6QH1QlzXf6L9c91tdj/oaUYkHS/QyxSoDISPI M27UROe94Xr6wl2D+1RnAE4+ugu8O7DC7Gn3l2eUzlKUMIhf8c5WtHLsOfXvEdP32P 3tkboSzush7xg== Date: Tue, 10 Jun 2025 15:22:04 +0000 To: Warner Losh From: Minsoo Choo Cc: FreeBSD CURRENT Subject: Re: Future of jemalloc on FreeBSD after archive Message-ID: In-Reply-To: References: Feedback-ID: 45891198:user:proton X-Pm-Message-ID: 31b66fe1b5a6321fbdfde382dc70350bb1886c8a 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=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4bGswP6ZjYz3SGB 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:62371, ipnet:185.70.43.0/24, country:CH] These are some replacements for jemalloc I found on the internet. Some of t= hem might not be suitable for our use cases. mimalloc by Microsoft - They claim it has better performance than jemalloc = and tcmalloc. It is also used for Bun, a javascript runtime for Node.js. Se= curity features like "guard pages, randomized allocation, encrypted free li= sts, etc" can be achieve with the hardened version with 10% performance pen= alty. tcmalloc by Google - Used by Google projects, but I'm not sure how Google'= s Bazel build system can be transformed well to our BSDmake. (No one wants = complicated makefiles, especially for malloc and libc) It is only supported= on Linux, so we need extra effort to port them to FreeBSD. Hoard - "malloc that can dramatically improve application performance, espe= cially for multithreaded programs running on multiprocessors and multicore = CPUs". Does not have any security feature on the README file. No support fo= r FreeBSD yet. rpcmalloc - "lock free thread caching 16-byte aligned memory allocator impl= emented in C". No support for FreeBSD yet. Mesh - "a drop in replacement for malloc(3) that can transparently recover = from memory fragmentation without any changes to application code." But lik= e tcmalloc, it uses Bazel build system. No support for FreeBSD yet. snmalloc by Microsoft - David's suggestion. Yet mimalloc also provides some= security features ("guard pages, randomized allocation, encrypted free lis= ts, etc. to protect against various heap vulnerabilities") as well. Still i= n 0.x stage. snmalloc and mimalloc look great for me, but my only concern is that snmall= oc is still in 0.x stage. On Monday, June 9th, 2025 at 7:17 PM, Warner Losh wrote: > 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 tod= ay? > > Warner > > On Mon, Jun 9, 2025 at 2:08=E2=80=AFPM 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 archiv= e. > > > > We could fork the repository to freebsd/jemalloc and continue to develo= p by ourselves. Then, we need to build our own CI systems for jemalloc to t= est on macOS/Linux as well. > > > > I CC'ed Warner as he guided me for D41421, so I'm seeking for his advic= e this time as well. > > > > [1] https://github.com/jemalloc/jemalloc > > [2] https://reviews.freebsd.org/D41421 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. From nobody Tue Jun 10 15:53:18 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 4bGtcV3mp8z5xr4q for ; Tue, 10 Jun 2025 15:53:30 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 4bGtcV237lz3ZYH; Tue, 10 Jun 2025 15:53:30 +0000 (UTC) (envelope-from theraven@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1749570810; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=/P8P2olRQVkg6uAU4Gwjd4DZIEPs4whcR6r7MiigFJM=; b=Lie3DbSXjZKQxCcUNHQY3BD16iIJR3ADn2ACuGkUq+TuNiiQtSbUxwQgAP5LwcAYJ/NKw1 9jkIS1uTSNq46AbaM/ptGrPg7Y8IDcBt1ggfYHTgGVtJMPnmF3XblTKx5QZxaEXPOLXkec k7HVWdky7RN6xnUMl3naY11M9xvnenTTg+ZP/U1ZhzKjLAcDgpC3SU5V2sBQvtSyKRlNlH rWmnlw9iQVJQMMV3zGCiTmIMTdTG338QT/jaEi6Sx1ANIXatGqBhIjUHr9zAYlxc72slzD 7QmLO9gYWYX83jdGHlrKPcL3kWnuBzgdAvKRsI1GWkGufCqPWT/7fyP52Q4YFg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1749570810; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=/P8P2olRQVkg6uAU4Gwjd4DZIEPs4whcR6r7MiigFJM=; b=BF40rulmxTyQLLQyOIHYpB3nFbw7JNrKIFO/W9lAdHktQ6fq3nC4g4Fnq+5XY34KBF7AvZ eZ+z/KIGvIR5cX8MIglQT9EaR3d1VRUqO3D/EVWW/mA13DtQLQeieNLAYI59qWJnkmdMQ8 QDLWEKvoN5vFAy2k4qwsFn38NVHUQNCozwqY9C4qaXLrPvwnpmEJl4tr657s3OehtG3UF6 gAS9cG/gJr2jKNlZRkuCDnpf4UUu9Q3paHAkxmO/FuJn0Lt+S7Xj0Xr1EYSrWmenrmsqLM Mwnju6CC3JB6pOHd+9FRnPGcnYihBacqdEvG8dkxfwUJvADAvrRzfmC8L1pr/A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1749570810; a=rsa-sha256; cv=none; b=BVGKNDD51dzdkTCmuyusgRGCLgsTv7AFZf3d6e0EKWheVS2CKqMKK/FYHDPJt4Nm/fCJmG 1gEsi4q+K83yHlfcRH/win9oDWo75Rp8WlJqwv4unbwnrt0hPzB4VRAw0uDHFvx0Lv7e4b esNsvh1ygp0e+1zXgDgBYEHoDe1FhtsEFvWZz4gUsd7lGZMmoALrAbArr3d4H10f+goc9c yfpNRauierjVSgbyfk5TIiM4eC/g0qowYkpO8lmssIwIzzlTcXpQntgSZWyj9swWKRo1Yk XewI7pjqodvji8Uo6wQe8eRx2JjFgEXlIla9DZe8gC3H/xi7YfN1Kxhk03PO7Q== Received: from smtp.theravensnest.org (smtp.theravensnest.org [45.77.103.195]) (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: theraven) by smtp.freebsd.org (Postfix) with ESMTPSA id 4bGtcV1JjJzHSn; Tue, 10 Jun 2025 15:53:30 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtpclient.apple (host86-143-41-189.range86-143.btcentralplus.com [86.143.41.189]) by smtp.theravensnest.org (Postfix) with ESMTPSA id 84882110E4; Tue, 10 Jun 2025 16:53:29 +0100 (BST) 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 \(3776.700.51.11.1\)) Subject: Re: Future of jemalloc on FreeBSD after archive From: David Chisnall In-Reply-To: Date: Tue, 10 Jun 2025 16:53:18 +0100 Cc: Warner Losh , FreeBSD CURRENT Content-Transfer-Encoding: quoted-printable Message-Id: <0EE4942C-1C27-48F6-B778-0596C3A99593@FreeBSD.org> References: To: Minsoo Choo X-Mailer: Apple Mail (2.3776.700.51.11.1) On 10 Jun 2025, at 16:22, Minsoo Choo wrote: >=20 > snmalloc by Microsoft - David's suggestion. Yet mimalloc also provides = some security features ("guard pages, randomized allocation, encrypted = free lists, etc. to protect against various heap vulnerabilities") as = well. Still in 0.x stage. >=20 > snmalloc and mimalloc look great for me, but my only concern is that = snmalloc is still in 0.x stage. It=E2=80=99s being used in production in multiple quite different use = cases. The main reason it isn=E2=80=99t 1.0 is that we may change some = of the internal APIs. This doesn=E2=80=99t matter for use as a global = allocator, because those APIs are stable (defined by C, C++, or Rust, = not things that we can change). snmalloc also has a number of security features (the bounds checking = alone addresses 10% of critical CVEs in the data set that we looked at = and probably has a bigger security impact than anything else). The = hardening things are discussed here: https://github.com/microsoft/snmalloc/tree/main/docs/security It=E2=80=99s also the allocator that we=E2=80=99ve used with a lot of = the CHERI work, so when the CheriBSD things are upstreamed it=E2=80=99s = easy to adopt. Supporting CHERI with mimalloc would be quite tricky. On 10 Jun 2025, at 13:47, Poul-Henning Kamp wrote: >=20 > David Chisnall writes: >=20 >> I've replaced jemalloc with snmalloc (to which I am a contributor) >=20 > It looks interesting, but rather than all of us having to do our > own homework, can you give us the "elevator pitch" for it ? Beyond the things I wrote in my previous mail: Snmalloc is a sizeclass allocator designed for concurrent workloads. = All allocations are preformed by a thread-local allocator, so there is = no locking required on the fast path for allocation. Frees from the = same thread are handled locally. Frees from remote threads are batched = (by default, up to 1 MiB of freed objects) and then sent back to the = original allocator using a lightweight message queue (single atomic = exchange to send a set of allocations, forward-progress guarantees). = This means that allocating on one thread and freeing on another (which = is the pathological case for thread-caching allocators, but a common = thing on multithreaded codebases) is really fast. The platform abstractions are cleanly separated (we try very hard to = avoid #ifdef) in most of the code. Here is the FreeBSD platform layer: = https://github.com/microsoft/snmalloc/blob/main/src/snmalloc/pal/pal_freeb= sd.h Architecture abstractions are *mostly* orthogonal to platforms, and = snmalloc supports all of the architectures that FreeBSD supports, = here=E2=80=99s the full set (note: CHERI is a mixin rather than a = separate architecture): https://github.com/microsoft/snmalloc/tree/main/src/snmalloc/aal For producer-consumer workloads, we=E2=80=99ve seen speedups of 50% = relative to thread-caching allocators like jemalloc. For = single-threaded workloads or workloads where allocation and deallocation = happen on the same thread, we=E2=80=99ve seen smaller speedups. David From nobody Tue Jun 10 16:02:37 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 4bGtqN2HWKz5xr8n for ; Tue, 10 Jun 2025 16:02:56 +0000 (UTC) (envelope-from bakul@iitbombay.org) Received: from mail-pf1-x42b.google.com (mail-pf1-x42b.google.com [IPv6:2607:f8b0:4864:20::42b]) (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 4bGtqN0Lw5z3cPD for ; Tue, 10 Jun 2025 16:02:56 +0000 (UTC) (envelope-from bakul@iitbombay.org) Authentication-Results: mx1.freebsd.org; none Received: by mail-pf1-x42b.google.com with SMTP id d2e1a72fcca58-7483c5e41edso154450b3a.3 for ; Tue, 10 Jun 2025 09:02:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iitbombay.org; s=google; t=1749571370; x=1750176170; 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=7vrbr9+DZu7mkNawmJBvjC2XAvmGVuphZd+KKGW6qz0=; b=H+XT0PweZ1JcGkFup3dJNYHcbx1Ny862Vh/c/zrLjFGatNGMFw/ca/T+haPut3H12n CMVT2RlGDzEcJJZxklslfwIv+6bQ6r8FjJMAXOlE9YZfwEoW60yWYSNMuZ3abU6pPtws JxSf73KthxlxuztBQkQFhuXTnpALCIdS40n/c= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749571370; x=1750176170; 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=7vrbr9+DZu7mkNawmJBvjC2XAvmGVuphZd+KKGW6qz0=; b=U11H9XE3gJcb9EAiWv0J1T8qOlZs/mgZy5GlThWRuvQzsqL25GAY/KWACO20l3nU/p 74WPfIjH62fgYibnrj12RcZlONdlhoMgigpnUtYtR6X70QIvE+sWLfgFoIlPT6uQLa95 Z1vTypTbcQHL80gJ75wCthRtRilEnyUHpF13uDhO+1O3mXLmUB31tSenwAQxGOKrcu5s uiledzDkgXC1BQJRXl0GIHgs9CUwvGK6zvuiLyL5J0SyXtkPRtf85W/5cv0SzicOYeQg 8KHwDiE24jA/MzDril4vMnseT7beQ/8ZB2DK1m1k24jX5oRqzTEmnJPTfQPpnMv4ze/3 mPzQ== X-Forwarded-Encrypted: i=1; AJvYcCWJs05UWJz6t9jLlwSVhm/5uKP/FXn92s9griMxBXe31IJ1oVpguyMzenj55UnsFY11HOROg/1iIbffM5SXCvc=@freebsd.org X-Gm-Message-State: AOJu0YzLMbLmznOQDxiqjOCoFPOKbUbH+afGaDz21594//rdahzHCAK1 44IrXcX+zoMfR6TdvqAYrpYrAgU1m3sTDbviRj847AXkfEjSK5Q5TrywJOVJ0laMeA== X-Gm-Gg: ASbGncvxrqGd+bUG6uNOybQgqT8ipHxnr6LimLmxPozEVmmb6fTeGbXqusboZZCjirM RuaWXUhHZ1UamU37UAtB+dTtrXapFs+a/a7JGNbitJQWg0dvYFCYqO4PZUzV48ByaDEcFbE0cz8 Wc5W0VSoG6JrXf/8ryYMor/M0dkGxY1I1p+KFi1DWZ/qmI/yyDHD/iQHCH/j65+snclJ6Ad7b+L 0yfpqc4nxYIKMmLnQZaaFfOxVOumtyoW+W4L+MXO7/9GokL9XVqvP8HsQLXwBs1Dc4ONULSr7eb jlogL3LffPZhRUn18n9B7yyaWGe1t7PFMuLghbpKTO8PMSI1XyP3g+VSH9h9mZ3Rf+hEh3ervFs HXS1jHABJolgU95exXNkC1m4SNjVcqRB+YEkqHsjQczaUTXsdpG37pMyE/QA= X-Google-Smtp-Source: AGHT+IEHC0p3vv1up2Yd0UuiFcStfb/gZr8FopWF5KqRQtcreutT+NmrXA5bi/SymP9c3JbCcsBvaw== X-Received: by 2002:a05:6a00:2c85:b0:739:b1df:2bf1 with SMTP id d2e1a72fcca58-7486ce2046fmr56936b3a.5.1749571369637; Tue, 10 Jun 2025 09:02:49 -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-7482b0847c4sm7606423b3a.79.2025.06.10.09.02.48 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Jun 2025 09:02:49 -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:02:37 -0700 Cc: Minsoo Choo , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <19F76966-2365-4598-9E9F-FC37133D980B@iitbombay.org> References: To: Gleb Popov X-Mailer: Apple Mail (2.3826.600.51.1.1) X-Rspamd-Queue-Id: 4bGtqN0Lw5z3cPD 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 8:40=E2=80=AFAM, Gleb Popov = wrote: >=20 > On Mon, Jun 9, 2025 at 11:08=E2=80=AFPM 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. =46rom 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=E2=80=99s not dead ! The Meta fork is the new home, =E2=80=9Cstil= l actively developing here=E2=80=9D but issues now have to go in = discussions = https://github.com/facebook/jemalloc/discussions/7#discussioncomment-13394= 532 Contributor commit info shows pretty abrupt handoff from Jason Evans to = Qi Wang (interwq) and David Goldblatt in 2017, so I presume this = =E2=80=9Csmall team=E2=80=9D was primarily these 2. Note Qi Wang=E2=80=99s= contributions tapering off, David stopped post-pandemic: LinkedIn says = he left Meta in 2024= 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 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!= From nobody Tue Jun 10 16:54:34 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 4bGvzF3CNBz5xwW9 for ; Tue, 10 Jun 2025 16:54:49 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (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 4bGvzF2ps0z3mjP for ; Tue, 10 Jun 2025 16:54:49 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x1033.google.com with SMTP id 98e67ed59e1d1-312116d75a6so4461253a91.3 for ; Tue, 10 Jun 2025 09:54:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1749574487; x=1750179287; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=y/nA0QYSvXtsgn4V+N36pnEn7dHe4GfM3CctklrEgTI=; b=XtXPmb0ZnxB1OjtJSHnTxTpkKiAFX6nJsefCxP8jVO+y/bOlRktxEHsB6Qbswg5IL5 Y6bLmSd+GrG3QZGeHid3OfGC0NlZ4CRdwSBsVna5EWBnW3IOFohKJ3ZGXZfdMkR3C5I0 c3G8uDv/S//3131S0E65wd3EZj2IX36ivmG2qOCtQ+u/GPfruEignfnVDc0BGWGdgTwW WNKzSvLE1LrLUwIXnThCUVrCmUOdTFH/AH97Koll19aAsr2a778MByPJ0FFuDY01PB/k EzMfqz5crjV+rZ3WlyIjW7oaA6EK4Dn4M5OPO5OkhpQhDlwJuZmcYVuJsm0cbiqlTuZx rfww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749574487; x=1750179287; 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=y/nA0QYSvXtsgn4V+N36pnEn7dHe4GfM3CctklrEgTI=; b=LESekwY376i9ZHMV27AhYPumHC7s8DvfqvD0ktaq2Pe/QyT86S1E44bPT99lyfacl4 lNlfAvUoS8lvp5uOzTSyw440l3Eavwg6BK6iULuPIP70AokeZbVSyetRJI9bhH5gEKhd Bs45JIDyaVfEy2wg1VhleITGIJI68ImCn1rJ667v05TXirwondHOKzVpDbIIW0ForUvE ltm/KOEWmCuJTXKxjTrvUbN+MnJ4GmrPKIJ3gCSFHMdF/6KJtliQ02cqPTyPIHpa9lAc YZhe+Sdjo1S8P4XbJOLCfcBj/7IXUQOAiDx7PIFsuPFtBJUZEHf5a8Sw7OvBvrfzAZ/R QJ9Q== X-Forwarded-Encrypted: i=1; AJvYcCWIXL+GK+L0x5T6zmyl1ASEsM4pUVWAUgARbcZnn/Itj+W69lhJYq52xqvLB1MpKDLNo99htqLZbCOehlWcQ6Y=@freebsd.org X-Gm-Message-State: AOJu0YwFjdKDVSZSo2vNwWF34qMQmbQL6YVdm80i9H2asyXQOHXlSJIZ 9HjhfRQ45rhKWKlGs96x+wAn2ag1/u3GeIt6JUAHC8z1EuXuFN/UOlo9Q9az/QTDjKDeO7PaAOD qJ5I4an7OZIwDaST1V4ucze/ujab50Xt9cfPebACMuw== X-Gm-Gg: ASbGnctWlUGgYLcxYzqT3Lgs2fKkLkOlijgNxgrRS/2qnibER726N21hVCJyKo8oLeP 1c3L4ngEZYmaP2e+u7tAL7PKsGPUQMba885LHGtEih+igsDahs7JwJSqCtQzr2yMgBwbR483tpU moCbS35rrq2RI/eEvcANNLjki6YqUfXQIhjyi1tKjpjp90 X-Google-Smtp-Source: AGHT+IEMYd3dpllCUHhz9ria6L2JAddHbzjl+NxGcbKm+Wcol0oNK5YRHyhVLOEWhgBz9JNKJB/kbuIow8Gv9d8H664= X-Received: by 2002:a17:90b:288b:b0:313:27e5:7ff1 with SMTP id 98e67ed59e1d1-313af0fce87mr399420a91.1.1749574486751; Tue, 10 Jun 2025 09:54:46 -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: <44DDF236-0911-4CE8-AD30-5E1AB5CB25EB@FreeBSD.org> In-Reply-To: From: Warner Losh Date: Tue, 10 Jun 2025 10:54:34 -0600 X-Gm-Features: AX0GCFsia14ScV9BcJFwvHGMUl6ywrR75lKAVtcTebOzCfNLCwYhlbukanrFVmM Message-ID: Subject: Re: Future of jemalloc on FreeBSD after archive To: Brooks Davis Cc: David Chisnall , Minsoo Choo , FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4bGvzF2ps0z3mjP 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 Tue, Jun 10, 2025 at 6:53=E2=80=AFAM Brooks Davis w= rote: > > On Tue, Jun 10, 2025 at 08:15:02AM +0100, David Chisnall wrote: > > On 10 Jun 2025, at 00:17, Warner Losh wrote: > > > > > > I'm unsure what to do in the future. What are all the cool kids using= today? > > > > I???ve replaced jemalloc with snmalloc (to which I am a contributor) in= libc about five years ago and have been using that on a few places. I bel= ieve Brooks imported a cleaned-up version of my patches to CheriBSD and was= planning on upstreaming them as an option. > > > > I've been doing infrastructure work for this as a background task > due to a decision to switch back to a wrapped jemalloc for CheriBSD > heap temporal safety work (at the time we were debugging too many > different things at once and decided that wrapping jemalloc meant we > were debugging fewer things). > > I think we should ship 15.0 with jemalloc, ideally updated to at least > 5.3.0. I'd also like to deprecate all the jemalloc specific symbols for > 15 by removing default versions. I've got a patch to do so, but probably > need an exprun for it and maybe a shim library to allow linkage with > those symbols. I agree. I have staged this, but am working through a few of the last snags in completely scripting the upgrade so that it's maximally auditable after the xz compromise. While I don't think we have a big risk of that, I think some caution is needed. I like the idea of deprecating the specific symbols... but that's contingent on exprun since I think we do use them in a few ports (or used to, I reviewed something that did years ago). > Longer term, pivoting to a malloc with better hardening is certainly the > right thing to do and snmalloc is a candidate. Yea, we need something that's maintained and still innovating. While malloc is a relatively stable interface, getting good performance out of it for the changing dynamic of applications requires constant study and tuning... I don't know enough to know if snmalloc is the best choice for us or not, but I do think we should be intentional about this and if there's a number of people that can guide the process, so much the better. Warner From nobody Tue Jun 10 17:11:20 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 4bGwLb2VBpz5xy4x for ; Tue, 10 Jun 2025 17:11:35 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) (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 4bGwLZ3xJSz3q3M for ; Tue, 10 Jun 2025 17:11:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20230601.gappssmtp.com header.s=20230601 header.b=u0FZ6Up3; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::630) smtp.mailfrom=wlosh@bsdimp.com; dmarc=none Received: by mail-pl1-x630.google.com with SMTP id d9443c01a7336-2352400344aso50401245ad.2 for ; Tue, 10 Jun 2025 10:11:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1749575492; x=1750180292; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=ILWXhQ/YfknV5WnZ6ydZI+TCttAtqcSmJd9aqNjrZho=; b=u0FZ6Up3HyjJBTe1MJfiihudMDq2Mwr8jDsSkoGUUTOEKqXD+2pweWtubsJ02/fh2O 78/tdqgOX05xGeiWMeX/APyARHI/z3bqi5O+j6cxGBK1aHN7W0eR3YdZnthBdt3TzAgz dwUGxjehIAwWfdeFg5UNPOwrGg/tOedcW+HyBA4BhUL2Fniy3hhVDcSIOubp71O77G05 8WpC3cJEYqDeLeKdT79hGgKQ11OiWAxwiY5IM3Oi3yz8YSthqFl/M9M2DMIHzK2WROwB fYfoT3LHrfJ02q/dwFTZwHFc+gm8PiVcJhBnE8vnfGQLydhvt98+xwCCPBRIkNIX8wo/ U+7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749575492; x=1750180292; 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=ILWXhQ/YfknV5WnZ6ydZI+TCttAtqcSmJd9aqNjrZho=; b=J5FR4WBrhmXB3mnSqP4jjdZCxt++cHEE1EUgLD185QegDFFj8DvEbgbQ5K0DGUlKDV e+sKuhYpdDWO0AV6zcVF3hmDQmRipqwWfx5TIFKDPrLUgHEqmu5e25DsVlH1+MfLBBaH mTOEWGMtKcAGX9iJyPrAvk+PmY/yGxyZfLHAhprpMepUFgt5IgOuPMBkcU/HvbTuWOTD RF86SW8noqTDhLMm4GOok9qskCEeft+U9uDBjXrGZWY6HjmYkb/8/8zNl/tcFLJBNYtJ xUXUZ1yBBtNzjtw7ryMNQ9f4SrqNPkDmf9zdWsrRzEEA8b826L1aW38jyHoQpyCt3jSA aMtw== X-Gm-Message-State: AOJu0YxcGi9d9ca+ijk22vl0v4FxKc6+MJCAnx2izKpT5pkT2bvJo9a2 t5Faa7VKn4ZFC9v+mKI0zZkuO7UsIZ3vf9dK+ppk5c9lstVI7J1PG7hr2JC8oc615wsjGce1VGg y+r8cBGGyLJdIPvxxBoTt0wMn09wqelkaEz1k8DngCQ== X-Gm-Gg: ASbGnct40FUo3TAZPWwdQ8AOFX8IZcQMS0PyaLPbMHNsp+4Wuts2P18UHfoA8EdCWUD +PYuOto5wuYTbdUo7gzBT0Fst/E+j5vnJYEPCkikIUxFuMvG25aLFyjOdXia+cpDs1PpZ9Lraf5 hNghvOYNUblJWbo1lifonfmOvyS1iMNdy3Zx66XPgJM+AK X-Google-Smtp-Source: AGHT+IGupxX5ydgkJ1gvs2ygDOaFYErE7FHWHjcPT5Fp9ogbImp/XmO6B1NMFPHvUsuRRPc1y12+MfIZTwg94lwPdMA= X-Received: by 2002:a17:902:e785:b0:235:e76c:4353 with SMTP id d9443c01a7336-23641b3f89cmr755435ad.51.1749575492410; Tue, 10 Jun 2025 10:11:32 -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: <78F50456-F056-4600-85DA-A07828E9F019.ref@yahoo.com> <78F50456-F056-4600-85DA-A07828E9F019@yahoo.com> In-Reply-To: <78F50456-F056-4600-85DA-A07828E9F019@yahoo.com> From: Warner Losh Date: Tue, 10 Jun 2025 11:11:20 -0600 X-Gm-Features: AX0GCFtope4y-d2xk4jCMovpNNdBYD6NioD6CBnfczfNToLZDreGpThNKNG4nxI Message-ID: Subject: Re: 2022's "stand: Document EFI consoles" update predates the 2023 "eficom" (vs. older "comconsole") update: going to be documented? To: Mark Millard Cc: FreeBSD Current , freebsd-doc@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-2.00 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20230601.gappssmtp.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::630:from]; RCVD_COUNT_ONE(0.00)[1]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+]; MISSING_XM_UA(0.00)[]; ARC_NA(0.00)[]; DMARC_NA(0.00)[bsdimp.com]; FREEMAIL_TO(0.00)[yahoo.com]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_NA(0.00)[no SPF record]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20230601.gappssmtp.com:+] X-Rspamd-Queue-Id: 4bGwLZ3xJSz3q3M X-Spamd-Bar: - tl;dr: Yea, I likely still need to update the docs to represent the current state of play. Warner On Sat, Jun 7, 2025 at 1:55=E2=80=AFAM Mark Millard wro= te: > > 2022: > > author Warner Losh 2022-09-01 16:34:30 +0000 > committer Warner Losh 2022-09-01 16:34:30 +0000 > commit 75a91c70f8d12825ded5a6d14841bf3065ba6595 (patch) > tree 6a7f7b85f596d2b5067194450b80df96f4ba40fc /stand/man/loader.efi.8 > parent b1819983e70f5b8890404b7e07d17888d0cccfb6 (diff) > > stand: Document EFI consoles > > Document how EFI consoles work, at least on x86. There's a number of weir= d quirks and limitations that are generally known, but not documented until= now. Include information on how EFI decides what the defualt console is, h= ow to set it and how to cope with common situations. Note limitations and m= ismatch between ACPI (which uses UID to identify a device) and our console = code (which uses a raw address) and explain why we can't translate between = them in the loader. > > Sponsored by: Netflix Reviewed by: manu, kevans, rpokala, pauamma > Differential Revision: https://reviews.freebsd.org/D36286 > > > vs. the 2023: > > > Commit message (Expand) Author Age Files Lines > * stand: libefi: avoid a null pointer deref in eficom Kyle Evans 2023-05-= 28 1 -2/+2 > * stand/efi/eficom: Free comc_port if we can't find the serial port Warne= r Losh 2023-05-25 1 -0/+10 > * stand/efi/eficom: Make aarch64 compat code probe correctly Warner Losh = 2023-05-25 1 -2/+5 > * stand/efi/eficom: Don't allow this for !HYPERV machines Warner Losh 202= 3-05-25 1 -0/+17 > * stand/efi/eficom: better handling of absent device Warner Losh 2023-05-= 25 1 -5/+16 > * stand: eficom: Only set baudrate when it changes Warner Losh 2023-05-11= 1 -17/+22 > * stand: eficom: Don't preemtively assume flow control Warner Losh 2023-0= 5-11 1 -9/+5 > * stand: eficom : remove unused ignore_cd Warner Losh 2023-05-11 1 -2/+0 > * stand: Move eficom to libefi Warner Losh 2023-05-11 6 -6/+1 > * stand: efi create eficom console device. Warner Losh 2023-05-11 3 -72/+= 39 > > > Those stand updates show up in main and releng/14.0 (but not in stable/= 13). > They did not include a "main 8 loader.efi" update. > > > Is man 8 loader.efi going to stop referencing comconsole as > what to use (vs. eficom) at some point? > > > Similarly for all of: > > # man -K comconsole > /usr/share/man/man8/loader.8.gz: console variable, or set it to seria= l console (=E2=80=9Ccomconsole=E2=80=9D) if the > /usr/share/man/man8/loader.efi.8.gz: work) and =E2=80=9Ccomconsole=E2= =80=9D for the serial on COM1 at the default baud rate. > /usr/share/man/man8/loader.efi.8.gz: =E2=80=9Ccomconsole=E2=80=9D. T= he default port is COM1 with an I/O address of 0x3f8. > /usr/share/man/man8/loader.efi.8.gz: comconsole_port is used to set t= his to a different port address. > /usr/share/man/man8/loader.efi.8.gz: comconsole_speed is used to set = the of the serial port (the default is > /usr/share/man/man8/loader.efi.8.gz: 9600). If you have console set = to =E2=80=9Cefi,comconsole=E2=80=9D you will get output > /usr/share/man/man8/loader_4th.8.gz: console variable, or set it to s= erial console (=E2=80=9Ccomconsole=E2=80=9D) if the > /usr/share/man/man8/loader_lua.8.gz: console variable, or sets it to = serial console (=E2=80=9Ccomconsole=E2=80=9D) if the > /usr/share/man/man8/loader_simp.8.gz: console variable, or set it to = serial console (=E2=80=9Ccomconsole=E2=80=9D) if the > /usr/share/man/man5/loader.conf.5.gz: console (=E2=80=9Cvidco= nsole=E2=80=9D) =E2=80=9Ccomconsole=E2=80=9D selects serial console, > > vs. the lack of any reference to eficom: > > # man -K eficom > # > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > > From nobody Tue Jun 10 17:12:46 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 4bGwN553b1z5xyQl for ; Tue, 10 Jun 2025 17:12:53 +0000 (UTC) (envelope-from verm@darkbeer.org) Received: from mx.coeval.ca (mx.coeval.ca [184.75.211.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4bGwN4614Sz3rKP for ; Tue, 10 Jun 2025 17:12:52 +0000 (UTC) (envelope-from verm@darkbeer.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=darkbeer.org header.s=mail header.b="T/pqrdlj"; spf=pass (mx1.freebsd.org: domain of verm@darkbeer.org designates 184.75.211.21 as permitted sender) smtp.mailfrom=verm@darkbeer.org; dmarc=none Received: from mx.darkbeer.org (unknown [192.168.211.20]) by mx.coeval.ca (Postfix) with ESMTP id 0BD4B436072 for ; Tue, 10 Jun 2025 17:12:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=darkbeer.org; s=mail; t=1749575566; bh=n8AL8/i71Br6VX5VPv29Jyu8R/YqN1wm0gfBfwaqNSQ=; h=Date:From:To:Subject:References:In-Reply-To; b=T/pqrdlj8/E1wIqY37zDecq9mwuxR9rZhMEPequGaZCcmliRlxLgFJ+GsH/o/Vhqi 3e4LAjPShEoYwISbZABLxMVFu1vi2oTmxLixvQ7veWKjpn4zBtFp1O2UZcCVNPfA1i djWlpqNU3BZz+LvicGAqqPt+g5DCFxcnYM6H7FaY= Received: by mx.darkbeer.org (Postfix, from userid 1001) id 087DC470B8B; Tue, 10 Jun 2025 17:12:46 +0000 (UTC) Date: Tue, 10 Jun 2025 17:12:46 +0000 From: Amar Takhar To: freebsd-current@freebsd.org Subject: Re: Future of jemalloc on FreeBSD after archive Message-ID: <20250610171246.GA8480@darkbeer.org> Mail-Followup-To: freebsd-current@freebsd.org 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: X-Spamd-Result: default: False [-3.49 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_HAM_MEDIUM(-1.00)[-0.996]; R_SPF_ALLOW(-0.20)[+ip4:184.75.211.21]; R_DKIM_ALLOW(-0.20)[darkbeer.org:s=mail]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:32489, ipnet:184.75.211.0/24, country:CA]; MISSING_XM_UA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[darkbeer.org]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[darkbeer.org:+] X-Rspamd-Queue-Id: 4bGwN4614Sz3rKP X-Spamd-Bar: --- On 2025-06-10 16:24 +0000, Brooks Davis wrote: > > 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. FYI issues do work on forks you have to enable it which they have done since it was brought to their attention. It's just disabled by default. https://github.com/facebook/jemalloc/issues Amar. From nobody Tue Jun 10 20:58:13 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 4bH1NY4XwHz5yHQG for ; Tue, 10 Jun 2025 20:58:37 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yw1-x112e.google.com (mail-yw1-x112e.google.com [IPv6:2607:f8b0:4864:20::112e]) (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 4bH1NX6vyyz3GVq for ; Tue, 10 Jun 2025 20:58:36 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=HhQh8vVP; spf=pass (mx1.freebsd.org: domain of kob6558@gmail.com designates 2607:f8b0:4864:20::112e as permitted sender) smtp.mailfrom=kob6558@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-yw1-x112e.google.com with SMTP id 00721157ae682-708d90aa8f9so57582007b3.3 for ; Tue, 10 Jun 2025 13:58:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749589109; x=1750193909; darn=freebsd.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=8npLLldZGERVUoe/j8aVym+uQbRBe2nZiprqiJB9vlQ=; b=HhQh8vVPhAPoM3GAdj+cqUAl4vOIrzUq1cROEnnDtB4IWUsxqDgMsHDBdc+FmVeRI7 jQogBD1B0k2nM73Crx4HojePX/z44Dt95hr10DGZzJlz8sgCf6srsfnVuLEmGoIXgruW rrxDGHPeizjELpiYth+/V04+lGwSiwNPDMKu5arhwc9WjRNXkIUSaXYbSvGAxbLswUej NY+20F+RUDp334r+fep6ln0mC0m3LBRFxI3cmwLDlTWJS2U/oS9CP5qYuvdSWYvYum0O bfFUEkzd0NWsuR//HZg4nmjlWbNWavx04/3LVoje3ODivEDoh42gI9NKeJP8drkD2Onq Ithw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749589109; x=1750193909; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=8npLLldZGERVUoe/j8aVym+uQbRBe2nZiprqiJB9vlQ=; b=mL4vJ/lPNfo9EHwwyTH5zlu0GaGmGiWnIXeC5xIKMH5vmsZT0KIhPTRJEP0o/4e5de gpMVFblHO+a1zs65kMaV49hBHHkRvdI1PsEfMp1hWofgzP0OpUKwcDaCzECkvKbl84B0 GWvZgUK9+iKoJX9nTFIX37fg7BslJD3J6U3mMqgav3pY8ayMGrS3icyBrZSake+7U4GM MEexXHtUJ2zYDwTistLOMwS9Q0Sw5dIqpHtm1eGqG4AuI/xomEq7J1l0rax5m00VUH1A n7sd+5IbUFofoXl9+aFVqiTbZxim5PS1imYAFhe3Op7UOKpZoO5u6f0J0WiUg18vMHmY SOhA== X-Gm-Message-State: AOJu0YyUxEX7aKxCBO4ZVIackJSeOUOLOmEloyP+c8eQwl7UAaQM+KVW q0mkyRkZ4Igsix3dHKShdb51wNdC+ZRVmWCd4ntpCrXtMwEwXyrMGET+UymiL0pjDrAWhblJDSs LfcaSsjKzKzRUXanPYLFGcsXN3WhQWL3XX9ak X-Gm-Gg: ASbGncvwiNTccC8rFx9TYW0Ca3fPAf4PKGpGa4cI01DhItvIk6NASs2HTVKet6Rqvr4 zk71OMOK7fsRs6rEyBT0Cn2+zAq4PLv5ILQzw0sTN17t28xOrLvPvXa2YN5+2EbSdjGuqDENwQX uMihcVPmlbQpp23bGiHMvCOLudFlQPlVTnfF0U+nf7A6UpTDEzmdWxjw+8pOuS/u2a6cawosvsh roE X-Google-Smtp-Source: AGHT+IFfduNVBXA5TkNodjGKeZaKfzvzuQdVLqgHYoIbt+WdHNCIxJuaLc9rJ9ZzffrNNGr5MWc+S4UfXhCZ0XJvSz4= X-Received: by 2002:a05:690c:620c:b0:710:ea78:8ff with SMTP id 00721157ae682-71140ad3573mr14196797b3.23.1749589109640; Tue, 10 Jun 2025 13:58:29 -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 From: Kevin Oberman Date: Tue, 10 Jun 2025 13:58:13 -0700 X-Gm-Features: AX0GCFuijoYgmVMpd3gq1Y4SHJZH_xLJH7yDh0icG5-Rdf8lHmI_CcNKXfS4KXk Message-ID: Subject: Bisecting issue in head To: FreeBSD Current Content-Type: multipart/alternative; boundary="0000000000006213de06373df56b" X-Spamd-Result: default: False [-3.68 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.98)[-0.982]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FORGED_SENDER(0.30)[rkoberman@gmail.com,kob6558@gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; MID_RHS_MATCH_FROMTLD(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; FROM_NEQ_ENVFROM(0.00)[rkoberman@gmail.com,kob6558@gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MISSING_XM_UA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::112e:from] X-Rspamd-Queue-Id: 4bH1NX6vyyz3GVq X-Spamd-Bar: --- --0000000000006213de06373df56b Content-Type: text/plain; charset="UTF-8" I probably just don't understand something about the git repo, but I am having no luck bisecting the kernel after updating 3 days ago to a kernel that crashed at boot. # git bisect start # git bisect good 99976934274d # git bisect bad 2542189532b3 # make -j12 kernel # shutdown -r now PANIC and boot kernel.old (9976934274d) # git bisect bad /usr/src updates to 1d482ca6e37b9d34ccd3c7d Can someone explain what happened? How can any /usr/src hash provide a /usr/src lacking Makefile? How can I bisect any further? -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --0000000000006213de06373df56b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I probably=C2=A0just don't understand s= omething=C2=A0about the git=C2=A0repo, but I am having no luck bisecting th= e kernel after updating 3 days ago to a kernel that crashed at boot.
<= div style=3D"font-family:tahoma,sans-serif;font-size:small" class=3D"gmail_= default">
# git bisect start
# git bisect= good 99976934274d
# git bisect bad=C2=A02542189532b3
<= div style=3D"font-family:tahoma,sans-serif;font-size:small" class=3D"gmail_= default"># make -j12 kernel
# shutdown -r now
PANIC and boot kernel.old (9976934274d)
# git bisect bad
/usr/src updates to=C2=A01d482ca6e37b9d34ccd3c7d

Can someone explain what happened? How can any /usr/s= rc hash provide a /usr/src lacking Makefile? How can I bisect any further?= =C2=A0=C2=A0
--
Kevin Oberman, Part time kid herder and retired Network Engine= er
E-mail: rkob= erman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B3= 18AB39EF1B055683
--0000000000006213de06373df56b-- From nobody Tue Jun 10 21:16:34 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 4bH1nJ1RnXz5y4C6 for ; Tue, 10 Jun 2025 21:16:36 +0000 (UTC) (envelope-from brooks@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 4bH1nH3qzLz3Wbd; Tue, 10 Jun 2025 21:16:35 +0000 (UTC) (envelope-from brooks@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1749590195; 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=jJngOsSUf1PxHhOHQICkU7g4vS4m36hQIsNgXfNHx+E=; b=QPFLUhnZ7kEmydrIdzouFUzJ9vZnlOLXCVICRCS5B1p/c2IoQIeiIR/LgBrdo+3iz/0hcm AKIzmGTAsl01TxWHyK7+XO53rxOfc8EOkpRrxoGxypZxMuSvjS+cuBHZGQ8giNzdPzJDob zsONueDdPePEI48soIZSmewzQIMoTkXazOjBY4xK72OzFp4Q+jixAdAFarpbSxOMAmrDCd 6bNh4ayR8S7eRO5HXB2iECZklMBiyaWwzGvglMvhKL1dY89oJ3vr+tdcP+35ShfRGGeuP6 feGSohrF06/E+Pw0jd1Yw8zqloS2Thx6KWY0glHXm6hFNwNBQMhCinCGQP9EoA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1749590195; 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=jJngOsSUf1PxHhOHQICkU7g4vS4m36hQIsNgXfNHx+E=; b=f5AJ569oZUARm7Nd2oesdGfNcV6HkcyG9UbDRV2MX99kLXFxVQcZbpfKiWOLTmUvXTrtGU rSnr9FXZJuF8Zj3htWTFff0TQGjRbHN3fLNL5dpDW0cWykKWqyanwcLedA+HaL+DApx0qw PvL5Nj7c9ngSp8PGNTrZrLjhVai7KrJBzokrpzkX3JS68MRTeciEy8q7QmQLFg3BSAL4Xx HjN7BWvk/L2QYqd3WGB17RLBSdvpr8Fw6llDwkLQz+ccJYLpbMkNcrdQ+FOsSdHw4YG2Md vCVuDk7HqLZaIzTSTW0iAiQLjSvD0+znzD+AhEi9qLR0T5DCBCgwCi4TcRLFTw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1749590195; a=rsa-sha256; cv=none; b=fvqS+1SqaHO6VIci+6C5Z/iCKrVM/6GS+bypVTvxMJBpQ45Dcmrja6FcGwMWUuT1NEIQo6 RQ1Rba9UoDPY2LMRaNB/QTZKjdyt8R1MvjacGa99pJI2yA5kpScFBFaVzfOfnbsYcoMVt1 W4L4CHNlnBwklwR7QEOKWbwJ19QV344sSo0E3PmGS+GV13+LOTRg83SsekAXPqbZjX5Yw6 kwWhNX8cCCkR+WnGDs9HEDO49+etrEGidtbNvGCdzLVAh32FMEXbh5pp+c+FAM0ZJzOmRB y9NL9G4IXPlN2ZO0qO1WlZx9ZNLotYJ42zBUyyq27Ap/VRfgA9vN822JD41xJg== 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 4bH1nH2t6szQBc; Tue, 10 Jun 2025 21:16:35 +0000 (UTC) (envelope-from brooks@freebsd.org) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id B067A3C01A0; Tue, 10 Jun 2025 21:16:34 +0000 (UTC) Date: Tue, 10 Jun 2025 21:16:34 +0000 From: Brooks Davis To: Kevin Oberman Cc: FreeBSD Current Subject: Re: Bisecting issue in head Message-ID: References: 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: On Tue, Jun 10, 2025 at 01:58:13PM -0700, Kevin Oberman wrote: > I probably just don't understand something about the git repo, but I am > having no luck bisecting the kernel after updating 3 days ago to a kernel > that crashed at boot. > > # git bisect start > # git bisect good 99976934274d > # git bisect bad 2542189532b3 > # make -j12 kernel > # shutdown -r now > PANIC and boot kernel.old (9976934274d) > # git bisect bad > /usr/src updates to 1d482ca6e37b9d34ccd3c7d > > Can someone explain what happened? How can any /usr/src hash provide a > /usr/src lacking Makefile? How can I bisect any further? I suspect you're probably bisecting across a merge commit. If so, you need to use the --first-parent argument to start to avoid taking right hand side which is off in the vendor tree and not a valid FreeBSD source tree. -- Brooks From nobody Wed Jun 11 03:53:29 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 4bHBbX3Lwmz5ybsc for ; Wed, 11 Jun 2025 03:53:44 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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) by mx1.freebsd.org (Postfix) with ESMTPS id 4bHBbW6Kfxz3pDf; Wed, 11 Jun 2025 03:53:43 +0000 (UTC) (envelope-from kostikbel@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: from tom.home (kib@localhost [127.0.0.1] (may be forged)) by kib.kiev.ua (8.18.1/8.18.1) with ESMTP id 55B3rU07049278; Wed, 11 Jun 2025 06:53:33 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 55B3rU07049278 Received: (from kostik@localhost) by tom.home (8.18.1/8.18.1/Submit) id 55B3rTrh049276; Wed, 11 Jun 2025 06:53:29 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 11 Jun 2025 06:53:29 +0300 From: Konstantin Belousov To: Warner Losh Cc: Brooks Davis , Minsoo Choo , FreeBSD CURRENT Subject: Re: Future of jemalloc on FreeBSD after archive Message-ID: References: <44DDF236-0911-4CE8-AD30-5E1AB5CB25EB@FreeBSD.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=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=4.0.1 X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on tom.home X-Rspamd-Queue-Id: 4bHBbW6Kfxz3pDf 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:6939, ipnet:2001:470::/32, country:US] On Tue, Jun 10, 2025 at 10:54:34AM -0600, Warner Losh wrote: > On Tue, Jun 10, 2025 at 6:53 AM Brooks Davis wrote: > > > > On Tue, Jun 10, 2025 at 08:15:02AM +0100, David Chisnall wrote: > > > On 10 Jun 2025, at 00:17, Warner Losh wrote: > > > > > > > > I'm unsure what to do in the future. What are all the cool kids using today? > > > > > > I???ve replaced jemalloc with snmalloc (to which I am a contributor) in libc about five years ago and have been using that on a few places. I believe Brooks imported a cleaned-up version of my patches to CheriBSD and was planning on upstreaming them as an option. > > > > > > > I've been doing infrastructure work for this as a background task > > due to a decision to switch back to a wrapped jemalloc for CheriBSD > > heap temporal safety work (at the time we were debugging too many > > different things at once and decided that wrapping jemalloc meant we > > were debugging fewer things). > > > > I think we should ship 15.0 with jemalloc, ideally updated to at least > > 5.3.0. I'd also like to deprecate all the jemalloc specific symbols for > > 15 by removing default versions. I've got a patch to do so, but probably > > need an exprun for it and maybe a shim library to allow linkage with > > those symbols. > > I agree. I have staged this, but am working through a few of the last > snags in completely scripting the upgrade so that it's maximally > auditable after the xz compromise. While I don't think we have a big > risk of that, I think some caution is needed. I like the idea of > deprecating the specific symbols... but that's contingent on exprun > since I think we do use them in a few ports (or used to, I reviewed > something that did years ago). > > > Longer term, pivoting to a malloc with better hardening is certainly the > > right thing to do and snmalloc is a candidate. > > Yea, we need something that's maintained and still innovating. While > malloc is a relatively stable interface, getting good performance out > of it for the changing dynamic of applications requires constant study > and tuning... I don't know enough to know if snmalloc is the best > choice for us or not, but I do think we should be intentional about > this and if there's a number of people that can guide the process, so > much the better. I believe before ever starting importing any such mallocs, we need to get rid of the malloc uses in C runtime. I already did that for some critical parts of libthr, perhaps whole libthr should be malloc-free. Then, libc uses of malloc needs to be audited, and stuff like TLS allocations get rid of it. Perhaps it is fine and even necessary to continue using malloc for e.g. asprintf(), gai, etc, which do not participate in C runtime proper. This should make malloc integration much less demanding. Perhaps libc could be converted to filter for malloc symbols, like it is for libsys. From nobody Wed Jun 11 04:12:14 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 4bHC1K5G1fz5yd1t for ; Wed, 11 Jun 2025 04:12:37 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yw1-x1133.google.com (mail-yw1-x1133.google.com [IPv6:2607:f8b0:4864:20::1133]) (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 4bHC1J6jj6z41PV; Wed, 11 Jun 2025 04:12:36 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-x1133.google.com with SMTP id 00721157ae682-70f31433d96so56884167b3.2; Tue, 10 Jun 2025 21:12:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749615150; x=1750219950; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=cGxOJaj5PH9CeUOEsPemFTlFVvn+XRDH/MASMRxSOsI=; b=ceasiKIHdmdfHcEQpOtZuWSD073A6zCEJKkw5+UTX0QSDJlrDX2sWN06wdW7+9QskQ cGFe8S1qmtGufk6dMA1S2DdlvM7CbxlhhO5rGkr2lTdZ6cVmvSc721VWXcbcalTYCTV6 WDcUOElIngsJc2qdfN0MFwN4dvjjmMvxmS5Yv45JUM8NwK02AP44aKytESExkt/XwOBu 4HqMhc+bxkJl1HvzG+evQOGMfY8kqRXbFlca41CNBW369FWpsp6RzwhcSU3hS8OOSEOQ CXdcguVvCwxiXGPjYZ580O3l6DSJGa5tZSHY2O3qRmWH6L3gYPnTko2vvM3OEOAamSQW FEiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749615150; x=1750219950; h=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=cGxOJaj5PH9CeUOEsPemFTlFVvn+XRDH/MASMRxSOsI=; b=p0FrhZJKzyLJz7bcxVlnh0IwN4KNwdX9dLiBqL9E/L6ch08ZiFp6SiaefdxIRmkeQg A4h6uVQyudk31ECOB5gsw6AZphCR1Qx1DLJdDjGwPD7xFp08dpP2xg97RoAoHsSrWoKK F3xrqJAk5LPYpVuUHLYBk9xQMNo61TZyEPIXvUSTeXGe5HevhKV/OQ+qBgeUYhr3QDGg fQ5S8AuUGi4SNZ1baI9WnihtNdmy4zh4DTJUntcoT0NFWOkHf3NaFEvT46PndDWVqcU9 hRBnFeZGFS1Oqwn95aWxJ1zrb4uN8PvSB3v9BWC0zl9FJ+2jPLbEgMWGdV2MtdHJsbIp +JDA== X-Gm-Message-State: AOJu0YwdKdod/QZOkBPS+q68rtUThjYQQBIkpDq2uUsFfBzSmPUvkNS9 iA7GbdT2vWw0iv4B/vfc+3n3vW6JZZi3Me516p9Bylg9pT0PU2JJ+tLNgDW/VXL3xGstHZ8K2G4 ySDeVuovZw0cR+FXFuidST6PTupRp5uj29vEF X-Gm-Gg: ASbGncvezjTh9nfaKmtOjkk+5lsZgfrlmbOxAUqmfU4Iah5at4piTQYrVN2FArR9U1G KrJTqQe+GjWXNK8LcSnPJmFY3yhlIy2uA9Vs3C854YFJnTYGv788ODQZD5us7IiwA7nFdkh33mj a3kpb9UoZvonyp245o0sCoApd4snZojCh3UYMwPNwJAomiHgbMf6Kt/X5lU31GWOgLPLZa4SW4x CMP X-Google-Smtp-Source: AGHT+IF5u9EEysqoZUl6/3rWGPWo3k5O6dsJLVwuhHPf1BXpHTQkMWtDJiDIq9Pyt0M6On/5P+Iu/J65wrfaa7/oFaY= X-Received: by 2002:a05:690c:6304:b0:70d:fe74:1800 with SMTP id 00721157ae682-7114240e93cmr20550587b3.15.1749615150284; Tue, 10 Jun 2025 21:12:30 -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: Kevin Oberman Date: Tue, 10 Jun 2025 21:12:14 -0700 X-Gm-Features: AX0GCFtXpNCCYj0C3HeeerUTKrcjrd-Fm9VJGJrgq96Rx5LDPcTxKqqqQpy0Y_U Message-ID: Subject: Re: Bisecting issue in head To: Brooks Davis Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="00000000000086c54b0637440558" X-Rspamd-Queue-Id: 4bHC1J6jj6z41PV 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] --00000000000086c54b0637440558 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks, Brooks! That was the issue. I did manatee to mess up the bisection, so I am back to near my original start, I do have a more recent good to start with. I spent too many years with old-fashioned SVN and CVS and forgot how easy it is to not only branch, but merge with git. Thanks again! On Tue, Jun 10, 2025 at 2:16=E2=80=AFPM Brooks Davis w= rote: > On Tue, Jun 10, 2025 at 01:58:13PM -0700, Kevin Oberman wrote: > > I probably just don't understand something about the git repo, but I am > > having no luck bisecting the kernel after updating 3 days ago to a kern= el > > that crashed at boot. > > > > # git bisect start > > # git bisect good 99976934274d > > # git bisect bad 2542189532b3 > > # make -j12 kernel > > # shutdown -r now > > PANIC and boot kernel.old (9976934274d) > > # git bisect bad > > /usr/src updates to 1d482ca6e37b9d34ccd3c7d > > > > Can someone explain what happened? How can any /usr/src hash provide a > > /usr/src lacking Makefile? How can I bisect any further? > > I suspect you're probably bisecting across a merge commit. If so, you > need to use the --first-parent argument to start to avoid taking right > hand side which is off in the vendor tree and not a valid FreeBSD source > tree. > > -- Brooks > --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --00000000000086c54b0637440558 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks, Brooks! That was the issue. I did manate= e=C2=A0to mess up the bisection, so I am back to near my original start, I = do have a more recent good to start=C2=A0with.
I spent too m= any years with old-fashioned=C2=A0
<= /span>
Thanks aga= in!

=
On Tue, Jun 10, 2025 at 2:16=E2=80=AF= PM Brooks Davis <brooks@freebsd.or= g> wrote:
On Tue, Jun 10, 2025 at 01:58:13PM -0700, Kevin Oberman wrote:
> I probably just don't understand something about the git repo, but= I am
> having no luck bisecting the kernel after updating 3 days ago to a ker= nel
> that crashed at boot.
>
> # git bisect start
> # git bisect good 99976934274d
> # git bisect bad 2542189532b3
> # make -j12 kernel
> # shutdown -r now
> PANIC and boot kernel.old (9976934274d)
> # git bisect bad
> /usr/src updates to 1d482ca6e37b9d34ccd3c7d
>
> Can someone explain what happened? How can any /usr/src hash provide a=
> /usr/src lacking Makefile? How can I bisect any further?

I suspect you're probably bisecting across a merge commit.=C2=A0 If so,= you
need to use the --first-parent argument to start to avoid taking right
hand side which is off in the vendor tree and not a valid FreeBSD source tree.

-- Brooks


--
Kevin Oberman, Part time kid herder and retired Network Engineer
E= -mail: rkoberman@g= mail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39E= F1B055683
--00000000000086c54b0637440558-- From nobody Wed Jun 11 05:28:09 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 4bHDjV5WQdz5yjxS for ; Wed, 11 Jun 2025 05:29:02 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp052.goneo.de (smtp5.goneo.de [IPv6:2001:1640:5::8:30]) (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) by mx1.freebsd.org (Postfix) with ESMTPS id 4bHDjR54t8z41dR for ; Wed, 11 Jun 2025 05:28:59 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b=b9S184Iy; spf=pass (mx1.freebsd.org: domain of freebsd@walstatt-de.de designates 2001:1640:5::8:30 as permitted sender) smtp.mailfrom=freebsd@walstatt-de.de; dmarc=none Received: from hub2.goneo.de (hub2.goneo.de [85.220.129.53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp5.goneo.de (Postfix) with ESMTPS id 359B52402D6 for ; Wed, 11 Jun 2025 07:28:52 +0200 (CEST) Received: from hub2.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPS id 9B58E24034E for ; Wed, 11 Jun 2025 07:28:50 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1749619730; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=amkz7D3UsvYNIB8vqOzVtUmjONF6AtZEprFbZnlVoHs=; b=b9S184Iy6rseehFLzIrbDG1LLMsGONBVO4JPqpg6ZGckksAmm+5+UedIZIuJoOWKD7efQZ /HrXtM+nhHb1iUjJJZm8qmPCxpqk8Hn5DUYZKIUN1zwm79vbb6Zl9bZCnzp0Z1SveOLaV4 T5BEQB4vqvFOx2OFfUd92rfgIi01gpcppLhhoRWipAnk/UH5Nl2KWnSPyGLPRN0cT4eLWZ bzPdZjOFtf4MY3YMSv5Hn1eDuYEfZSRUep5vS5KhYawEdkF0/ElOAEnTfxdxTXfnGTPzdk hYiLiGC8xyn0+2MFYC0nRDpCvHbikVwlmAcXtviOamT1JbM+r3kn9xBgN4xEEg== Received: from thor.sb211.local (dynamic-2a02-3100-25db-ed02-6d3c-d85c-852e-01a8.310.pool.telefonica.de [IPv6:2a02:3100:25db:ed02:6d3c:d85c:852e:1a8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPSA id 6314F24033B for ; Wed, 11 Jun 2025 07:28:50 +0200 (CEST) Date: Wed, 11 Jun 2025 07:28:09 +0200 From: A FreeBSD User To: FreeBSD CURRENT Subject: if_bridge(): IPv6 EUI-64 seemingly not working Message-ID: <20250611072836.2a0b026a@thor.sb211.local> 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: multipart/signed; boundary="Sig_/VrzlWAacSd1nMrus9iR.L0X"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Rspamd-UID: d36048 X-Rspamd-UID: d834ad X-Spamd-Result: default: False [-3.22 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_SPAM_MEDIUM(1.00)[0.998]; NEURAL_HAM_SHORT(-0.98)[-0.975]; NEURAL_HAM_LONG(-0.54)[-0.540]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; R_SPF_ALLOW(-0.20)[+ip6:2001:1640:5::8:0/112]; RCVD_IN_DNSWL_LOW(-0.10)[2001:1640:5::8:30:from]; RCPT_COUNT_ONE(0.00)[1]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:25394, ipnet:2001:1640::/32, country:DE]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MISSING_XM_UA(0.00)[]; RCVD_TLS_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[walstatt-de.de]; DKIM_TRACE(0.00)[walstatt-de.de:+] X-Rspamd-Queue-Id: 4bHDjR54t8z41dR X-Spamd-Bar: --- --Sig_/VrzlWAacSd1nMrus9iR.L0X Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hello development folks, after the announcement not supporting set IPs on NICS member of a bridge I = tried to switch on all of my administered CURRENT and 14 boxes towards the proposed scheme - w= ith different results. Background: several boxes sit behind dynamically changing uplinks. The boxe= s are identified via dynamic DNS entries containing the NIC's MAC address at my dyn DNS prov= ider. A prerequisite is to configure the if_bridge() in question to inherit the/a (= persistent) MAC of a/the first inherited NIC. In my case, this part works without flaw. net.link.bridge.pfil_bridge When it comes to obtain an IPv6, CURRENT, in contrast to 14-STABLE, fails t= o set the host part according EUI-64. The resulting 64 host bit, which are considered to contai= n the 48 bit of the MAC, do contain anything but not anything similar to ANY of the attached NI= C/NICs.=20 For the record, here the sysctl settings changing default settings of OIDs = involving bridge (according to some docs when jails share epair() devices on that bridge): [...] net.link.bridge.inherit_mac=3D1 net.link.bridge.pfil_local_phys=3D0 net.link.bridge.pfil_member=3D0 net.link.bridge.pfil_bridge=3D0 net.link.bridge.pfil_onlyip=3D0 [...] I do not see the described (mutual) misbehaviour on 14-STABLE and or 14.2-R= ELENG. So the negative effect of this is that the hosts in questions are not acces= sible/known anymore to the net. A bug or a "feature (due to simple dumb misconfiguration)? Thanks in advance, oh --=20 A FreeBSD user --Sig_/VrzlWAacSd1nMrus9iR.L0X Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRQheDybVktG5eW/1Kxzvs8OqokrwUCaEkUBAAKCRCxzvs8Oqok r4aoAQCE6LX0jRtSPnsVvQ8j/GJybAoNO/xC7Vg3lGY9gbDrdwEAywmD7EMy2ILf gL+0wleOUIy0VMBsVu256oz/bTmvGgU= =tUX5 -----END PGP SIGNATURE----- --Sig_/VrzlWAacSd1nMrus9iR.L0X-- From nobody Wed Jun 11 14:33: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 4bHSnw6bwRz5xyBh for ; Wed, 11 Jun 2025 14:33:40 +0000 (UTC) (envelope-from brooks@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 4bHSnw3tljz3RxH; Wed, 11 Jun 2025 14:33:40 +0000 (UTC) (envelope-from brooks@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1749652420; 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=MTgaYn1NJc+g3aPKKyR5eruyKXpXjf21nNOG9y9htxU=; b=xOHu4JbffyAfLP2lXQbIVKa+AgdAUj0cfxO38u/w9Rg5sA6HDTn10tWT0QL3WULk9VuuKD NXbTE9kVRmVLnumSH5gjY1cg0j2aKPqJuvw4WaLenfYuOvJbXfuEdZu43bc5Qm2mK45+a7 VLvTqHKFWQUCtRAZwgxYAq8f3zpSczuq8dikIh88SkqRHLkmG0HrG43ulmy3y4+zGg8TTd X94nnqt4bYVNZJWm9JqZzTwM5PCz6ULPxkgYHhCnF+iLP6/odmld3gvhieZ6BAVfx4rz3U 1TRHbnkAt1QqNTra0owtQmJLAAR3mIUi0eUmFITjUJjUovu6bz5QEEC4QnL99A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1749652420; 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=MTgaYn1NJc+g3aPKKyR5eruyKXpXjf21nNOG9y9htxU=; b=usOBoM6tuYiH/qAAfdpWQc6NIrrFIBdj/maMp1pwWnQGkRkdVGuTvVlDuz0F0oxL35UABz AwsBj5YkzcmlPsbyN+lEKA/CZKCfaxRkO8/lcKmHRQgLragcCkUee5nmoFuwg/iszR/eKB umL585VBmGAhRchFv5lYZUrggnE4sjXYvmS3MJOmVkTZJRXfWKQmg7QGb3WKXV9FgiJp1/ mzObTM0up05APYQL6lY3P1oFM9xE7ByyOhywaRP36Ea1ePwuaRrPQExBKDFRLTUhU5aJL/ b+MHfZ11cih3C6WsTgAlOv/bEVWdjXA9uOFMyRDzYaHVG3aaL0MUpz5GeZtenA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1749652420; a=rsa-sha256; cv=none; b=WCL7X3M6wWZulgZ7VkRAwmE+QsngqfMIxVZDkgd8cAEjG5ov3YlWSzskb4jAHOmNLeGcwY dFG8U3QMwvz9f1F/OCVkwER5WkveVARvr6SGuTb2aqccFbcZPGDcB7F30iRhEaQVY+cYe5 Akln8mVN9HNKUIXzEreuSGnxkxL0p57m7G/tpkt4lpCpwnfGoo+i2FD/utBE9LTT695V58 ySLHTj4qzc8TdfEYCd16qS9h41Q0G5H7bWBdzxLZjn1adJhblxeCcp1H32DJHgqD19nAY3 fxmhbHDgTsiexr9Kr+7I9ncr8y8jvMxlSjwNZ+fKbBLJEGSH8Jnm8I82vB/TzQ== 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 4bHSnw3N71z13Wc; Wed, 11 Jun 2025 14:33:40 +0000 (UTC) (envelope-from brooks@freebsd.org) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id D03DB3C01A0; Wed, 11 Jun 2025 14:33:39 +0000 (UTC) Date: Wed, 11 Jun 2025 14:33:39 +0000 From: Brooks Davis To: Konstantin Belousov Cc: Warner Losh , Minsoo Choo , FreeBSD CURRENT Subject: Re: Future of jemalloc on FreeBSD after archive Message-ID: References: <44DDF236-0911-4CE8-AD30-5E1AB5CB25EB@FreeBSD.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: On Wed, Jun 11, 2025 at 06:53:29AM +0300, Konstantin Belousov wrote: > On Tue, Jun 10, 2025 at 10:54:34AM -0600, Warner Losh wrote: > > On Tue, Jun 10, 2025 at 6:53???AM Brooks Davis wrote: > > > > > > On Tue, Jun 10, 2025 at 08:15:02AM +0100, David Chisnall wrote: > > > > On 10 Jun 2025, at 00:17, Warner Losh wrote: > > > > > > > > > > I'm unsure what to do in the future. What are all the cool kids using today? > > > > > > > > I???ve replaced jemalloc with snmalloc (to which I am a contributor) in libc about five years ago and have been using that on a few places. I believe Brooks imported a cleaned-up version of my patches to CheriBSD and was planning on upstreaming them as an option. > > > > > > > > > > I've been doing infrastructure work for this as a background task > > > due to a decision to switch back to a wrapped jemalloc for CheriBSD > > > heap temporal safety work (at the time we were debugging too many > > > different things at once and decided that wrapping jemalloc meant we > > > were debugging fewer things). > > > > > > I think we should ship 15.0 with jemalloc, ideally updated to at least > > > 5.3.0. I'd also like to deprecate all the jemalloc specific symbols for > > > 15 by removing default versions. I've got a patch to do so, but probably > > > need an exprun for it and maybe a shim library to allow linkage with > > > those symbols. > > > > I agree. I have staged this, but am working through a few of the last > > snags in completely scripting the upgrade so that it's maximally > > auditable after the xz compromise. While I don't think we have a big > > risk of that, I think some caution is needed. I like the idea of > > deprecating the specific symbols... but that's contingent on exprun > > since I think we do use them in a few ports (or used to, I reviewed > > something that did years ago). > > > > > Longer term, pivoting to a malloc with better hardening is certainly the > > > right thing to do and snmalloc is a candidate. > > > > Yea, we need something that's maintained and still innovating. While > > malloc is a relatively stable interface, getting good performance out > > of it for the changing dynamic of applications requires constant study > > and tuning... I don't know enough to know if snmalloc is the best > > choice for us or not, but I do think we should be intentional about > > this and if there's a number of people that can guide the process, so > > much the better. > > I believe before ever starting importing any such mallocs, we need to > get rid of the malloc uses in C runtime. I already did that for some > critical parts of libthr, perhaps whole libthr should be malloc-free. > > Then, libc uses of malloc needs to be audited, and stuff like TLS > allocations get rid of it. Perhaps it is fine and even necessary to > continue using malloc for e.g. asprintf(), gai, etc, which do not > participate in C runtime proper. > > This should make malloc integration much less demanding. Perhaps libc > could be converted to filter for malloc symbols, like it is for libsys. Currently the only deeply integrated bits are the __je_bootstrap_* bits in TLS. I don't know of anything else should change. asprintf() absolutely must use malloc because its allocation must be passable to free. It might be there are some things with their own free interface that don't need to use the system malloc, but IMO there's little reason not to. We've got a patch in CheriBSD to use a separate malloc in TLS. It's essentially using a local copy of rtld_malloc as a tls_malloc, but structured differently due to CheriBSD history. Reconverging with FreeBSD is on our to do list. I've sometimes pondered extracting the malloc implementation from libc, but I'm a bit less convinced of the value than with libsys. I don't think it would be terribly hard to do. -- Brooks From nobody Wed Jun 11 15:35:10 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 4bHV9D3jFTz5y3Rd for ; Wed, 11 Jun 2025 15:35:28 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lj1-f169.google.com (mail-lj1-f169.google.com [209.85.208.169]) (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 4bHV9B5lSfz3r21 for ; Wed, 11 Jun 2025 15:35:26 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of adrian.chadd@gmail.com designates 209.85.208.169 as permitted sender) smtp.mailfrom=adrian.chadd@gmail.com; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none) Received: by mail-lj1-f169.google.com with SMTP id 38308e7fff4ca-32934448e8bso59288371fa.3 for ; Wed, 11 Jun 2025 08:35:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749656124; x=1750260924; h=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=T1zUIQ4L4Gcjn6RWUFrpgjcZdrOYonIpgE2gKY9+ZuY=; b=bTQp96tTb4ApmhJD4Ih62VvAdHHmSIz9hjD/l63KBb13mY6kmBKETsWasfm2JoY281 NrPe/xLHFUZaVUzJgnA5taiMZ1ywxbK/Qw2W9RZAvQYAHJ4HSRRUsLJo1j9Ui6PMFICG PiYMONA3Ght4xIAzCRhaPntS1M0XEScwY0b4TClorPVjq+RpSOK0GaCNFCkWEBSpnqFW u0WR5ehDOc2N3Pdfs089VUgF4phIyXwasllhMcKedjLRX6L9VqOc4TxGxMrEaXS0RlM0 3u8GT1VdZefHIokwOzbRm37NRXjPY2p+cnWIw55xVfqoSWGCx7FvRkmHa8URrZcsh0qN rJcQ== X-Gm-Message-State: AOJu0Yyaa5vERtLPCTZ4ZKY4Nyr24RrJ6feCB6Bx2TvkZKZAJHEmO968 /V/xaI6UpVhHWkIckkcZdAtPBqRS+/LIMKxnaDwT5zW5f9z2TGdT8W86TvSn3V54EI5ZgZipBqD 5Sg3PDX0zcMUVYum1e18zx8AF40R3+N2pyA== X-Gm-Gg: ASbGncuT/vumDTik9lc8hRi0t8MPRH8ihR1bMmt2zCmKIiwj11BfAAjjZTEr56ccA4b dzfgta4cif1xiLYW4oQtX/C+c1czgZMgdk6ZOyDDjuVso4b8tQNgBCYXWvyHomGojXMEZfqAMrG aJdyJ5JGa/15ZnLacF1q8YuQNLCG3vgAcPq3Pyqj+7zfeV X-Google-Smtp-Source: AGHT+IFrHnoa+gM95g+yPJetWnG1Sr6z37O7bnUZxtKxNqTglYL9Lrgk3pXAWW4YwcMuUTqcptTuoD1m/zlARqv73+g= X-Received: by 2002:a2e:a9ac:0:b0:32a:8555:8117 with SMTP id 38308e7fff4ca-32b21d725e7mr12812031fa.9.1749656123394; Wed, 11 Jun 2025 08:35:23 -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: <19F76966-2365-4598-9E9F-FC37133D980B@iitbombay.org> <20250610171246.GA8480@darkbeer.org> In-Reply-To: <20250610171246.GA8480@darkbeer.org> From: Adrian Chadd Date: Wed, 11 Jun 2025 08:35:10 -0700 X-Gm-Features: AX0GCFtsW2faOE3gpS7voLE1bGzV7GNqpeypQ0NieniGjbXUVs_3PcUz_rGbGiY Message-ID: Subject: Re: Future of jemalloc on FreeBSD after archive To: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000b6ced406374d8f91" X-Spamd-Result: default: False [1.09 / 15.00]; NEURAL_SPAM_LONG(1.00)[1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_SPAM_MEDIUM(0.99)[0.993]; FORGED_SENDER(0.30)[adrian@freebsd.org,adrianchadd@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; TAGGED_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[adrian@freebsd.org,adrianchadd@gmail.com]; MISSING_XM_UA(0.00)[]; TO_DOM_EQ_FROM_DOM(0.00)[]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.208.169:from]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; RCVD_IN_DNSWL_NONE(0.00)[209.85.208.169:from]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4bHV9B5lSfz3r21 X-Spamd-Bar: + --000000000000b6ced406374d8f91 Content-Type: text/plain; charset="UTF-8" On Tue, 10 Jun 2025 at 10:13, Amar Takhar wrote: > On 2025-06-10 16:24 +0000, Brooks Davis wrote: > > > > 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. > > FYI issues do work on forks you have to enable it which they have done > since it > was brought to their attention. It's just disabled by default. > > https://github.com/facebook/jemalloc/issues And FYI, I work at facebook, so if there are any weird things going on with the jemalloc repo at facebook (or any other facebook open source repo) please feel free to poke me and I'll try to route it internally to the right folks. -adrian > > > Amar. > > --000000000000b6ced406374d8f91 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, 10 Jun = 2025 at 10:13, Amar Takhar <verm@da= rkbeer.org> wrote:
On 2025-06-10 16:24 +0000, Brooks Davis wrote:
>
> Why not move the repo or break the fork so issues work?=C2=A0 This fee= ls like
> flailing around without understanding how github works and does not > inspire confidence.

FYI issues do work on forks you have to enable it which they have done sinc= e it
was brought to their attention.=C2=A0 It's just disabled by default.
=C2=A0 https://github.com/facebook/jemalloc/issues

And FYI, I work at facebook, so if there are = any weird things going on with the jemalloc repo
at facebook (or = any other facebook open source repo) please feel free to poke me and I'= ll
try to route it internally to the right folks.

<= /div>


-adrian
=C2=A0
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">

Amar.

--000000000000b6ced406374d8f91-- From nobody Wed Jun 11 18:52:52 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 4bHZYN191dz5yJw2 for ; Wed, 11 Jun 2025 18:53:12 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (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 4bHZYM2dfCz3rRf for ; Wed, 11 Jun 2025 18:53:11 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=OaGr45GT; spf=pass (mx1.freebsd.org: domain of yaneurabeya@gmail.com designates 2607:f8b0:4864:20::72d as permitted sender) smtp.mailfrom=yaneurabeya@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-qk1-x72d.google.com with SMTP id af79cd13be357-7cadd46eb07so18304685a.3 for ; Wed, 11 Jun 2025 11:53:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749667985; x=1750272785; darn=freebsd.org; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=FUQyZ58OJ/Ct1tUblTLDw0id4ZzSZyezgzTxHTYPGV0=; b=OaGr45GT03oyppU3+OaaRQU7SvoiDOMtHtFLk+JS79to5nlxAPbhNRzuP94LU0tq54 sZvDAo9G6W6U01+GSoG0sJvIkOjxQ3eBroaAl4YZzGMxbtP+QUjHRvkApZ3dJKSgMOS2 dB3Lq/6aNN9Y+NGVMAYqv/oecy0dPGDd8q6jl64idcUl/q1hlhdq3f5gqNq7napphbyH mxdazSD/OntRIJJGN3YDpsjiYLYCJdgwjp6WNIDFxy4gdqa2Gez1IpypF4w7BFFOR2Y3 3PsdRzOIXpVG/Qf7Bc1b9x5YzIWB1m5EWDMQ4oej7rVl4BBAQ1CdRp9LuPho9rCqcirv V71A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749667985; x=1750272785; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=FUQyZ58OJ/Ct1tUblTLDw0id4ZzSZyezgzTxHTYPGV0=; b=CWwtFSgHUdRdx/xvqPQxIJS66rOGddqrUXcMd6xDSAvLL9emU5oF2y/xeuVlLYcj0Z hs1WfHk+m8aR+N5zheiFBfxGiv38XxVkSi21PuTbkTCdEnOkBxY3LDEpcfE+puhQx3TN zjtrFw34Q/9JOv98VW+5POCNIz+hXpMiDmu1z4GPsV99gsRPZQZZKSCxAzeTUUPH/exK Nr9RuIRcrqlLxkpN0RsBPVTZxX04M6VIlbB1JFwz4enuMaTrUKUIkPpMkVWqJ71+lvtd DOhs6o6AH2hNNc6udDCRAZ93fTZfxyUM5ZKYbjGY2Jb7EBVBPEqya2vv9HZLwhYicLtZ Lxuw== X-Forwarded-Encrypted: i=1; AJvYcCVJYCZYu0MJB1TUHszV6WX0FTywvthCe2X1EE9v98UTTFx1bS4DxbuzQqNpOYeBcRpoaHxRuo02zXMQVIk3/U8=@freebsd.org X-Gm-Message-State: AOJu0Yxof+Ap1Gd6WIPvr9CoY9D2dlruxFwBSrkvfz2XOmEQ1JX0jlBE 19NT13tsKXleED9lpGZ58ZU3FOMJNhDw/AUZCXuPyBtYpEf89Q9/hqNQ X-Gm-Gg: ASbGnct45FkeUuicM+lzL5IVRMFluSujz828tQ4SBDPvOjsJKH+c8RZW1dy+hFOTRxW Cv4EnbsWFIeYi6YE2l7NHnXplRjXMvETVAIqTEvfRNYEN2F+R/+0Tdpg22wzQUhtSCc5dPdUF28 w+nrpa/MkB8G+irC644eNJl5gg4K6zWfLJZozUr9mUW+v6F+JvgHsIFFrh0WJJG1huR0UMN7vQ6 5JwCy5Pb2IQ16wCuKFSh93QXU8xdnaim0juT4E/N6qlWq4INNonZxrXvZpMYLxpjT57Lr3wn+cJ KmCR3/slRPELUxQClHmWH5644neseO1zArQNpQSzTRoU/Qt1lN7zgg8PEsR73FNZVhk1NbVzoYD UXg== X-Google-Smtp-Source: AGHT+IH7anu5ejGDc4ykTrLs2mZYauTxjxaOfU2akErwXuMdVfQepTO9tM2AiYq4xyBmrY1Zz/wc4g== X-Received: by 2002:a05:620a:394a:b0:7cd:49d6:32ce with SMTP id af79cd13be357-7d3a88b4f88mr646996885a.32.1749667985355; Wed, 11 Jun 2025 11:53:05 -0700 (PDT) Received: from smtpclient.apple ([62.3.36.182]) by smtp.gmail.com with ESMTPSA id af79cd13be357-7d25a61c935sm899480985a.96.2025.06.11.11.53.04 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Jun 2025 11:53:04 -0700 (PDT) Content-Type: multipart/signed; boundary="Apple-Mail=_8AB8D76D-8E53-4AA9-A320-DEA82365C276"; protocol="application/pgp-signature"; micalg=pgp-sha256 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: "Enji Cooper (yaneurabeya)" In-Reply-To: <584301BC-9EC6-4205-AB23-41C0EDF8F478@iitbombay.org> Date: Wed, 11 Jun 2025 11:52:52 -0700 Cc: Warner Losh , Minsoo Choo , FreeBSD Current Message-Id: <56D570C5-57E8-41B3-95CE-19701B12C439@gmail.com> References: <584301BC-9EC6-4205-AB23-41C0EDF8F478@iitbombay.org> To: Bakul Shah X-Mailer: Apple Mail (2.3826.600.51.1.1) X-Spamd-Result: default: False [-3.36 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_SPAM_MEDIUM(0.99)[0.995]; NEURAL_HAM_SHORT(-0.99)[-0.986]; NEURAL_HAM_LONG(-0.77)[-0.772]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; FREEMAIL_ENVFROM(0.00)[gmail.com]; HAS_ATTACHMENT(0.00)[]; ARC_NA(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; DKIM_TRACE(0.00)[gmail.com:+]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::72d:from]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MLMMJ_DEST(0.00)[FreeBSD-current@freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Rspamd-Queue-Id: 4bHZYM2dfCz3rRf X-Spamd-Bar: --- --Apple-Mail=_8AB8D76D-8E53-4AA9-A320-DEA82365C276 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Jun 10, 2025, at 8:20=E2=80=AFAM, Bakul Shah = wrote: >=20 > Looks like there is https://github.com/facebook/Jemalloc > See https://x.com/permutans/status/1931398314924150814 Interesting. Given Meta=E2=80=99s drive to implement/deploy GenAI today, = it=E2=80=99ll be interesting to see how exactly this dynamic plays out = over the longterm. Cheers, -Enji= --Apple-Mail=_8AB8D76D-8E53-4AA9-A320-DEA82365C276 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEkHfexGRJ3gYRdA2gGpE5DjPsNJgFAmhJ0IQACgkQGpE5DjPs NJgTmhAAk7c6JycTu8nVygXB4v8h5swV8O4gzOdLKtIbyCJC4TJASFbzJdggDb9v XRdAXV511WvJlJhdxsPCmHB9ktYAnhaGO3Jem2oB9uWCdqwn9ik5oVAnNMPhhZaY 3HtGpbGXcliYgYMunZpQVfDEsWxZ2G3Lh2orczbNFrxxVKAaysssBpDKPtEELy0M NTDFatT6wiFwQaiN/zyFXFC9Ze4LO395OxztkIXw3WEvpC5v8sNvgVvIBGN7xuTq Ba0VA3bVJMLwTRx6IRzBJ0GxB6/bVenqzb/yZAxCCCDcrlgfWwk+acZaElWlGw7z HHF3MiqaiCj8KIWTzKeICb81lFdTozcAtZ97j1ILXciK8glLjumYcvdz8SYP1CNm 7hrug+VMryKZsu9kxFsbCdQ8yP7mbApqzxrNWqwDjNbQDNm+LV4RpimGnZxMB4gP ga4PKN3iCNQ+qqtjyU+6Kci1AZTz8v5ql460ty2ajU6n1D3bydWGjSk/hNHP/77K G6W3tZQMfv4ITKuAjQyA9mCpoYbOViySFj+/lqaAZvZl5VdPobFl0UfZ2kR1ovI3 P9xL0BEOpADp6/BLRTFcUY19PE1N62opM8EtLdLHQ/Sk7/e3ckBreYDxT/b4D1/O HV6wqTem2afcOiMk7yxUEjYB1KYfrMxC4gkeR4yOHfbrPPEF9Ig= =7+m+ -----END PGP SIGNATURE----- --Apple-Mail=_8AB8D76D-8E53-4AA9-A320-DEA82365C276-- From nobody Thu Jun 12 03:58:30 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 4bHpfZ6NF1z5y2wq for ; Thu, 12 Jun 2025 03:58:30 +0000 (UTC) (envelope-from ivy@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (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 "freefall.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bHpfZ5jmFz45tw; Thu, 12 Jun 2025 03:58:30 +0000 (UTC) (envelope-from ivy@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1749700710; 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=fu44mzD0+hvsZRnfdSJOgV0GKvgafZvHqhOWiQUw8k4=; b=ns/aJaFX4HWZWNRl1LoYmU+FwjHfGssUf9tk5+cj9hKLThMbWglB3skSrsqRwMCbBTics3 teBGkdKIxn5pCObTd6IkEQau7tv3pz3tuYn6UJod9NCkzNpEyA77TIzA7HMxxyLVmPuJxL 0Gke+orfQw7pzHHCBU8NciFFTenxsShhKr5unKVenAEgxwm+hQ/1qOxcJuaQnaxB0EkruN Tkj/sYt01lKxfSug6FwjfxXHgqiVqjNKve/Jl1oRKubFz+38aQGgT/hBLSubYSejqqJeh+ fS9F2d+zNWYk/dorAI0tz46n5ZSqswD/ggL5UJKKH6X943Kqjn/ZP9yKxIFOYg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1749700710; 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=fu44mzD0+hvsZRnfdSJOgV0GKvgafZvHqhOWiQUw8k4=; b=yOv39vpujoIxrRkb+ahfodM0csQy6tOVQfzNmEJ9CxqhxoL7hjDXo9DW+j0PprH8E968+l /wpqaTh5By7b1T2l1XCQd8jljIQupQYS6wxEJXlIYSUC6Ol1QbNCh0J7DuiaTosxu+PtrA vRTom7bdwIbKA/oMc0D7P59EBAANpO2Y+6ojlxR1o7E1eQh/upK29UFcmJIdpq5N//5QkI ewG0MbHwScZ0nV2fxTgFTUy6C4IcdWeyyjiRoEvyRqomnEAY/iihvXA2K5jEtSOlad+lz3 FQe+LknEs0JBVlm6/pMeg55x90D3inWuqcaEYBDoXDF8wgxlNE6K4yJGfpsOiQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1749700710; a=rsa-sha256; cv=none; b=uIZVo6XcVN55pl+vcmW+afWPHYEWFqywUCVTEAoZISZBSuOzx2Oycz4hjLyglY6/CktL9z 7QN6Qtxe9zpNd55QwUWNAtSEr67gX9Fq2Y1IPHCo4NaRcXVJD19XAEsHHpK4LVwFpadhwv SAvpHsku3CIvcgNsZMS67L0ZhDzYdtI+vLYyH6wPc1IWJQcgv0HTUBEANZp30lwpOuZgqt +W3hu2dWMUFp+lrOcs61lQAF7m/Au1LSp1CgFTgl5vMvNfeS9IezjtAKC9j9L6voM3h1Rp 943ly6yItT5QNp1Kw+BI/tzspV1TQmcZSqQ0jZxrDeLv+HMuczCKfWcKAgCW4Q== Received: by freefall.freebsd.org (Postfix, from userid 1532) id 862CE10964; Thu, 12 Jun 2025 03:58:30 +0000 (UTC) Date: Thu, 12 Jun 2025 04:58:30 +0100 From: Lexi Winter To: A FreeBSD User Cc: FreeBSD CURRENT Subject: Re: if_bridge(): IPv6 EUI-64 seemingly not working Message-ID: Mail-Followup-To: A FreeBSD User , FreeBSD CURRENT References: <20250611072836.2a0b026a@thor.sb211.local> 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: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="DePLRVFpag87hEq5" Content-Disposition: inline In-Reply-To: <20250611072836.2a0b026a@thor.sb211.local> --DePLRVFpag87hEq5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable A FreeBSD User: > When it comes to obtain an IPv6, CURRENT, in contrast to 14-STABLE, > fails to set the host part according EUI-64. The resulting 64 host > bit, which are considered to contain the 48 bit of the MAC, do contain > anything but not anything similar to ANY of the attached NIC/NICs.=20 please show the output of 'ifconfig' for the bridge interface and all interfaces which are members of the bridge. > A bug or a "feature (due to simple dumb misconfiguration)? this is not intentional, it should still work as it did before. --DePLRVFpag87hEq5 Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQSyjTg96lp3RifySyn1nT63mIK/YAUCaEpQZgAKCRD1nT63mIK/ YA71AP9YHKiQO4SsfTt+/cp9rSzCjQgjUhmMQmjCAB5V11GVxQEAkhOXqwlZBU5E bU4/qql+x8tNFx2JbtreP9B1CUTQuQ0= =Ue7u -----END PGP SIGNATURE----- --DePLRVFpag87hEq5-- From nobody Thu Jun 12 05:33:01 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 4bHrm11CL2z5y9dt for ; Thu, 12 Jun 2025 05:33:21 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp052.goneo.de (smtp5.goneo.de [IPv6:2001:1640:5::8:30]) (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) by mx1.freebsd.org (Postfix) with ESMTPS id 4bHrm05lFRz3pwh; Thu, 12 Jun 2025 05:33:20 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; none Received: from hub2.goneo.de (hub2.goneo.de [IPv6:2001:1640:5::8:53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp5.goneo.de (Postfix) with ESMTPS id B4B412402CE; Thu, 12 Jun 2025 07:33:12 +0200 (CEST) Received: from hub2.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPS id 18AD4240266; Thu, 12 Jun 2025 07:33:11 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1749706391; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=wkUOh3x/GzbyfMvECp97T5PMRSJ0ZUT0EqirxZtpJSI=; b=G6qvu1crEe85lkOagQIT44STYYp37DrkXvB3iL87n30bW+2HOHzASQhQ26eBZoaCrN5cvb YBcn+uKxRxpDyUBWg3uIl/RLid/58XJyMNrVAWn4a92TE8ZbmILWI5pqEUpRkn2AZVN5kW XNRmYs9Jf5gpNBcAl6pyBtTKBOmFF8dfCbbcsK/13pzDDZoBB9h+Xpk6oSj2GolflrdlrT WT5M21Soyzm50wlj8kopS/weZddrqz6gf69ZpcJR/a+JbwzSu4ywBmRKxpZB1GScmfLicg etxK+mwsmrpZaeYvFpW5nI940ztSbMl/6PFD6tNkS8i2nQQrhVONvOeuQKDSjw== Received: from freyja (p5de89b8f.dip0.t-ipconnect.de [93.232.155.143]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPSA id 8B4F02402EB; Thu, 12 Jun 2025 07:33:10 +0200 (CEST) Date: Thu, 12 Jun 2025 07:33:01 +0200 From: FreeBSD User To: Lexi Winter Cc: FreeBSD CURRENT Subject: Re: if_bridge(): IPv6 EUI-64 seemingly not working Message-ID: <20250612073301.60bfc7ce@freyja> In-Reply-To: References: <20250611072836.2a0b026a@thor.sb211.local> Organization: Heimstatt X-Mailer: Claws Mail 4.3.0 (GTK 3.24.49; amd64-portbld-freebsd14.3) 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-Transfer-Encoding: 7bit X-Rspamd-UID: 86e5d5 X-Rspamd-UID: 600080 X-Rspamd-Queue-Id: 4bHrm05lFRz3pwh 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:25394, ipnet:2001:1640::/32, country:DE] On Thu, 12 Jun 2025 04:58:30 +0100 Lexi Winter wrote: > A FreeBSD User: > > When it comes to obtain an IPv6, CURRENT, in contrast to 14-STABLE, > > fails to set the host part according EUI-64. The resulting 64 host > > bit, which are considered to contain the 48 bit of the MAC, do > > contain anything but not anything similar to ANY of the attached > > NIC/NICs. > > please show the output of 'ifconfig' for the bridge interface and all > interfaces which are members of the bridge. > > > A bug or a "feature (due to simple dumb misconfiguration)? > > this is not intentional, it should still work as it did before. Seems, linklocal address is the benfeactor ... > [... sysctl net.link.bridge for the record if appropriate ...] net.link.bridge.ipfw: 0 net.link.bridge.member_ifaddrs: 0 net.link.bridge.log_mac_flap: 1 net.link.bridge.allow_llz_overlap: 0 net.link.bridge.inherit_mac: 1 net.link.bridge.log_stp: 1 net.link.bridge.pfil_local_phys: 0 net.link.bridge.pfil_member: 0 net.link.bridge.ipfw_arp: 0 net.link.bridge.pfil_bridge: 0 net.link.bridge.pfil_onlyip: 0 [...] $ ifconfig bridge0 bridge0: flags=1008843 metric 0 mtu 1500 description: vlan101-uplink options=0 ether 4c:52:62:2b:05:eb inet 192.168.201.10 netmask 0xffffff00 broadcast 192.168.101.255 inet6 fe80::5a9c:fcff:fe00:393a%bridge0 prefixlen 64 scopeid 0x6 inet6 fd60:b403:201::10 prefixlen 64 inet6 fd60:b403:201:0:5a9c:fcff:fe00:393a prefixlen 64 autoconf pltime 14400 vltime 86400 inet6 fd60:b403:101:0:1cef:d312:32c5:fdae prefixlen 64 autoconf temporary pltime 14400 vltime 86400 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: igb0 flags=143 ifmaxaddr 0 port 1 priority 128 path cost 20000 groups: bridge maclabel mls/low(low-low) nd6 options=23 $ ifconfig igb0 igb0: \ flags=1008943 \ metric 0 mtu 1500 options=4e503bb ether 4c:52:62:2b:05:eb media: Ethernet autoselect (1000baseT ) status: active maclabel mls/low(low-low) nd6 options=29 Also, some netgraph modules are compiled statically into the kernel - for the record, if that matters, but disabled so far. ############################################################################### security.mac.mls.enabled=0 security.mac.portacl.enabled=0 security.mac.bsdextended.enabled=0 security.mac.ipacl.ipv6=0 security.mac.ipacl.ipv4=0 security.mac.do.enabled=0 ############################################################################### From nobody Fri Jun 13 19:04:03 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 4bJpj91BzZz50xXy for ; Fri, 13 Jun 2025 19:04:13 +0000 (UTC) (envelope-from paulf2718@gmail.com) Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (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 4bJpj8165tz416R for ; Fri, 13 Jun 2025 19:04:12 +0000 (UTC) (envelope-from paulf2718@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=VoVNzKmz; spf=pass (mx1.freebsd.org: domain of paulf2718@gmail.com designates 2a00:1450:4864:20::42a as permitted sender) smtp.mailfrom=paulf2718@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-wr1-x42a.google.com with SMTP id ffacd0b85a97d-3a35c894313so2445937f8f.2 for ; Fri, 13 Jun 2025 12:04:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749841445; x=1750446245; darn=freebsd.org; h=content-transfer-encoding:in-reply-to:content-language:references :to:subject:from:user-agent:mime-version:date:message-id:from:to:cc :subject:date:message-id:reply-to; bh=FVVGhV3HYupFFrxbHuEM33mVsc93KQtfwENo8RDgL3k=; b=VoVNzKmzLiWXSAplflmTuVZTwUJd/P5UEK6F98X0tI5A9/KBeXSRK75P1VzL2XavRq TWwS1j0Fk6hEl9fEM+x+n6FcpjGvDd+17hMWfF+YbGnCJEOMketPqImqeh8jiI3NRn6I OfVP1oV+YiwT58WNpu2hjW72gx88/DedvvWmKhB/k+l0JgZTpfs9ttROyz8sjqIcABid T73yTsw5jAtH91Cd70omZ+6TogTvAJOvG5UnqxF/APQ7v4oJTJ4Veuwc/sm/0B+abGhR 7shrZ4faWA7LSPjKgrFWtbyt2T6zjAvcFfr4bTKbSgAufOe/fcOIIJCFAbA2d1XWdajT WwqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749841445; x=1750446245; h=content-transfer-encoding:in-reply-to:content-language:references :to:subject:from:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=FVVGhV3HYupFFrxbHuEM33mVsc93KQtfwENo8RDgL3k=; b=rQ4HhYBPeZ+j9KGEjtatpNxOONkHqOMrYWa9+0n8hOS2BUBF1vhJG1vbNA71eM5NSS +Sb2TTuQ3VzyWcgUhfhrA757/oVbC0ipoiWBP16i06EMusYjps6wozOCqIjuPTrlFYxk dAJoLzgPPBY97Wi8sEW3b3X+2Wi93tJ7GCURryfxHIZuu2CiHNV5h1P4b4BYCxWRVhm1 /4zqZNJs2LoS7miyvhJDo13hYjBZB4uznCCv6oU8j9dJYotApyoefTMChbe5Jxhyf+7G pQPMeB+a7R+faoL8g5vYbreuPJ2vNO1Cfc+lN9ATxOrkKakzdIAaiIQZa/snJLIYSPUM gW2w== X-Gm-Message-State: AOJu0YyAzozFMn9tdgRj0meagcm4Nweq7+ZTOtVMXHwCYyfIPL1bLWbX 99nE9JjHAYos5psX0yc8d20iNq2DrueNu+JhMt49zN8QheYZQCX5KEey5bGw9w== X-Gm-Gg: ASbGncsrupZYBaw5Djs68j+lJAP47qYQoDqd/p+lGWuBHWDf9KFZXRQ004wR9wwZQvi tF3jpIsPygooi6uSfyBVFWfPMK1QZa2//S1TTvUcf8TqtF2ydcbHnkwtvOQt1Ae5cIFJM4EsSUo 04nQ9z88d/bdtYg/XAhAvrlztJ4+6nGlCxSyu5BFZVZNJ7Bciyu2G+MufNgB6+2qLy3wAHtfbZF mUbzpD179lTL4XSO8WxF/z+pQYZj8o7pH+tFTKPLzCdtE77u2C5OlbG8yF5jP3zh6gQrMS31bBD kXUE4kSo1Ubarj4Bt46xl9gTAeREJ6pp+8NHCkVA1NTDs6uOg5Vgglj+SpU+7PoePnOp+KwENL+ xyldlahcbUOma0U7xNXFA83ZhTNgE6SqeHVg= X-Google-Smtp-Source: AGHT+IHWx/hjCADRhEljTYr2wxDtXQ6N/+I+XgvCZrB7oTo/vz4xW/uWUqinKAhDzkDyxd3AZT1pQA== X-Received: by 2002:a05:6000:290b:b0:3a5:2e84:cc7b with SMTP id ffacd0b85a97d-3a57238b7f2mr764593f8f.11.1749841444768; Fri, 13 Jun 2025 12:04:04 -0700 (PDT) Received: from ?IPV6:2a01:cb15:8545:7700:62cf:84ff:fe81:caec? ([2a01:cb15:8545:7700:62cf:84ff:fe81:caec]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-4532e13cfbesm60772585e9.22.2025.06.13.12.04.03 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 13 Jun 2025 12:04:03 -0700 (PDT) Message-ID: <836f8890-ca73-4e26-a439-c09c99c21e6b@gmail.com> Date: Fri, 13 Jun 2025 21:04:03 +0200 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 User-Agent: Mozilla Thunderbird From: Paul Floyd Subject: Re: Future of jemalloc on FreeBSD after archive To: freebsd-current@freebsd.org References: Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [1.31 / 15.00]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; NEURAL_SPAM_LONG(1.00)[1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_SPAM_SHORT(0.31)[0.306]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_TLS_LAST(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::42a:from]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4bJpj8165tz416R X-Spamd-Bar: + On 6/9/25 22:08, Minsoo Choo 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/D41421 It seems to be fairly dead, See this on Reddit https://www.reddit.com/r/cpp/comments/1la7r64/jemalloc_postmortem/ I would recommend looking for an alternative unless Meta really do make some effort to keep development going. A+ Paul From nobody Sun Jun 15 00:01:32 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 4bKYG66HzVz5Vl2N; Sun, 15 Jun 2025 00:01:50 +0000 (UTC) (envelope-from salvadore@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (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 "freefall.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bKYG64hzBz3rWm; Sun, 15 Jun 2025 00:01:50 +0000 (UTC) (envelope-from salvadore@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1749945710; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc; bh=Sl5UdYBPI6gCf/6oABuPJB8buTxt4l2g/wBNmtbvTl0=; b=u8rWJcaBjrYJbFtRn89yC9dNZmWaP9/mT6wUWguhzkemzNZbYV8sPtrO/Gl5NuUBLBl1Fy 2Fg+fJWCdkxuzJFwEXY8rIVi9ZsjCAIqyYFBrvsCauk41aGsG7ldZ6MFCvtCvsCeF6+4W4 DPfzpwHNgwBrOay2em/o2uRfdHzGxpVE8ASWKR3sFfYa5R5idbbxtKjbqSixQS/tcp+AGJ /f6d4gbmayfQ+2qAK0D09pACFH2b261v0StptxPllx6yoUjrc3bE0VmcGkfAgGzmENHuqg vtAsx1cjk8ksnEvOU6jnwOpfielugD9kul9Ql2gYjlKSAx7vkXeQk3CVljznow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1749945710; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc; bh=Sl5UdYBPI6gCf/6oABuPJB8buTxt4l2g/wBNmtbvTl0=; b=qlMPcAM4Qxszbn5uQdl061VhZDhqTNpv1OsumypUl6tmJx1zBVSJ+jVP1/zH9Mfi1kpQ0/ IV4GicxDg49Yb4N1hp0pIxxqXFHqkctQn28IRzZt2vvm/lqlizJLgQbedPQkvHxfXDRLGR tULVr1HYkVWtMEBR3u+ZSVglxToQYckmVZqe4seRPZmXU2ccf13xMYSZbTQf5kcMsoASKi Qrr1vutNlzwAu3bsONU8CrVo5c+eYiGF4+3QRjUAwcS0dURIGyQlEwsCDTJLNaq38yRJ1A tGe4c+Jv0MPzB/1CkD9LufLTStsn4P/jVqr1LYcXMP2A6K1JReM6ed8xLRNA7g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1749945710; a=rsa-sha256; cv=none; b=bh0GA6vAElhlAxFk0pPEVluxJw6+S0arVwMfbxHA71JvH5teUy+Lvkb9js9NJphWa3aleB 827GVFD8ZBitjZQ+zW/qTtfb+C7CRZVIbnbwDzLfGqPqTrryDpP4h0dqN10gMZo7//+plW u8o+jBFNAFB3YT6IxqgsW3gvVMpSYbk342+XUaoBD5OMjY3QJPblXLej7KarqzcSmf/660 DlyWb4iHNT031WvjV6IIsKVcWLcL8+rFuvcleMsHfHMPjJMvrvrXUz28mjzZbFvItC3ixP TEHx/Fk/wLMMSQQU9U2phE2ioyuFRtt3Zl9pF4dhFjuvPjNTIU9+fo3ctq6mCQ== Received: by freefall.freebsd.org (Postfix, from userid 1472) id 716571230B; Sun, 15 Jun 2025 00:01:32 +0000 (UTC) To: freebsd-status-calls@FreeBSD.org Subject: [2 WEEKS LEFT REMINDER] Call for 2025Q2 status reports Cc: freebsd-current@FreeBSD.org,freebsd-hackers@FreeBSD.org,devsummit@FreeBSD.org,info@bsdcan.org,soc-students@FreeBSD.org,soc-mentors@FreeBSD.org Message-Id: <20250615000150.716571230B@freefall.freebsd.org> Date: Sun, 15 Jun 2025 00:01:32 +0000 (UTC) From: Lorenzo Salvadore 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 Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is June, 30th 2025 for work done since the last round of quarterly reports: April 2025 - June 2025. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2025-04-2025-06/ (create it if it is missing); * submit a pull request at . You should put your reports in the directory doc/website/content/en/status/report-2025-04-2025-06/ (create it if it is missing); * send an email to status-submissions@FreeBSD.org including your report. An AsciiDoc template is available at . We look forward to seeing your 2025Q2 reports! Thanks, Lorenzo Salvadore (on behalf of status@)