From nobody Sun May 7 21:19:01 2023 X-Original-To: freebsd-arch@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 4QDy3W1s1Jz49WtB for ; Sun, 7 May 2023 21:19:19 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from mail.rlwinm.de (mail.rlwinm.de [138.201.35.217]) (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 4QDy3V0183z3HtR for ; Sun, 7 May 2023 21:19:17 +0000 (UTC) (envelope-from crest@rlwinm.de) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of crest@rlwinm.de designates 138.201.35.217 as permitted sender) smtp.mailfrom=crest@rlwinm.de; dmarc=none Received: from [IPV6:2001:9e8:978:1d00:3db4:6da6:3cca:fbb9] (unknown [IPv6:2001:9e8:978:1d00:3db4:6da6:3cca:fbb9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.rlwinm.de (Postfix) with ESMTPSA id 4B1E533F02 for ; Sun, 7 May 2023 21:19:03 +0000 (UTC) Message-ID: Date: Sun, 7 May 2023 23:19:01 +0200 List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 Subject: Re: Support for more than 256 CPU cores Content-Language: en-US To: freebsd-arch@freebsd.org References: <84816f2f-b23c-f448-55fe-454cbb604681@selasky.org> From: Jan Bramkamp In-Reply-To: <84816f2f-b23c-f448-55fe-454cbb604681@selasky.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-3.23 / 15.00]; NEURAL_HAM_SHORT(-0.99)[-0.991]; NEURAL_HAM_MEDIUM(-0.97)[-0.971]; NEURAL_HAM_LONG(-0.96)[-0.965]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:24940, ipnet:138.201.0.0/16, country:DE]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arch@freebsd.org]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[rlwinm.de]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arch@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4QDy3V0183z3HtR X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On 05.05.23 17:52, Hans Petter Selasky wrote: > On 5/5/23 17:23, Tomek CEDRO wrote: >> On Fri, May 5, 2023 at 3:38 PM Ed Maste wrote: >>> FreeBSD supports up to 256 CPU cores in the default kernel >>> configuration >>> (on Tier-1 architectures).  Systems with more than 256 cores are >>> available now, and will become increasingly common over FreeBSD 14’s >>> lifetime. (..) >> >> Congratulations! :-) >> >> I am looking after AMD Threadripper with 64 cores 2 threads each that >> will give 128 CPU to the system.. maybe this year I could afford that >> beast then I will report back after testing :-) >> >> In upcoming years variations of RISC-V will provide unheard before >> number of CPU in a single SoC (i.e. 1000 CPU) at amazing power >> efficiency and I saw reports of prototype with 3 x SoC of this kind on >> a single board :-) >> >> https://spectrum.ieee.org/risc-v-ai >> > > Hi, > > Maybe it makes sense to cluster CPU's in logical groups somehow. Some > synchronization mechanism like EPOCH() are O(N²) where N is the number > of CPUs. Not in the read-case, but in the synchronize case. It depends > a bit though. Currently EPOCH() is executed every kern.hz . Unless the implementation scales quadratic with the number of CPU logical CPUs representable by cpuset_t instead of the number of CPUs available to the kernel it should still be worth it to change the ABI in time for 14.0 even if the existing implementation of EPOCH doesn't scale well. If the ABI isn't extended in time the whole 14.x major release line will either be limited to 256 logical CPUs, require users to change the type and recompile *everything*, or have to reinterpret cpuset_t as something other than a flat bitmap of cores. In my opinion there are three important constraints:  * Don't delay the 14.0 release more than necessary.  * Don't penalize systems with 256 or less cores too much.  * Make the struct big enough to allow a better implementation later. Just increasing the bitset by a factor of four shouldn't be to expensive, but is it enough to allow the implementation of algorithms that scale better or is additional storage needed. e.g. a bit for each logical group at each level of grouping? From nobody Sun May 7 21:51:34 2023 X-Original-To: freebsd-arch@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 4QDymw10v4z49ZCq; Sun, 7 May 2023 21:51:44 +0000 (UTC) (envelope-from bofh@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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QDymw0WPgz3h8T; Sun, 7 May 2023 21:51:44 +0000 (UTC) (envelope-from bofh@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1683496304; 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=9rqXHS09T9QOJ8Gc/BTeNDpHZ3tdhnjmgdbP7Cynys0=; b=sfCElv3l0Cajq0rVT62lLz5RmC0qaItTy7QcTEJuJQQgl0usip+ZGl3o1YzjnZz+kYVwC6 8EOxRg67tvEsq8v8yNnt5xhzyZNS//M5iycBd7wM6VOZZam6AmDy/4Ho7h8e9D6ppjODKH qkYB94hK/8HcowWfq9EgRCvUmGtPfKgfFkjsgB20pWZx3ICKStGaDJcSOrPWcH536LlKjy VUOnznEcRpovk9kc22BotTKssiD7pZsDl6tmWXnQkzE1mcTBTZohcm5Xen9j4+ti1yDLO9 EYd55GA2tZJhC4HZYYmS5jhPnLwfd2j8CkV9wjkj0yI3lwmRyGtGv2pgpRd7Qg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1683496304; 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=9rqXHS09T9QOJ8Gc/BTeNDpHZ3tdhnjmgdbP7Cynys0=; b=JAp2odmEWdcALfR11iYTI+5Bp5Yb8P6tqaj/w0HTSfvLlG+u4OH++Zsn1rEIrdvoT9RF+q CneezyAfygOYkVTwqt78eS6FmaqXAeBug6wv+D2VU1dJDaCltEvfo/TiZJ/tgUzk9Zgk6G l8pppqYEbqokkj/tIx2otYcvcRITQx8bT3DD93DZGcbdvG2h7JWfpocNDs9d7xCpbVN4t+ dzXDmtG4PD9rYNvccPFMOP4qKP95yyVW8Q9Th9NYLmPhIgTfdYizWXL4J0HE6CwEZ1/Sez Ii3IivtgDuQPZCJnrcbFqDLPDwd32NYKU3Nj9H4GLSab8GwxJ+Ca1PAAgDmhVA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1683496304; a=rsa-sha256; cv=none; b=old3sfE4nGXKnsHlmRSzf/s91mUU/QPwYouNStPZMFK5mUM2YDafI3tMm5opGUaNQl20+s C8EP69B0M3X0vPtuyTlDgiwVcpBxzF2tHnlShwIiybhoJZWg5btw/rtqb3WEX4LVhDp4SO T4+ECRZyjYKx7qtGnRidX5SS8HVzdxRWAQr4B/il/NbkGmGHVxg8SZ8fppbLFE4QGJJrds hKi9mnSNDf3mQ5cysHdiU46ZqVUyftU9gUVfwiC2Hcq8ASoSFBtQhHHC6sQpcdL2I01njU JoVWWEchVVWpKX9pu8poshVjKkxgJHp5NZ0uZERpBHu8TEzEYa2I5VeiuP2/7g== Received: from mx.bofh.network (mx.bofh.network [IPv6:2a01:4f8:261:25de::227]) (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 ECDSA (P-256) client-digest SHA256) (Client CN "mx.bofh.network", Issuer "R3" (verified OK)) (Authenticated sender: bofh/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QDymv3dFHzXTm; Sun, 7 May 2023 21:51:43 +0000 (UTC) (envelope-from bofh@freebsd.org) Received: from smtpclient.apple ( [80.113.232.25]) by mx.bofh.network (OpenSMTPD) with ESMTPSA id 21cef34f (TLSv1.2:ECDHE-ECDSA-AES256-GCM-SHA384:256:NO); Sun, 7 May 2023 21:51:40 +0000 (UTC) Content-Type: multipart/signed; boundary="Apple-Mail=_C3334CE5-ACF2-45E3-8874-D2467ED173AD"; protocol="application/pgp-signature"; micalg=pgp-sha512 List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.3\)) Subject: Re: Support for more than 256 CPU cores From: Moin Rahman In-Reply-To: Date: Sun, 7 May 2023 23:51:34 +0200 Cc: freebsd-arch , FreeBSD Current Message-Id: References: To: Ed Maste X-Mailer: Apple Mail (2.3696.120.41.1.3) X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_C3334CE5-ACF2-45E3-8874-D2467ED173AD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On May 5, 2023, at 3:38 PM, Ed Maste wrote: >=20 > FreeBSD supports up to 256 CPU cores in the default kernel = configuration > (on Tier-1 architectures). Systems with more than 256 cores are > available now, and will become increasingly common over FreeBSD 14=E2=80= =99s > lifetime. The FreeBSD Foundation is supporting the effort to increase > MAXCPU, and PR269572[1] is open to track tasks and changes. >=20 > As a project we have scalability work ahead of us to make best use of > high core count machines, but at a minimum we should be able to boot a > GENERIC kernel on such systems, and have an ABI for the FreeBSD 14 > release that supports such a configuration. >=20 > Some changes have already been committed in support of increased = MAXCPU, > including increasing MAX_APIC_ID (commit c8113dad7ed4) and a number of > changes to reduce bloat (such as commits 42f722e721cd, e72f7ed43eef, > 78cfa762ebf2 and 74ac712f72cf). >=20 > The next step is to increase the maximum cpuset size for userland. > I have this change open in review D39941[2] and an exp-run request in > PR271213[3]. Following that the kernel change for increasing MAXCPU = is > in D36838[4]. >=20 > Additional work on bloat reduction will continue after this change, = and > looking forward FreeBSD is going to need ongoing effort from the > community and the FreeBSD Foundation to continue improving = scalability. >=20 > [1] https://bugs.freebsd.org/269572 > [2] https://reviews.freebsd.org/D39941 > [3] https://bugs.freebsd.org/271213 > [4] https://reviews.freebsd.org/D36838 >=20 By any chance will this be merged into 13? Kind regards, Moin --Apple-Mail=_C3334CE5-ACF2-45E3-8874-D2467ED173AD 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----- iQKTBAEBCgB9FiEETfdREoUGjQZKBS+fvbm1phfAvJEFAmRYHWZfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDRE Rjc1MTEyODUwNjhEMDY0QTA1MkY5RkJEQjlCNUE2MTdDMEJDOTEACgkQvbm1phfA vJHjIw/+PJmVaqSnjEOT6WJiuZvO72HKqpZIlH4GlDeZR9aWrCOVPiw7MjnYvoZa E0XPBngzxPnM5adP0k7rjekdIScwxkorqZsNa6ncTGXc7sa1dDe22wjVPlTk3BxX eLy+SjzoNcilT8bcykFbl2OydFwTR4AhtGWFn1oZ/KvqZXeYrfH+TmsxswleKe8D pDgmalvUTD736ugYeG08+amdEv6leT1RaOuUdADxWTj7ptU7aJSZhwHyZthpsq7d 6y2JxDIhxi2trmK3TaOfPf5yXHUdt9d6/sV3Z/gD7e8nSKBnI8ZZ/dGHk7/PLpsh AxqImzwPi1jldTxcE/LPXJ4wyEWF1FVGCIhyBJhASdn0HkjpuWKCjFVHYDmbEaRU LNZ0iJnNGHTiMfOxLpp/SsushQQYNkAdcQWlZVSJ31JgYSV/kx0XvgU/A96Cikjx 6To+Rxp6xB1Hn5IjC4RMaUcaZy0qbBsywmWVNDGeIfCDCLIg306sABRtY0Q1HmBR mTH4K0bmGlj6FgRuQXewquSNnytuLCELh8rUErNuK1UM2obHyYKlehFyYRifJZwh IOj2izQFj+6krGjpepP/5yHRRgQ2iwBchCqFr6QoJZYKt1c80kqUrUWKGSYyojq7 JghRa61zEptePqlnHO/9heudUFkBVght3DS8+LsTqi9Su7Kwlqg= =0Pdu -----END PGP SIGNATURE----- --Apple-Mail=_C3334CE5-ACF2-45E3-8874-D2467ED173AD-- From nobody Sun May 7 22:24:52 2023 X-Original-To: freebsd-arch@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 4QDzWR5mYXz49cHq for ; Sun, 7 May 2023 22:25:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) (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 "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QDzWR3KTSz3lLt for ; Sun, 7 May 2023 22:25:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x62f.google.com with SMTP id a640c23a62f3a-965f7bdab6bso476656366b.3 for ; Sun, 07 May 2023 15:25:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1683498303; x=1686090303; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=9MDL7g+qankNW5HDb7eKTuBPpA290CIqQVPmY97yJe4=; b=sqBygtmSjj+NEcZuSaG411xorAXZDDch8AzlJOXDDjoSTbgIMv8e5ROjiqKste7Fxt pHScaCeFQemJsgQDOMsZ91DAEc27Ny3mPcQtpqHhcukEtTzvL25QqJZRQQkwoX2RuPZ9 yc9xSjJX2b0LyOV4hUuUP6e1a9Rx/j9hO4VdXcgpm+vpAgN9y/pReDuNxcr0i2ISFhvR sfO9kSshpTJiCJLLqs+wsII+OVio7fCihIH/bC/8Vu2yTdGvF4hFW4BvRTtSuOxbo17p PFQXbIhTB3Smt3XOYAODK6jkDv6LsmB5kNnHTMhYx9+074pDwOgyfq7OR7hUlbPhqX8g 49/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683498303; x=1686090303; 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=9MDL7g+qankNW5HDb7eKTuBPpA290CIqQVPmY97yJe4=; b=iRgWYkpubRdKI6V+d6F+RFBOKGMsMrMHibLbC/1XIRk6ZPGP+yaDAzM8witmbax3ND FUHUkBC/GE25GtAiMUxycSMraIyDSsKTdjddfaqckc69NBn19xR0C8jmQ4o3FN/CsQKa lz2dPD4HWjOnicrVyIXuxXhkAa4ud6iz+Gn9RFGNSGkbdf1pZ9PVPkPMEKIF59SlUpFZ rFbHkrvMywCbh5DewuI6g/WRv7xSsl1g9D9Vbj5nfu+KvafpFFtT6TMlpM8IQkrLvX3c GHC64/KmP8JSnRbveAvz+AgdM0hiVAs/m9sI6RReLsbSijSr9dD8SbTlGz+/JrpSsbO4 xLfg== X-Gm-Message-State: AC+VfDyi/dPVUFVX9puLTlmZPvQxrKy6xtPUA50HBO8SQSDOHEpDHddJ hJWvDDC6tGARxcwyFl6XJBHl86oxoPXagoRzbXBA+A== X-Google-Smtp-Source: ACHHUZ4W1tXF9nfWdOWnqV5fKqsJAoYS338za8SBVweS4Vhc3/xOczvMfwkOP9k8FMPSWwJHufjUAtC1pSZ8cgZklE8= X-Received: by 2002:a17:907:72d6:b0:960:f1a6:6a12 with SMTP id du22-20020a17090772d600b00960f1a66a12mr7616641ejc.55.1683498303455; Sun, 07 May 2023 15:25:03 -0700 (PDT) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Sun, 7 May 2023 16:24:52 -0600 Message-ID: Subject: Re: Support for more than 256 CPU cores To: Moin Rahman Cc: Ed Maste , freebsd-arch , FreeBSD Current Content-Type: multipart/alternative; boundary="0000000000005b94b605fb21fe84" X-Rspamd-Queue-Id: 4QDzWR3KTSz3lLt X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --0000000000005b94b605fb21fe84 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, May 7, 2023, 3:51 PM Moin Rahman wrote: > > > > On May 5, 2023, at 3:38 PM, Ed Maste wrote: > > > > FreeBSD supports up to 256 CPU cores in the default kernel configuratio= n > > (on Tier-1 architectures). Systems with more than 256 cores are > > available now, and will become increasingly common over FreeBSD 14=E2= =80=99s > > lifetime. The FreeBSD Foundation is supporting the effort to increase > > MAXCPU, and PR269572[1] is open to track tasks and changes. > > > > As a project we have scalability work ahead of us to make best use of > > high core count machines, but at a minimum we should be able to boot a > > GENERIC kernel on such systems, and have an ABI for the FreeBSD 14 > > release that supports such a configuration. > > > > Some changes have already been committed in support of increased MAXCPU= , > > including increasing MAX_APIC_ID (commit c8113dad7ed4) and a number of > > changes to reduce bloat (such as commits 42f722e721cd, e72f7ed43eef, > > 78cfa762ebf2 and 74ac712f72cf). > > > > The next step is to increase the maximum cpuset size for userland. > > I have this change open in review D39941[2] and an exp-run request in > > PR271213[3]. Following that the kernel change for increasing MAXCPU is > > in D36838[4]. > > > > Additional work on bloat reduction will continue after this change, and > > looking forward FreeBSD is going to need ongoing effort from the > > community and the FreeBSD Foundation to continue improving scalability. > > > > [1] https://bugs.freebsd.org/269572 > > [2] https://reviews.freebsd.org/D39941 > > [3] https://bugs.freebsd.org/271213 > > [4] https://reviews.freebsd.org/D36838 > > > > By any chance will this be merged into 13? > Nope. It breaks too many kernel KBIs that are exposed to at least some modules. Warner > > Kind regards, > Moin > --0000000000005b94b605fb21fe84 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sun, May 7, 2023, 3:51 PM Moin Rahman <bofh@freebsd.org> wrote:


> On May 5, 2023, at 3:38 PM, Ed Maste <emaste@freebsd.org> wr= ote:
>
> FreeBSD supports up to 256 CPU cores in the default kernel configurati= on
> (on Tier-1 architectures).=C2=A0 Systems with more than 256 cores are<= br> > available now, and will become increasingly common over FreeBSD 14=E2= =80=99s
> lifetime.=C2=A0 The FreeBSD Foundation is supporting the effort to inc= rease
> MAXCPU, and PR269572[1] is open to track tasks and changes.
>
> As a project we have scalability work ahead of us to make best use of<= br> > high core count machines, but at a minimum we should be able to boot a=
> GENERIC kernel on such systems, and have an ABI for the FreeBSD 14
> release that supports such a configuration.
>
> Some changes have already been committed in support of increased MAXCP= U,
> including increasing MAX_APIC_ID (commit c8113dad7ed4) and a number of=
> changes to reduce bloat (such as commits 42f722e721cd, e72f7ed43eef, > 78cfa762ebf2 and 74ac712f72cf).
>
> The next step is to increase the maximum cpuset size for userland.
> I have this change open in review D39941[2] and an exp-run request in<= br> > PR271213[3].=C2=A0 Following that the kernel change for increasing MAX= CPU is
> in D36838[4].
>
> Additional work on bloat reduction will continue after this change, an= d
> looking forward FreeBSD is going to need ongoing effort from the
> community and the FreeBSD Foundation to continue improving scalability= .
>
> [1] https://bugs.freebsd.org/269572
> [2] https://reviews.freebsd.org/D39941
> [3] https://bugs.freebsd.org/271213
> [4] https://reviews.freebsd.org/D36838
>

By any chance will this be merged into 13?

Nope. It breaks too many kernel K= BIs that are exposed to at least some modules.

<= /div>
Warner

Kind regards,
Moin
--0000000000005b94b605fb21fe84-- From nobody Sun May 7 23:10:14 2023 X-Original-To: freebsd-arch@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 4QF0Wc63rdz49gLn for ; Sun, 7 May 2023 23:10:20 +0000 (UTC) (envelope-from rebecca@bsdio.com) Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (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 4QF0Wb27cZz3pLY; Sun, 7 May 2023 23:10:19 +0000 (UTC) (envelope-from rebecca@bsdio.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdio.com header.s=fm1 header.b=rS184AIS; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=i9fC+oBf; spf=pass (mx1.freebsd.org: domain of rebecca@bsdio.com designates 64.147.123.19 as permitted sender) smtp.mailfrom=rebecca@bsdio.com; dmarc=none Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 16AD6320070D; Sun, 7 May 2023 19:10:17 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sun, 07 May 2023 19:10:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdio.com; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm1; t= 1683501016; x=1683587416; bh=T0K6ubkSJjvAiAqUEG0lalVYeWcjYvOYSlW 4PchAysA=; b=rS184AIS18m5eQArdHa3mLJCbVcDwY5SIPQ0pOd7XfdWcCqCCur Z54oPQZIsRlM0eALiUIExL1u1c7htfjEbNUlzUx6QAxEIdTaOTTc5srfEy4KXg70 kaFNVnlq0d9ij0ZA8CQ4FxuX9pb/Pr4GpGXl7I11AkmVYJLeboaVjXdl5OrUBG84 30kXJ079+AXEvuRiS4I5OivvvAq3uVMD6p2Zo4gfmxMt1cs6V+A1Wp1WTXc2HQxZ I4WrpiSXDh7BxdDzVNgB5WdBhSIEpWI6N/8aspIHOxnEPOfeL/Aiu/vtrcYTP+Zo 6N11E2m/igfkpRNtpqBBoA+lc2HdO8zCp9g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1683501016; x=1683587416; bh=T0K6ubkSJjvAiAqUEG0lalVYeWcjYvOYSlW 4PchAysA=; b=i9fC+oBfOqh2/6Gl9hcZthGPZJbhhGYh5LD84VEEzQvbvNyNlIL lSUKEU5AmtSCsbMdFYSQWQbNgzGjCRL7MoTXPeOZP3RvKC+MZjX2e6PeGlmNUwvd NhYpqG0/y+s7a0YZbJodpmjTTiRYHAyBvtpgm6BA25ByFbpBYGyHjJC8igjfevXu BjNKFdVMImqp8AxCsx+skuCR9zwsj3lff1NK6WZMi1rmR8HJW1dWQuxwB6Dv/uVy lKJf9pAZmsaeW0eqK2gy9kCHdC7cAy831OmsxJXMHh7qWm/DdwHRzD4mE95lkjzT IC2pyv7JsssbOH+hzKA+erItP9sLNexfcPg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeefjedgvddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfevfhfhjggtgfesth ekredttdefjeenucfhrhhomheptfgvsggvtggtrgcuvehrrghnuceorhgvsggvtggtrges sghsughiohdrtghomheqnecuggftrfgrthhtvghrnhepueevtdffieeuveeitdellefhie fgleevkedugfejleekudelgfdtkefhkefhudeunecuffhomhgrihhnpehmohhnohdqphhr ohhjvggtthdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehrvggsvggttggrsegsshguihhordgtohhm X-ME-Proxy: Feedback-ID: i5b994698:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 7 May 2023 19:10:15 -0400 (EDT) Message-ID: <5b809b1e-24d2-1654-824c-f8367d7ef0d5@bsdio.com> Date: Sun, 7 May 2023 17:10:14 -0600 List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: Future of 32-bit platforms (including i386) Content-Language: en-US To: Jessica Clarke , Hans Petter Selasky Cc: freebsd-arch , John Baldwin References: <671d3bf6-b207-e7c5-5282-4df317193db6@selasky.org> From: Rebecca Cran In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-4.51 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.91)[-0.905]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.19]; R_DKIM_ALLOW(-0.20)[bsdio.com:s=fm1,messagingengine.com:s=fm3]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.19:from]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arch@freebsd.org]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[bsdio.com:+,messagingengine.com:+]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; MID_RHS_MATCH_FROM(0.00)[]; DMARC_NA(0.00)[bsdio.com]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4QF0Wb27cZz3pLY X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N On 4/27/23 17:50, Jessica Clarke wrote: > I don’t know where to start with this other than to give an emphatic no to almost all of what you said, or at least the bits for which meaning can be extracted. Regardless, this is not the place for such pie-in-the-sky discussions; if you want to theorise about weird and wacky computer architectures then please take it elsewhere. It's hard enough to get it right when there's a single instruction set, as with Arm's big.LITTLE. For example: https://www.mono-project.com/news/2016/09/12/arm64-icache/ I've also heard of problems of programs crashing due to instructions supported on one core type not being supported on the other. -- Rebecca Cran From nobody Mon May 8 19:01:33 2023 X-Original-To: freebsd-arch@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 4QFVy75y8Nz4BFpW; Mon, 8 May 2023 19:01:35 +0000 (UTC) (envelope-from jhb@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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QFVy75WDCz40QD; Mon, 8 May 2023 19:01:35 +0000 (UTC) (envelope-from jhb@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1683572495; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=naNyuef0hEVh7ER6V5H6FTzeZ6VyxOxioyEBOv+r7W0=; b=lwLpfL+EO9D8N8A3ioCLYPhTtKqcuNJr+8c/b7w246n2kGtXJ2A+ONwfRvO8G3E4uPfVJa 3ULj4HyGj+N6T+ph26MOT1LsLSInLWEaQNMV1qbu4r7FF7AZXHI2P4paNc48l3J8Jq4EjV KJSWPogPvg2x/otJFySr6K7juEBZze4hO6nSWbQLf7rIwNYmcwZvYGKUTuuPBljakpudLd F0Du0L/L+4wmEN3wiaxYUbcfJs+vVKiL8THd0Za6ytBomrprlTp58kB1k/iPJwwVLYHErz FY4MeRzg0XKBPHJbE2Mci6pOW+87Kablq+ZW1DZcIweO0zzdD7Q+C2NzWN6+0A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1683572495; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=naNyuef0hEVh7ER6V5H6FTzeZ6VyxOxioyEBOv+r7W0=; b=HhDFcnIrwgvrTDa5tBfvXctD6VVLevsbrxm0A74FoKtMxuVjEFeh6cChxI9twgeF9jq7Gj oIRbs8ZcjfiThRtg/EKfzLgeha1iudAcWwSbAlr0amUInky4Czpm108MkSL/aisUxr0I2r fDiFTjQvJjfvNtCx1oZc5RXptroXFINOvHyoqHxzqlmQW2yx7PTREKL7Ha5oR2SRnFTtSz siFKA7bLvSRORL5yAF/w/Brcc6EsOtMDtzIU0Ps1qXbtvBTQAMGwmiSVHU4J0UwZA4yNVo q3JK9L3o8lZLkAynRucqHBntK/G9MlghATtv0WCc0y7K6QjA6CwWCaMeEo03uA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1683572495; a=rsa-sha256; cv=none; b=urh9GxT+/EPhnDSiwxSj9xWox540k4J8JxwxPG+dT/jA4HkbT6l8ESIcHHwNM58Z7x9XTH P7TKuKgc8EpnLWfPQZUnb5wzORAEmoWQxhKrU9n49UCaZgWlJXmz0jvIwSvlZNaBEkILI7 eTH0GWF+nvNCQ1YhpUYaNyh+8JDp+ub5sFu1MPKvAoNRvEMB1N89ZaH+vVF6u0fBRjZyjP PNX3PO96ZQaTb+8GOQRP6pn7LuJSEhMPhWtNkws9CoZqW65R/Il0vL8sDYAoyjnENmdThW rV7nqcB2u+/E3jJlRjdkqn99zNmJKfdZA+pRHt8OZLQoqMbqQmG4V5lHoWuLfw== Received: from [IPV6:2601:648:8680:16b0:9597:2b45:6d3:31cd] (unknown [IPv6:2601:648:8680:16b0:9597:2b45:6d3:31cd]) (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: jhb) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QFVy72Cbvzy7H; Mon, 8 May 2023 19:01:35 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Message-ID: <5e59d762-6f58-46a4-bceb-de7fcb87682d@FreeBSD.org> Date: Mon, 8 May 2023 12:01:33 -0700 List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 Subject: Re: Support for more than 256 CPU cores Content-Language: en-US To: Ed Maste , freebsd-arch , FreeBSD Current References: From: John Baldwin In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-ThisMailContainsUnwantedMimeParts: N On 5/5/23 6:38 AM, Ed Maste wrote: > FreeBSD supports up to 256 CPU cores in the default kernel configuration > (on Tier-1 architectures). Systems with more than 256 cores are > available now, and will become increasingly common over FreeBSD 14’s > lifetime. The FreeBSD Foundation is supporting the effort to increase > MAXCPU, and PR269572[1] is open to track tasks and changes. > > As a project we have scalability work ahead of us to make best use of > high core count machines, but at a minimum we should be able to boot a > GENERIC kernel on such systems, and have an ABI for the FreeBSD 14 > release that supports such a configuration. > > Some changes have already been committed in support of increased MAXCPU, > including increasing MAX_APIC_ID (commit c8113dad7ed4) and a number of > changes to reduce bloat (such as commits 42f722e721cd, e72f7ed43eef, > 78cfa762ebf2 and 74ac712f72cf). > > The next step is to increase the maximum cpuset size for userland. > I have this change open in review D39941[2] and an exp-run request in > PR271213[3]. Following that the kernel change for increasing MAXCPU is > in D36838[4]. > > Additional work on bloat reduction will continue after this change, and > looking forward FreeBSD is going to need ongoing effort from the > community and the FreeBSD Foundation to continue improving scalability. > > [1] https://bugs.freebsd.org/269572 > [2] https://reviews.freebsd.org/D39941 > [3] https://bugs.freebsd.org/271213 > [4] https://reviews.freebsd.org/D36838 FWIW, I think it will be useful for main to run with a larger userspace MAXCPU than kernel for at least a while so that we have better testing of that configuration and to give headroom for bumping MAXCPU in the kernel during the 14.x branch. The only other viable path I think which would be more work would be to rework cpuset_t in userspace to always use a dynamically sized mask. This could perhaps be done in an API-preserving manner by making cpuset_t an opaque wrapper type in userland and requiring CPU_* to indirect to functions in libc, etc. That's a fair bit more work however. -- John Baldwin From nobody Mon May 8 20:11:12 2023 X-Original-To: freebsd-arch@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 4QFXVk3X0cz4BKCC for ; Mon, 8 May 2023 20:11:26 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-lj1-f175.google.com (mail-lj1-f175.google.com [209.85.208.175]) (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 "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QFXVj3qxcz4Cpk for ; Mon, 8 May 2023 20:11:25 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.208.175 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com; dmarc=none Received: by mail-lj1-f175.google.com with SMTP id 38308e7fff4ca-2ad89c7a84fso23186991fa.2 for ; Mon, 08 May 2023 13:11:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683576683; x=1686168683; 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=jNzHEeJacU+uV1M5yv78eb45CSb750JBu+ZGpwAdwtk=; b=lr7vXkc7Bbk2LJwpFRKhB+iw7AchnxBhlBa+nhudpMdhl163GYSzyIYrDFTlTq5S7t MsGA0N1AS/IXeSb6XCTwhTW5jMPG+sD4PKZeFNgqrWnT4QMK1O54fTCAl0+3QbhvGJXy WZHTzliFTnWUZLmNsd3lZjLyxZoezJcOT+K585yvmWAUTG7sSwE3ztbNB2GbMs5vGti6 oo4zmfeyQkgPe5jHVFou/wyIcWrfxnbz7AuS51clkm6G7n4zgGc92C1OqPi18ADEm6D6 fN6vYO5XxrqG5HGeJC2YMwqfYX7f7THIE5GCfBl5q/fFxdIuqhqWswtzohId9OMVQUia nSdw== X-Gm-Message-State: AC+VfDxE3MGO2i3znV6nFNapDm40/BQPGrwddPqxXIvo+dvtoammkXqy eTvgO5ady9GADT79UL/NCUiLmAr28pOWeGFzPIuVXaNd2bk= X-Google-Smtp-Source: ACHHUZ6VRvQS6x13ya6BGmrvFU4O+4Hfz+RqfqW2MdobRa1zAcQRwChEWm/9wQzWnpKfjlHmaY6I4EhYDZwMm3YwpJU= X-Received: by 2002:a2e:8803:0:b0:2ab:1b57:6e3d with SMTP id x3-20020a2e8803000000b002ab1b576e3dmr73774ljh.51.1683576683175; Mon, 08 May 2023 13:11:23 -0700 (PDT) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 References: <12f8559c-d696-5344-98d5-1751d04088af@FreeBSD.org> In-Reply-To: From: Ed Maste Date: Mon, 8 May 2023 16:11:12 -0400 Message-ID: Subject: Re: OpenSSL 3.0 for 14.0-RELEASE: issues with 1.x/3.x symbol clashing, ports linking against base OpenSSL, ports that don't compile/link against OpenSSL 3, etc To: Pierre Pronchery Cc: freebsd-arch@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-1.45 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_HAM_LONG(-1.00)[-0.998]; NEURAL_SPAM_MEDIUM(0.55)[0.549]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-arch@freebsd.org]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.208.175:from]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; R_DKIM_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; RCVD_IN_DNSWL_NONE(0.00)[209.85.208.175:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[carpeddiem]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arch@freebsd.org]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4QFXVj3qxcz4Cpk X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N On Fri, 5 May 2023 at 16:03, Ed Maste wrote: > > I had a look at the remaining build failures with your changes merged > in, and I see errors due to deprecation notices in: For the simple cases where deprecation notices are the only issue we can just set OPENSSL_API_COMPAT=0x10100000L to specify the API in use explicitly. We can do this in advance of bringing in OpenSSL 3; it will just be a NFC at present. I've done this for bhyve just now, with commit 9c6f3dfda6dd. We can do the same for the other components using OpenSSL, and can switch each of these to using OpenSSL 3 APIs at some point after we import OpenSSL 3. From nobody Tue May 9 18:12:11 2023 X-Original-To: freebsd-arch@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 4QG5pk18QJz49HwK for ; Tue, 9 May 2023 18:12:14 +0000 (UTC) (envelope-from des@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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QG5pk0L6wz4Hjf; Tue, 9 May 2023 18:12:14 +0000 (UTC) (envelope-from des@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1683655934; 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=5ZbGwWiM2XCadY2wkQHRC8Jnx3qH8rVBvmT1wiZTWlY=; b=dmoL+oNhpTcQl7D/U05cx4pbAFfLDPXAvFIilYy2ydbiV5yOhZ6G/4SIdj+mfTeqHpIXGc IZD1YhTJD/gUqc1bq78vsU9X3tbDbzPMr723Q3kgQkLJzutIPCtHim3dKY1s5W2+ku8niY jyTFcjYl//b20N//wYoLnfX8/iW5HYEvy3hFyQ/BxJvEqWRp9IG+aKNiorTbPvB9xoZuQt XYzpwz9qUVNE3BuJGJC8Ycz19g5PogQpZ8LVOhLV0QUOq9JWhVEezRlFrPBDVh0PV5R9jK NFu27gbSQynSlMvJESK0Aa/3Z3js25ITfciubsfda9Cj92l4AgdcZl+A55x6yg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1683655934; 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=5ZbGwWiM2XCadY2wkQHRC8Jnx3qH8rVBvmT1wiZTWlY=; b=tiCY9dF8VGzk2VEX62y7ZTJFihlsKN1FCpmYtzu61dXqg6Tqb+OqEEKvYpnu7ci62T+HD3 jdKBmONKQ8jWAxum1ttyD2OFMV/kMQaZ7woV3CBi1n5BV+GOplApxXM7ksbE9Ptj2cuP7e NKKWXrRBzYjtGzD2VuJyZ6/9aiip0gX0zpdY5KwQrGVNSLz2sE058fALthLa2IWQNgcBa1 mLvSGkIe/DjRpVdsXoa1VHca8KrNxBcMSKWV5okJQTD4xJSUDllKKpmEx+vRXWMeuXR5bF qqm7tEBpl43uj4ABPnr9gvB0IhUXv7xtURQFBIEJj+b+ESrNc41baKUi8uaFDg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1683655934; a=rsa-sha256; cv=none; b=tucMVczYFos6q0TmeHvmevAOP8yyoCwqgBxbO31KCNjBzXmDpBx8aUKeHHUlkySU9L2WuB rAzX60UmnMvM6UUqlgAEmZP6inrofQoryE8Z9fsCL1hEv9V21M7xBVA8p02G3uMWFJCYoJ 2wWjHuc74AVcr5Kx3ogjkm5GJsjDiQp1qYixYQpVu0uoQ7rxK3O5VQ3EctmhJGMbQ3C+Vq u2cHQuYCpWdTlkqtDfGrwsxASMRbLdOyOucHO3d68qWZsgnb9jqiIiB4wJOS/1uHzmWmCR FaC7cocaB6DcdJAuZ2N9JkMCzfkjzhVh3CnTmNDQvqiagsMwFqyXSbb8zx8Mfg== Received: from ltc.des.no (unknown [88.169.161.78]) (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: des) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QG5pj5tc5zPmn; Tue, 9 May 2023 18:12:13 +0000 (UTC) (envelope-from des@freebsd.org) Received: by ltc.des.no (Postfix, from userid 1001) id F0F1C315AC; Tue, 9 May 2023 20:12:11 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Xin LI Cc: Pierre Pronchery , freebsd-arch@freebsd.org Subject: Re: OpenSSL 3.0 for 14.0-RELEASE: issues with 1.x/3.x symbol clashing, ports linking against base OpenSSL, ports that don't compile/link against OpenSSL 3, etc In-Reply-To: (Xin LI's message of "Wed, 3 May 2023 16:55:07 -0700") References: <12f8559c-d696-5344-98d5-1751d04088af@FreeBSD.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (berkeley-unix) Date: Tue, 09 May 2023 20:12:11 +0200 Message-ID: <86y1lxwf0k.fsf@ltc.des.no> List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-ThisMailContainsUnwantedMimeParts: N Xin LI writes: > On an unrelated note, the digest authentication support for libfetch > only MD5; RFC 7616 proposed newer digest algorithms, but as far as I > know there is no commonly used server supporting it, possibly because > people are moving to basic authentication over https nowadays. Should > we just remove the support at some point in the future? I'd rather not. We can just switch back to libmd for digest auth. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@FreeBSD.org From nobody Thu May 11 04:30:51 2023 X-Original-To: freebsd-arch@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 4QGzVL3D1Bz49dVH for ; Thu, 11 May 2023 04:31:06 +0000 (UTC) (envelope-from freebsd-arch@m.gmane-mx.org) Received: from ciao.gmane.io (ciao.gmane.io [116.202.254.214]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4QGzVK20Dmz4DRZ for ; Thu, 11 May 2023 04:31:05 +0000 (UTC) (envelope-from freebsd-arch@m.gmane-mx.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of freebsd-arch@m.gmane-mx.org designates 116.202.254.214 as permitted sender) smtp.mailfrom=freebsd-arch@m.gmane-mx.org; dmarc=none Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1pwxxC-00062V-Io for freebsd-arch@freebsd.org; Thu, 11 May 2023 06:30:58 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-arch@freebsd.org From: Pierre Pronchery Subject: Re: OpenSSL 3.0 for 14.0-RELEASE: issues with 1.x/3.x symbol clashing, ports linking against base OpenSSL, ports that don't compile/link against OpenSSL 3, etc Date: Thu, 11 May 2023 06:30:51 +0200 Organization: FreeBSD Foundation Message-ID: References: <12f8559c-d696-5344-98d5-1751d04088af@FreeBSD.org> List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Content-Language: en-US In-Reply-To: X-Spamd-Result: default: False [0.43 / 15.00]; FORGED_MUA_THUNDERBIRD_MSGID_UNKNOWN(2.50)[]; NEURAL_HAM_SHORT(-0.98)[-0.977]; NEURAL_HAM_LONG(-0.97)[-0.971]; NEURAL_HAM_MEDIUM(-0.62)[-0.622]; MV_CASE(0.50)[]; FORGED_SENDER(0.30)[pierre@freebsdfoundation.org,freebsd-arch@m.gmane-mx.org]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; FROM_NEQ_ENVFROM(0.00)[pierre@freebsdfoundation.org,freebsd-arch@m.gmane-mx.org]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:24940, ipnet:116.202.0.0/16, country:DE]; MLMMJ_DEST(0.00)[freebsd-arch@freebsd.org]; RCVD_TLS_LAST(0.00)[]; HAS_ORG_HEADER(0.00)[]; DMARC_NA(0.00)[freebsdfoundation.org]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4QGzVK20Dmz4DRZ X-Spamd-Bar: / X-ThisMailContainsUnwantedMimeParts: N Hi everyone, It's been a long and tough fight, but I finally managed to complete a `make buildworld` on amd64 with the latest state of my work on OpenSSL 3; see https://github.com/freebsd/freebsd-src/pull/740 for a first draft of a pull-request via GitHub. I will probably not be able to work on this again until the DevSummit at BSDCan, so feel free to take it from there until then. HTH! -- khorben On 5/8/23 22:11, Ed Maste wrote: > On Fri, 5 May 2023 at 16:03, Ed Maste wrote: >> >> I had a look at the remaining build failures with your changes merged >> in, and I see errors due to deprecation notices in: > > For the simple cases where deprecation notices are the only issue we > can just set OPENSSL_API_COMPAT=0x10100000L to specify the API in use > explicitly. We can do this in advance of bringing in OpenSSL 3; it > will just be a NFC at present. I've done this for bhyve just now, with > commit 9c6f3dfda6dd. We can do the same for the other components using > OpenSSL, and can switch each of these to using OpenSSL 3 APIs at some > point after we import OpenSSL 3. -- Pierre Pronchery From nobody Thu May 11 07:22:44 2023 X-Original-To: freebsd-arch@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 4QH3Jg5JMtz49rLy for ; Thu, 11 May 2023 07:22:59 +0000 (UTC) (envelope-from antoine.brodin.freebsd@gmail.com) Received: from mail-lf1-f51.google.com (mail-lf1-f51.google.com [209.85.167.51]) (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 "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QH3Jg1q7pz3Jfj for ; Thu, 11 May 2023 07:22:59 +0000 (UTC) (envelope-from antoine.brodin.freebsd@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lf1-f51.google.com with SMTP id 2adb3069b0e04-4f2510b2b98so5038371e87.3 for ; Thu, 11 May 2023 00:22:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683789777; x=1686381777; 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=rjrd1/MaCj4zurRCAX++xVEsEuJ7j/1bROjHX9C/9xo=; b=I6WaUo7UTxZKgJTjwZXNhHV/imWnZHxWdLXG5pMDoZR+jBtT4n1qqBWlaBxpdnxrSd WKOl+Fg+9t/bu/QPkxHB7PcwFdyD7TfpiC0eDwrIZBHRMvLzBHo5mZ39dSjw+su5jOcn gFzzyU+c1+ijrG9TIJzuZjPHPHx/aKKMHSps9PmESKh6DWci5XoKvOI4lK2Y9lW8welO t+rRtnVMn3KOYNjdGiV68gT2eMUF9rhp3lDaCkaV/O+2v0Pu1RV0OdSViH6jHQWOof8H Dsf+BIdRxVo9/UKFCL2TnzLyOJ3q8QrHP39gOQTkxFEZoZQLwn+LRa7OEYxLXAieUnib sAoA== X-Gm-Message-State: AC+VfDxLT6ezbagNG1qaIFwZeaBlUbHdScvnSKTRRWazd6zv+RD3Ylz0 hTiPFzt8tWNbvIPM/m9a2cErSq0q+vr1O8GRA2E= X-Google-Smtp-Source: ACHHUZ5It8pCsDpmBpQnPWzEnW6QzA/VK57+PzZuwMTNTRsWKf5AzyLFWHgRDvXAOBr/01EsNSJXhW/+snsPp0I8+l0= X-Received: by 2002:ac2:546b:0:b0:4f1:430d:ca5c with SMTP id e11-20020ac2546b000000b004f1430dca5cmr2821563lfn.56.1683789777212; Thu, 11 May 2023 00:22:57 -0700 (PDT) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 References: <12f8559c-d696-5344-98d5-1751d04088af@FreeBSD.org> In-Reply-To: From: Antoine Brodin Date: Thu, 11 May 2023 09:22:44 +0200 Message-ID: Subject: Re: OpenSSL 3.0 for 14.0-RELEASE: issues with 1.x/3.x symbol clashing, ports linking against base OpenSSL, ports that don't compile/link against OpenSSL 3, etc To: Pierre Pronchery Cc: freebsd-arch@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4QH3Jg1q7pz3Jfj X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Thu, May 11, 2023 at 6:31=E2=80=AFAM Pierre Pronchery wrote: > > Hi everyone, > > It's been a long and tough fight, but I finally managed to complete a > `make buildworld` on amd64 with the latest state of my work on OpenSSL > 3; see https://github.com/freebsd/freebsd-src/pull/740 for a first draft > of a pull-request via GitHub. > > I will probably not be able to work on this again until the DevSummit at > BSDCan, so feel free to take it from there until then. > > HTH! > -- khorben Thanks, I have this error during buildworld: =3D=3D=3D> secure/lib/libcrypto/modules/fips (all) make[6]: /usr/obj/poudriere/data/src-openssl3/amd64.amd64/secure/lib/libcry= pto/modules/fips/.depend, 1: ignoring stale .depend for /usr/obj/poudriere/data/src-openssl3/amd64.amd64/tmp/usr/lib/libcrypto.a building shared library fips.so cc -target x86_64-unknown-freebsd14.0 --sysroot=3D/usr/obj/poudriere/data/src-openssl3/amd64.amd64/tmp -B/usr/obj/poudriere/data/src-openssl3/amd64.amd64/tmp/usr/bin -Wl,-zrelro -fstack-protector-strong -shared -Wl,-x -Wl,--fatal-warnings -Wl,--warn-shared-textrel -o fips.so.full -Wl,-soname,fips.so fips_entry.pico fipsprov.pico self_test.pico self_test_kats.pico -lcrypto ld: error: unable to find library -lcrypto cc: error: linker command failed with exit code 1 (use -v to see invocation= ) *** Error code 1 Antoine > On 5/8/23 22:11, Ed Maste wrote: > > On Fri, 5 May 2023 at 16:03, Ed Maste wrote: > >> > >> I had a look at the remaining build failures with your changes merged > >> in, and I see errors due to deprecation notices in: > > > > For the simple cases where deprecation notices are the only issue we > > can just set OPENSSL_API_COMPAT=3D0x10100000L to specify the API in use > > explicitly. We can do this in advance of bringing in OpenSSL 3; it > > will just be a NFC at present. I've done this for bhyve just now, with > > commit 9c6f3dfda6dd. We can do the same for the other components using > > OpenSSL, and can switch each of these to using OpenSSL 3 APIs at some > > point after we import OpenSSL 3. > > -- > Pierre Pronchery > > From nobody Thu May 11 14:54:25 2023 X-Original-To: freebsd-arch@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 4QHFKq1Pwrz4BKl2 for ; Thu, 11 May 2023 14:54:39 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (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 "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHFKp50s9z4WSl; Thu, 11 May 2023 14:54:38 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pf1-x42e.google.com with SMTP id d2e1a72fcca58-64115e652eeso58572655b3a.0; Thu, 11 May 2023 07:54:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683816877; x=1686408877; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=QxLTMbyfm+C4UKzIKPveQ3RO32lavbd2bra0+ZMjGeI=; b=YvD0KRV2Rt5lYT2zt0/3gahWSiLea5dP7q1W9E7gKxwrp7uO+gsJ40uMNVH/f8jbNt qq98ve8IvxSTQOpNjZZ9WWzPtedgoGsS0F6S3sRiiM729tN7kJjC3cCbHFDeKjqp6TvQ MUZjCxg9TgJZgkqDV0/ImcLLWTWqsNUP8ZtrXbALKD4czfrAYcEF88WCN4J5bYpwnq/q Otots+zhPdHxqVoBQjkvvfBM6Cse89/2MC+SQyP9p9FIW/LQ57vgWARtgse3hbS90Poz GGNJFkWRr87T5KWWy6afp/03l1IANJmpMGRdcORD9rDOrGujH7OZlcMqWNw51BZMUGeV crnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683816877; x=1686408877; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=QxLTMbyfm+C4UKzIKPveQ3RO32lavbd2bra0+ZMjGeI=; b=HjCgy8Ixzd1X3pCqWfipzI7wj+8S1u1xJU6VPYO9Sv4kEBoM8SiBeQu/7YjphYdchF zoKPvOGP924dqiNvQDHfvLugMrhPPRoQCVWfuUY66IOgtMZLiBttTm1Ts7odRRPn+tzw HqWtGglaY9bmz9pBKMS1jei0LcQ8wXsxMdtZITV719Kii64cGZ1EFfxws3A8O8EUr1Jd VD6hzImwa+clFoF8/xlkv8euAdQDogEJnEMdTfbSZMmNQWlBTz19Wq9fRj6qv9Tm+SUt tQ8l04c43gj/ERQkMwPR+SgBxagySxtLS3b7yujMlmMteacqD73DlaqoCUULkOIcO8Sl xLoQ== X-Gm-Message-State: AC+VfDx6jj8D8fYa6utq3TmmKtmmxxxehKjJWLnDvCSpzMfll+nlGAUB PI+Psk/5yN/QpNRLxrsORrBffvzACxU= X-Google-Smtp-Source: ACHHUZ42SFA6yZAQThFoC78EtUFkWRWNSdG+B9GQAzQa+q6f2hlSshX4ew3sV55FahiChV+M/17l1g== X-Received: by 2002:a05:6a00:1da9:b0:645:834c:f521 with SMTP id z41-20020a056a001da900b00645834cf521mr14252392pfw.17.1683816876664; Thu, 11 May 2023 07:54:36 -0700 (PDT) Received: from smtpclient.apple (c-73-19-52-228.hsd1.wa.comcast.net. [73.19.52.228]) by smtp.gmail.com with ESMTPSA id u18-20020aa78492000000b006470a6ef529sm5001320pfn.88.2023.05.11.07.54.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 11 May 2023 07:54:36 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Enji Cooper List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org Mime-Version: 1.0 (1.0) Subject: Re: OpenSSL 3.0 for 14.0-RELEASE: issues with 1.x/3.x symbol clashing, ports linking against base OpenSSL, ports that don't compile/link against OpenSSL 3, etc Date: Thu, 11 May 2023 07:54:25 -0700 Message-Id: References: Cc: Pierre Pronchery , freebsd-arch@freebsd.org In-Reply-To: To: Antoine Brodin X-Mailer: iPhone Mail (20D67) X-Rspamd-Queue-Id: 4QHFKp50s9z4WSl X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > On May 11, 2023, at 00:23, Antoine Brodin wrote: >=20 > =EF=BB=BFOn Thu, May 11, 2023 at 6:31=E2=80=AFAM Pierre Pronchery > wrote: >>=20 >> Hi everyone, >>=20 >> It's been a long and tough fight, but I finally managed to complete a >> `make buildworld` on amd64 with the latest state of my work on OpenSSL >> 3; see https://github.com/freebsd/freebsd-src/pull/740 for a first draft >> of a pull-request via GitHub. >>=20 >> I will probably not be able to work on this again until the DevSummit at >> BSDCan, so feel free to take it from there until then. >>=20 >> HTH! >> -- khorben >=20 > Thanks, I have this error during buildworld: >=20 > =3D=3D=3D> secure/lib/libcrypto/modules/fips (all) > make[6]: /usr/obj/poudriere/data/src-openssl3/amd64.amd64/secure/lib/libcr= ypto/modules/fips/.depend, > 1: ignoring stale .depend for > /usr/obj/poudriere/data/src-openssl3/amd64.amd64/tmp/usr/lib/libcrypto.a > building shared library fips.so > cc -target x86_64-unknown-freebsd14.0 > --sysroot=3D/usr/obj/poudriere/data/src-openssl3/amd64.amd64/tmp > -B/usr/obj/poudriere/data/src-openssl3/amd64.amd64/tmp/usr/bin > -Wl,-zrelro -fstack-protector-strong -shared -Wl,-x > -Wl,--fatal-warnings -Wl,--warn-shared-textrel -o fips.so.full > -Wl,-soname,fips.so fips_entry.pico fipsprov.pico self_test.pico > self_test_kats.pico -lcrypto > ld: error: unable to find library -lcrypto > cc: error: linker command failed with exit code 1 (use -v to see invocatio= n) > *** Error code 1 Good find! The modules directory will likely need to be built in a later stage of world= (after libcrypto has been installed). That, or LDFLAGS needs to be adjusted= to find libcrypto in the build tree. Adjusting LDFLAGS is likely the easiest path forward. -Enji= From nobody Thu May 11 15:45:18 2023 X-Original-To: freebsd-arch@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 4QHGSV0vqrz4BNNc for ; Thu, 11 May 2023 15:45:30 +0000 (UTC) (envelope-from kevans@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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHGSV0QSkz4bNn; Thu, 11 May 2023 15:45:30 +0000 (UTC) (envelope-from kevans@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1683819930; 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=5a7otI97PcDGXdz/Cwi1/6odZaKer1veDNR5t0+ln8w=; b=VaHlO2+8zBw/IShMKblINpwIcPXXw8xQ5nV7nGstmpDzt+GYGIPD94Zx/V0TdW33s6WtIZ qe6YHtUDSCJsla3+65f2Cd7FkTOf8hvfBMHg2zFAJ2tHO3Ml5C+czqkBs8R4HxTch33wNf zvV5ie/rh+1cc54mPckSkXX3lwjy/DJLi8xCxmQM5Wvunygf038qiACgx1oYF6Bgyenh9e sCLIwVXS+99xfoJ7rsXfZeePTJfSiqIhzH57udzrrKlQi6Afr2CUBmHGTwl21zysoIhKKU outv6Sm4A4inoojHx2JsV4YOYvAZbU6P8+yNLly6oW8lz7RAxmucNJalahVBDQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1683819930; 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=5a7otI97PcDGXdz/Cwi1/6odZaKer1veDNR5t0+ln8w=; b=DK60CCO3xgfOE1DhkTcXfEPantoQSzE+IbG2OsusyyLhgngexuSJMsQmMwPivOMHOFdhD9 JV2WNNkE9aN2aJYTCDhNZ+WpMwvuuwLEK7Q8sCfs9ARzhYlFpnm4d0f6VMZBGuxUQHqyi9 X7ugy/vusIfcUkFOg3+fQslDdQgbrWg1qPDyPllmvOCDoLSpmb0wa98612BLkUQ9WdtMBM Nlw92wVMAEDAemL/Ii8w/DWUXmnCRLr9l+g7lDcccg6qW31AH8v6gwTycb3oE1Fc59DS8w tPjiKUr3qYNe5/J12POkswPcNHliM09Nl3i5Zg5Qx3BpeBCSJa5asBIY0pbYkQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1683819930; a=rsa-sha256; cv=none; b=TKkwEcE9Wr6mH3dCL7kt08TghN811G6i2yUTSP/LNFAb9CcrbRtDaLlvwYVlr9OW7GYGF9 SoASjC7pc7cgYa0NykZZeaZUFS/Ao4umIO5PxdJaW7cffdjp01MEVFkbTdHCF9l/b72Sb8 boYvw5bNWAwr9pMLFAOwJI+xlzzHk6CoaVrJ4AlEF4WWae1Vk+g7kaz0FvGcWq8ckRqsmU nNkrd+YcH6PdqwwtN41ansloKTGFJyo7izlhDjeVy7Rux+zACRCak1Y0PbqSio86pbXNWb Yj7iLMUZfLccMdzCVo511Ja3Tg+6ZevnHjjVq/9PjkYWgeK7EsWWiPt2Tzmm7Q== Received: from mail-qv1-f51.google.com (mail-qv1-f51.google.com [209.85.219.51]) (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 "GTS CA 1D4" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QHGST6MqSzMDL; Thu, 11 May 2023 15:45:29 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qv1-f51.google.com with SMTP id 6a1803df08f44-61b71b7803bso42266656d6.1; Thu, 11 May 2023 08:45:29 -0700 (PDT) X-Gm-Message-State: AC+VfDzV5yDDTW5L2BD7BLco9QriUhWnH+HOgXMPYWzUBdL0Y61qhtMV V1Om3ukASG6/1wjy+wHL+HhJKnNInkEGziOrGvE= X-Google-Smtp-Source: ACHHUZ42wVPWlSmRRTln3cVlXMe49Gw5gQJa7Xhm0bas/HbereHMVQ1ysG3pnOsw5bQAe94X1P/BvRz09eW1Mj8QYF0= X-Received: by 2002:ad4:5b8f:0:b0:61d:be1e:7c4e with SMTP id 15-20020ad45b8f000000b0061dbe1e7c4emr31937283qvp.12.1683819929450; Thu, 11 May 2023 08:45:29 -0700 (PDT) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Kyle Evans Date: Thu, 11 May 2023 10:45:18 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: OpenSSL 3.0 for 14.0-RELEASE: issues with 1.x/3.x symbol clashing, ports linking against base OpenSSL, ports that don't compile/link against OpenSSL 3, etc To: Enji Cooper Cc: Antoine Brodin , Pierre Pronchery , freebsd-arch@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-ThisMailContainsUnwantedMimeParts: N On Thu, May 11, 2023 at 9:54=E2=80=AFAM Enji Cooper = wrote: > > > > On May 11, 2023, at 00:23, Antoine Brodin wrote: > > > > =EF=BB=BFOn Thu, May 11, 2023 at 6:31=E2=80=AFAM Pierre Pronchery > > wrote: > >> > >> Hi everyone, > >> > >> It's been a long and tough fight, but I finally managed to complete a > >> `make buildworld` on amd64 with the latest state of my work on OpenSSL > >> 3; see https://github.com/freebsd/freebsd-src/pull/740 for a first dra= ft > >> of a pull-request via GitHub. > >> > >> I will probably not be able to work on this again until the DevSummit = at > >> BSDCan, so feel free to take it from there until then. > >> > >> HTH! > >> -- khorben > > > > Thanks, I have this error during buildworld: > > > > =3D=3D=3D> secure/lib/libcrypto/modules/fips (all) > > make[6]: /usr/obj/poudriere/data/src-openssl3/amd64.amd64/secure/lib/li= bcrypto/modules/fips/.depend, > > 1: ignoring stale .depend for > > /usr/obj/poudriere/data/src-openssl3/amd64.amd64/tmp/usr/lib/libcrypto.= a > > building shared library fips.so > > cc -target x86_64-unknown-freebsd14.0 > > --sysroot=3D/usr/obj/poudriere/data/src-openssl3/amd64.amd64/tmp > > -B/usr/obj/poudriere/data/src-openssl3/amd64.amd64/tmp/usr/bin > > -Wl,-zrelro -fstack-protector-strong -shared -Wl,-x > > -Wl,--fatal-warnings -Wl,--warn-shared-textrel -o fips.so.full > > -Wl,-soname,fips.so fips_entry.pico fipsprov.pico self_test.pico > > self_test_kats.pico -lcrypto > > ld: error: unable to find library -lcrypto > > cc: error: linker command failed with exit code 1 (use -v to see invoca= tion) > > *** Error code 1 > > Good find! > > The modules directory will likely need to be built in a later stage of wo= rld (after libcrypto has been installed). That, or LDFLAGS needs to be adju= sted to find libcrypto in the build tree. > I suspect it's a fairly simple one, actually: move all of the parts that actually build libcrypto into a subdir of secure/lib/libcrypto and make sure there's a proper SUBDIR_DEPENDS_modules=3D libcrypto. The module is built in secure/lib/libcrypto/Makefile, but I would guess either it's racing the build of modules/ (SUBDIR) against the build of the module in the parent Makefile, or it's just going to build the SUBDIR first every time. I don't recall the exact behavior of make here. libcrypto is in _prebuild_libs, but I don't think we have any way you can actually tell we're in the prebuild phase to avoid SUBDIR'ing in the modules/ while we're doing the earlier build. If we did, the later all pass should descend back into libcrypto/ and do nothing for the lib itself but build the modules. Thanks, Kyle Evans From nobody Fri May 12 01:23:26 2023 X-Original-To: freebsd-arch@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 4QHWHX6LlYz4BJNb for ; Fri, 12 May 2023 01:23:36 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4QHWHW1cBMz3lmT; Fri, 12 May 2023 01:23:34 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of jamie@catflap.org designates 2001:19f0:7400:8808:123::1 as permitted sender) smtp.mailfrom=jamie@catflap.org; dmarc=pass (policy=none) header.from=catflap.org X-Catflap-Envelope-From: X-Catflap-Envelope-To: bofh@FreeBSD.org Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 34C1NQb1002455; Fri, 12 May 2023 02:23:26 +0100 (BST) (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 34C1NQsB002454; Fri, 12 May 2023 02:23:26 +0100 (BST) (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202305120123.34C1NQsB002454@donotpassgo.dyslexicfish.net> Date: Fri, 12 May 2023 02:23:26 +0100 Organization: Dyslexic Fish To: yaneurabeya@gmail.com, bofh@FreeBSD.org Cc: vishwin@FreeBSD.org, portmgr@FreeBSD.org, freebsd-arch@FreeBSD.org, emaste@FreeBSD.org, cy@FreeBSD.org, brnrd@FreeBSD.org Subject: Re: OpenSSL 3.0 for 14.0-RELEASE: issues with 1.x/3.x symbol clashing, ports linking against base OpenSSL, ports that don't compile/link against OpenSSL 3, etc References: <4733AD1A-7954-4B79-9789-A57A0B46C71B@freebsd.org> In-Reply-To: <4733AD1A-7954-4B79-9789-A57A0B46C71B@freebsd.org> User-Agent: Heirloom mailx 12.4 7/29/08 List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Fri, 12 May 2023 02:23:26 +0100 (BST) X-Spamd-Result: default: False [-1.95 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.995]; NEURAL_SPAM_MEDIUM(0.75)[0.749]; DMARC_POLICY_ALLOW(-0.50)[catflap.org,none]; R_SPF_ALLOW(-0.20)[+mx:dyslexicfish.net]; MIME_GOOD(-0.10)[text/plain]; RCVD_NO_TLS_LAST(0.10)[]; R_DKIM_NA(0.00)[]; RCPT_COUNT_SEVEN(0.00)[8]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arch@FreeBSD.org]; FREEMAIL_TO(0.00)[gmail.com,FreeBSD.org]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FREEFALL_USER(0.00)[jamie]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; HAS_ORG_HEADER(0.00)[]; TO_DN_NONE(0.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US] X-Rspamd-Queue-Id: 4QHWHW1cBMz3lmT X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N Moin Rahman wrote: > I have completed my final partial exp-run with ports that has USES=ssl in any form and the result is available from here: > https://pkg.bofh.network/build.html?mastername=MAIN-default-openssl3&build=2023-05-04_16h25m58s I noticed that security/sslscan isn't on that list, presumably because its reliance on SSL is conditional: | UNSAFESSL_USES_OFF= ssl In addition, it is already marked as failing unless built specifically against openssl-unsafe. | .if empty(PORT_OPTIONS:MUNSAFESSL) && ${SSL_DEFAULT:Mopenssl} | BROKEN= Does not build with openssl | .endif For what it's worth, I updated, and fixed this port to work with openssl 3.1.0 (it needs to compile it statically to retain the full functionality without requiring "openssl-unsafe" to be installed.) The updated version removes any requirement for USES=ssl at all. PR has gone through maintainer-timeout but no-one is picking it up. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270101 Cheers, Jamie