From nobody Tue May 7 12:02:19 2024 X-Original-To: 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 4VYcP40S3xz5KhR7 for ; Tue, 07 May 2024 12:03:20 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (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 "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VYcP269Zhz4vNM; Tue, 7 May 2024 12:03:18 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=leidinger.net header.s=outgoing-alex header.b=H5+Z1G9Y; dmarc=pass (policy=quarantine) header.from=leidinger.net; spf=pass (mx1.freebsd.org: domain of Alexander@Leidinger.net designates 89.238.82.207 as permitted sender) smtp.mailfrom=Alexander@Leidinger.net 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 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1715083387; 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=7SBD7tyyeWRQqM00goE+WqgyTLrq05QFNT82VmJ2+s4=; b=H5+Z1G9YH6x/9wpQaFTXfl2eWgYhIUyzBPTZ6GFI+UEJ/aFOK69Y7z7d5uRSWqwwwj9uUg qCCTGXvUYWOA6y5vA4RVCrybHdHYZM+ZZK7hsydCpRtrtRIaEVKTedsTdg5AeLYvxk0+dS w/vtNHqt5AA/4FHdVHqPhRsp+2hMFQ8UXPNmpZWlTKISC2nM8Uebsf6jsktA7yF4OlWcA7 6np67PfHfBB7WMNheXjkw1QO/ym1t9HJ4SNExfifgO9pzHrtgFo90HcA34EJgWyZ+bl2+Z 3F92Mz5tT9iu+f+5gxkGkW7Jq+DjnEKyEufpQMShfTPepSVb/AbgZZ/dMTWSSw== Date: Tue, 07 May 2024 14:02:19 +0200 From: Alexander Leidinger To: Current , Bnovkov , alc@FreeBSD.org Subject: Graph of the FreeBSD memory fragmentation Message-ID: <0a3ddc685e54a289ff5cff569a95cd29@Leidinger.net> Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_f6683ec094448c69143bf6afa5492c95"; micalg=pgp-sha256 X-Spamd-Bar: ------ X-Spamd-Result: default: False [-6.02 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.92)[-0.920]; DMARC_POLICY_ALLOW(-0.50)[leidinger.net,quarantine]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_DKIM_ALLOW(-0.20)[leidinger.net:s=outgoing-alex]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE]; HAS_ORG_HEADER(0.00)[]; DKIM_TRACE(0.00)[leidinger.net:+]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MISSING_XM_UA(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_ATTACHMENT(0.00)[] X-Rspamd-Queue-Id: 4VYcP269Zhz4vNM This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_f6683ec094448c69143bf6afa5492c95 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Hi, I created some graphs of the memory fragmentation. https://www.leidinger.net/blog/2024/05/07/plotting-the-freebsd-memory-fragmentation/ My goal was not comparing a specific change on a given benchmark, but to "have something which visualizes memory fragmentation". As part of that, Bojans commit https://cgit.freebsd.org/src/commit/?id=7a79d066976149349ecb90240d02eed0c4268737 was just in the middle of my data collection. I have the impression that it made a positive difference in my non deterministic workload. Is there anything which prevents https://reviews.freebsd.org/D40575 to be committed? Maybe some other people want to have a look at the memory fragmentation and some of Bojans work (https://wiki.freebsd.org/SummerOfCode2023Projects/PhysicalMemoryAntiFragmentationMechanisms). Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_f6683ec094448c69143bf6afa5492c95 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmY6GFkACgkQEg2wmwP4 2IbjkQ//X8juo4BKMMYHssQK7MimF1rSp3Td/g1fbHIs7D/U1OrivpNVA5zyXZXn KhYVAVU5btbZZrMXxF30HRE3ZvZjr6s0OPpLS8H5BMpZahYaOPFJHP1xJmEsp+Lz 3jf96T63rJHE8+1JyexjPc50ErkyAvZ7L1wkokYu6LQDEhCSOkgYqXRSDFOVwXTj PyjSn6f7b96qzJpXqvfQ1kmIlIyH11D6ctgmMMaidxZ8K2tpsCg2G8S9+csD1Ouq Qz0wKyi0aJO9qupG8y0KHCLqqNgDPhY8wLp+pd/Ig1X5/Lsbbq61ZtHqtv9kaSk8 uLzm1uwKcZTG3lzsIX4WkN5MtPicEyrCkcN1+BfqlG9fVbHJk+lcS23aWBroox9E QEbmQOnH1Sh08PnBZ/RTbHOyhQrGTP14y+TrYo1talZ7TbkmfqlIQdcudKgtxnuB whtNiDWXt2yCsgEjPrEZx83z+2ZZlZLyov0WWEk6Upbb3raLTDrPFFaaxWRSdC97 DaY9DE0X2K3ci5Z3UHFohSvliH4g28wV9fqB0bdYuTL4XhpKIXEeNQZhpsuMdW4Y lchKzQ+XtKRuYF1QKgqG1nhEi8bQIhOXkKDSNrNesJxDe+rdWZll4i+tOtGVDv02 eIyEoW19vVKix5TbRXctp/fjk7jWKbrLuWQysINllMhaIY4CAX4= =ckw/ -----END PGP SIGNATURE----- --=_f6683ec094448c69143bf6afa5492c95-- From nobody Tue May 7 12:46:06 2024 X-Original-To: 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 4VYdLb12hSz5Klwg for ; Tue, 07 May 2024 12:46:15 +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 4VYdLY16bdz41fd for ; Tue, 7 May 2024 12:46:13 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=catflap.org; 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 X-Catflap-Envelope-From: X-Catflap-Envelope-To: 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 447Ck6qZ080494 for ; Tue, 7 May 2024 13:46:06 +0100 (BST) (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 447Ck6wt080493 for current@freebsd.org; Tue, 7 May 2024 13:46:06 +0100 (BST) (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202405071246.447Ck6wt080493@donotpassgo.dyslexicfish.net> Date: Tue, 07 May 2024 13:46:06 +0100 Organization: Dyslexic Fish To: current@freebsd.org Subject: termcap.db unused? User-Agent: Heirloom mailx 12.4 7/29/08 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-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Tue, 07 May 2024 13:46:06 +0100 (BST) X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.59 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_LONG(-0.98)[-0.982]; NEURAL_HAM_SHORT(-0.91)[-0.907]; DMARC_POLICY_ALLOW(-0.50)[catflap.org,none]; R_SPF_ALLOW(-0.20)[+mx:dyslexicfish.net]; RCVD_NO_TLS_LAST(0.10)[]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_ORG_HEADER(0.00)[]; FREEFALL_USER(0.00)[jamie]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[current@freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4VYdLY16bdz41fd I was looking at a ktrace dump file recently (/bin/ls) and noticed that during initialisation, it attempted to read /etc/termcap.db - as that failed, it then read the text version pointed to by /etc/termcap Adding a link: /etc/termcap.db -> /usr/share/misc/termcap.db caused subsequent runs to use the termcap.db version. Is there any reason why /etc/termcap is linked, whilst /etc/termcap.db isn't? And if so, what's the purpose of /usr/share/misc/termcap.db ? Cheers, Jamie From nobody Wed May 8 15:53:57 2024 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 4VZKT34h0rz5JPlm for ; Wed, 08 May 2024 15:54:15 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic313-19.consmr.mail.gq1.yahoo.com (sonic313-19.consmr.mail.gq1.yahoo.com [98.137.65.82]) (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) by mx1.freebsd.org (Postfix) with ESMTPS id 4VZKT248ldz4lQZ for ; Wed, 8 May 2024 15:54:14 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=cwgkanzO; dmarc=pass (policy=reject) header.from=yahoo.com; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.65.82 as permitted sender) smtp.mailfrom=marklmi@yahoo.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1715183651; bh=HDAmUv7o0c2L3HeeK5/n4PG3j2v/F3amc5PiR9p/X/I=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=cwgkanzOh9up0J++FUcYK3hagGP9RE3ExPyzVKBUUjR07kU67DkOXlUz9Y3dj+HLVfQqc+blOsa7vzo30w9HUfP78P/9hwkCPH4Lp/Ps5VZWb68uILVtDhGR3OiQWIidJgW6vu3JcMXWm2bmsgLeXd0q15gkdC+9Oowr/+2lZMKbGr1aH8w7vZHImqsw7ti30BarSqKkgBq/Y6DFFGlycwpwSsoQBAPqwx80D6Q/Cw7DUyukxpWJWfGyUgtRDpxmZZAvaqPUhl5I3n/B6w/GH/CSb2OiIrNKdBA+WbN24H2j4GlpCS5AZ8gwH81Lvu8zd/6P+13C5ABp8+iiK26IFw== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1715183651; bh=VRIBI1Pj3aJHhNt5baFD8SPMtIbt6kZT9LZUjjVvDdt=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=XpLz+ofW1xKB2suGYBYrOXsgpbO+nR38f0PbCievpguB8nFSShgqy1Q19Cf8DC6gzdgbR7jjikZ4dUcfvefRQ89X5ORLU23jIwnwxV9Q8AlwttgyzAuWsEeMbs4cTf/19PXOyp+LCCgA5+BY/xh2Vawpk4IAaw6J5IUFICBoh/7BBJzXNB1TpOog1tl2fF+KHXUs5yVGory8RmAGcz+Od54d6O/FvPko6PtkIN5s+Y3/82p3rHn3F+KneX8qel5ZBs/rVKAY19FRM5wmwx4PP6tU86f/c1uVKlY8VxollzFUycw3bZgVqDNgmAwL2yzGy6rGgRT/EQwGynry/MNtQA== X-YMail-OSG: _gywWToVM1lVD.qt1hs384zbHavweNcOp_LRYhD4zkaX9qh16ENcDVDICjEzqDv u7BC3qzrszsxExPg0pieMxan9jhEYSNBNTeozVDFYiTJIeYfTxIRPF_u9KI7Au7TR8YJEeMRTg0k Sfc7lrRy8cuWyjDcW7r.Mg1ik_i8naxcvGLWBdq7QgElpE1nrfqQcSnNx2RI9QCK31Ee0C0sbkT. Gp3tYWk0pav.1qLDJCqpge.SXtJm2waWDbfmK_VwtXAhPSwbBkcQ7TLHtv4nFUlNY4EJEtFBNXNx Pelil9bw0nQVKAQ3DOrevW30Mj4PgqJ0zbbOmKyYEu2vgYWvBAiPKTLkHOMx_YGdQ0dQ5RUmF55D jpk.DXbPKjQiuTjCM7gi9ydDCJzV8I_m4x2oMRIjP8ljiwEHkLslScbaY_S.Oeb0Y6Ua2_3UjMYG YMBzHBgQeN2y076uxrrHkq7aJQKwA2d1ofU_GeFekyqyEeMr8WiLM.NKqeNBY0Fn3c5BR66fPoQM i6Vx1tsJnQilGFMOFIT8lsUnnjtaYz1cjCi9GUfq8kuBiizt1LWJl4rrHr4ZraRpL7NxdT_kwtS6 Ymb26IKoHr32IVUSK3M4UG1MzJ.XdrhCV.Ny3oJRiblwIdm9iLhKUVCHzn9idlDGpqAuSYx7faaS Mcph8Is92QadRoSqyRjFZzeicPxS7VfR8ococ4cehFaiRaTplw82dmlNpTajQu8a3Rkq_7Zw93m_ xlP_RXZQUNN1Njbwu6E0.lrCBVx1sNoMpRciZcjR5Ttil4uim4Li45QFgduOdMsnXrodpGgF5WZi VTAGYzPjn.Yq4cxo_b1pgzGSdenrxsJgh884XsziVqye3UMop9fAQgD56TgqlpzjBQMTW8HgNmXb QjWkYTJuK.E8Rtc7DlVr2bIwqVp5lR7nb.Q6OERWZ1GcJcFAi9MYGU7UvmrMPdMKHpQVNMBi0z.L JjBId26eGJrTwvf6E.KS.duT2kkJaKjqkz7oLWgHjPKoITxf6LPUGs6fGLzGXSylbzOREfSx7y64 7bzZPyRbDMOKS5s6cATiTK0krNpQgFgY_AYRw0Hz75c9EaP_HnAAYdce1memnrDwSsEHqBRQtmc8 pxHZ7qQ78tgq6oaiZq33rPOT1WJQouHgmokDNM34A4np2T00SwCDiiJyXYVBRmRnSmX0DuXorcPZ HnqJV3FIciVfQPp7pzkHp27jJy8FsERURumoN8IyFy3WoOeExIlV07TeXOX.E6HzWeDFrWFTIO8l LqpJS03CfU.E75beMqTXpQcp1clwA1DbWgi.ORtrFoY32C6F9YGmEGI_MpAxF14KGt.FOeacpQrn CAnEKarPPHjInGMJjYWzK.30LtwhcjADTPgA8WNRXv9BERoeq8uxts9lAwadkYvw8RI4veWvWDNO TTkeSie1.EARLtyaOOv_8Lj1794EpYiJ8mmV1XpTOTefb1O7AwZzbmz7frcBSNXnkYCkcLeWMkFk UFFmxdmpn5uTrMQAVHnGEcsNoYYXLbITd2X2EFTzF5JczcX6r1CA38IJt0qswJkqCf.DjeAnXktQ cd8RsVxgGBdHWCj_m5WZFAvD0xKnNcZuZ.5ts5kaTpSo8GZaAAu1uZfHUEaCnPTUpdrp6_PPzhTa NUMP_XWlRvrHB4DFdwywD03ulrLIxxTS..jvEH0TO2lOsxFW8pm3mg.krDIqX_3ZPloA_iwN3PNe d6z6HdWMizBx7FKWhsFhukhqJXf5jh7lm7JuM7M.mEfGOL4SEpLag_xTuTtgWtAs3.vC1MQPt6vi h2WtTWyjxhCVUDqcxbRGq9Akiy9yYJNf.ox1ldLz6wrop01kRPW6xcitHL9Du0kDw.pTi8RZXlrP 4Sbm9jxngD6nte3X267EC3joDNHlEtaq0a1hEnKq6twVE8wGqlfshOjEjftRh2Tamy7Nslf8ZdmD K9zWJeufWPGhm9Io.bSpv35aOd6NxuPLyxMcXWu_LIHgVErKYAkRQMv5IG_MN1UOfxcYERb1VjIm WgAcP.F4Fs84qTLJSklMp.vjFR04jOgUAro7hAxIZxntGvsIX157eu2NF2DDluhgviD0cQeZzivk yEeb9IKQiyGub2dacB9tL_GP8.n8FFy7WYSJ.4RwRikJ3obKIGuC29s0YeBOC3mt_Y3nkvAaa7hX ewAzCxbBsI_z2TzCOD_DKO_75sTOpJ6LWSV_TXWJk8G0rFwKwPxO5y8nTtDDp3ISxZGWD.fykTNS WTrQ7zyHdieYzMUQjfb3bIeJNhDxYe2wZTVB0bIg8Wbu6zFGQfq15TxA1.FLqj8ZysZVjPM8k0Tn WsHwrtOjbZQm3Ar0Z03Ks X-Sonic-MF: X-Sonic-ID: 47db2391-9f86-47b2-9a46-d2ec3e0015d9 Received: from sonic.gate.mail.ne1.yahoo.com by sonic313.consmr.mail.gq1.yahoo.com with HTTP; Wed, 8 May 2024 15:54:11 +0000 Received: by hermes--production-gq1-59c575df44-qrd65 (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 7f7b8eeb426256031e04f3ad7fe3159f; Wed, 08 May 2024 15:54:08 +0000 (UTC) Content-Type: text/plain; charset=us-ascii 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 \(3774.500.171.1.1\)) Subject: Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, . . .] [Update to Host OSVERSION 1500018 did not help] From: Mark Millard In-Reply-To: <3CF25092-E285-43E2-9B7A-F5108E4E0A7A@yahoo.com> Date: Wed, 8 May 2024 08:53:57 -0700 Cc: void , FreeBSD Mailing List , Current FreeBSD Content-Transfer-Encoding: quoted-printable Message-Id: <8B799B49-C5BD-428B-AEFA-042E1371BF4D@yahoo.com> References: <03736C90-EE54-47B3-AEA7-ED1AC0343B4B@yahoo.com> <046DE453-9F01-4D07-9E14-EF22E537A163@yahoo.com> <5243EC66-2A75-4C06-B2F7-E9E6E6C2840A@yahoo.com> <3CF25092-E285-43E2-9B7A-F5108E4E0A7A@yahoo.com> To: Philip Paeps X-Mailer: Apple Mail (2.3774.500.171.1.1) X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.39 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.89)[-0.888]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_CC(0.00)[f-m.fm,freebsd.org]; TO_DN_ALL(0.00)[]; ARC_NA(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; DKIM_TRACE(0.00)[yahoo.com:+]; FROM_HAS_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.65.82:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.65.82:from]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[] X-Rspamd-Queue-Id: 4VZKT248ldz4lQZ On Apr 29, 2024, at 20:16, Mark Millard wrote: > On Apr 29, 2024, at 20:11, Mark Millard wrote: >=20 >> On Apr 29, 2024, at 19:54, Mark Millard wrote: >>=20 >>> On Apr 28, 2024, at 18:06, Philip Paeps wrote: >>>=20 >>>> On 2024-04-18 23:14:22 (+0800), Mark Millard wrote: >>>>> On Apr 18, 2024, at 08:02, Mark Millard wrote: >>>>>> void wrote on >>>>>> Date: Thu, 18 Apr 2024 14:08:36 UTC : >>>>>>=20 >>>>>>> Not sure where to post this.. >>>>>>>=20 >>>>>>> The last bulk build for arm64 appears to have happened around >>>>>>> mid-March on ampere2. Is it broken? >>>>>>=20 >>>>>> main-armv7 building is broken and the last completed build >>>>>> was the one started on Mon, 19 Feb 2024 12:32:10 GMT. It >>>>>> gets stuck making no progress until manually forced to stop, >>>>>> which leads to huge elapsed times for the incomplete builds: >>>>>>=20 >>>>>> [...] >>>>>>=20 >>>>>> My guess is that FreeBSD has something that broken after = bd45bbe440 >>>>>> that was broken as of f5f08e41aa and was still broken at = 75464941dc . >>>>>>=20 >>>>>=20 >>>>> One thing of possible note: >>>>>=20 >>>>> Failing . . . >>>>>=20 >>>>> Host OSVERSION: 1500006 >>>>> Jail OSVERSION: 1500014 >>>>=20 >>>> I have finished a package builder refresh this morning. All our = builder hosts (except PowerPC - I don't touch those) are now on = main-n269671-feabaf8d5389 (OSVERSION 1500018). >>>>=20 >>>> ampere1 successfully finished its 140releng-armv7-quarterly build, = so it looks like the problem with stuck builds was limited to ampere2 = building main-armv7. I'll keep a close eye on this one when it starts = its next build. >>>>=20 >>>=20 >>> I see that main-armv7 started. >>>=20 >>> It queued only 31935 instead of the prior 34528 (or more): it is = doing an >>> incremental build instead of a full build. For example, pkg was not = built >>> but instead the prior build is in use. Thus bad results from the = prior >>> build might be involved in this new build. >>>=20 >>> I'd recommend forcing a full "poudriere bulk -c -a" that does a = from-scratch >>> build for the purposes of the main-armv7 test. >>=20 >> Actually the test is not going to previde the information we are >> after as things are. >>=20 >> giflib-5.2.2 failed to build, which leads to devel/doxygen being >> skipped. devel/doxygen was the first one to hang up in the prior >> 2 failing attempts, if I remember right. >>=20 >> giflib-5.2.2 also causes graphics/graphviz to be skipped. >> graphics/graphviz was installed just before the hangup in all of >> the example hanups. So the context will not be replicated. >>=20 >> We need graphics/giflib to build to actually do the test. >=20 > Looks like: >=20 > = https://cgit.freebsd.org/ports/commit/graphics/giflib?id=3D5007109903fc271= e3ef0ba01d78781c1fed99f3f >=20 > is the fix for the graphic/giflib build failure. Well, main-armv7 is building again and things are still getting stuck. So much for my idea. For reference I list the over 10-hr-so-far ones: doxygen-1.9.6_1,2 build-depends 13:03:54 py39-pydot-2.0.0 run-depends 12:24:04 py39-pygraphviz-1.6 lib-depends 12:10:38 "ps -alxdww" would likely be appropriate to get a copy of the otuput of. "procstat -k -k" usage and the like on stuck processes would probably be appropriate. Does anyone with appropriate investigative background have login access to ampere2 to take a look at what is getting stuck? =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Wed May 8 16:45:33 2024 X-Original-To: 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 4VZLcN3q7Tz5JVK6 for ; Wed, 08 May 2024 16:45:40 +0000 (UTC) (envelope-from bojan.novkovic@kset.org) Received: from mail-ej1-f45.google.com (mail-ej1-f45.google.com [209.85.218.45]) (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 4VZLcM41wDz4tF4 for ; Wed, 8 May 2024 16:45:39 +0000 (UTC) (envelope-from bojan.novkovic@kset.org) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none); spf=pass (mx1.freebsd.org: domain of bojan.novkovic@kset.org designates 209.85.218.45 as permitted sender) smtp.mailfrom=bojan.novkovic@kset.org Received: by mail-ej1-f45.google.com with SMTP id a640c23a62f3a-a59cdf7cd78so958463666b.0 for ; Wed, 08 May 2024 09:45:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715186737; x=1715791537; h=content-transfer-encoding:in-reply-to:autocrypt:from:cc :content-language:references:to:subject:user-agent:mime-version:date :message-id:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=HZ14SRWTwctkGkBR5mrsLxdNA2KS57Eo4NnfqMbEkIs=; b=pOH9K83kEvO2cJuVYuZt4aa3uirY5Qqkx/VGW+xhZdOEE9mVc/nEccw0DVCPRRfnTw gLZzRV/cDCt3Ch6j7nE+3knExX6IyTpfojWn4J4AywQcfILotssWY1TSddpk2vMVe+Ro 5wf0+JFcgys0UEZnmsFrj/LpPGEIbaZy/whNIgoB7qpwjU/x29y3h489BRDxrNbUX07c nWQUBToGk0y+ZkBBOZJcBubg2Ky9XVIbIdM9LJP29FT/yv2LhJysf69qW32I0dsfrodp 7cCsxcblLkRUAHJIdsx5At58WrnkkkGMtzp2720pZpYu31HpIE0xxSnYj/cSxAyTj+oy AJ+Q== X-Gm-Message-State: AOJu0YwuNFmu0QBK3una+0h/6DUdRcswAn8oO3jx6zKAfJlbO1KtTfdA rjtA1aLAsbPiCsybOuqtDoWINhFa7bifjblXXomByFOIfR3uj9U5XIT42N6FtEU= X-Google-Smtp-Source: AGHT+IGhlz2jrNFE6K5aK2HdmfywCL3eua49kerO0ccBJgiohrSVeVzZH+8UG9H8d5EnIMnHRO2K0w== X-Received: by 2002:a17:906:b34b:b0:a59:c52b:9939 with SMTP id a640c23a62f3a-a59fb95a2dfmr163317066b.32.1715186736785; Wed, 08 May 2024 09:45:36 -0700 (PDT) Received: from [192.168.0.91] ([46.234.79.3]) by smtp.gmail.com with ESMTPSA id l1-20020a1709061c4100b00a599d994f88sm6268388ejg.117.2024.05.08.09.45.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 08 May 2024 09:45:36 -0700 (PDT) Message-ID: <5c7357c3-5a10-4a8e-9245-8a5787c57f35@freebsd.org> Date: Wed, 8 May 2024 18:45:33 +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: Graph of the FreeBSD memory fragmentation To: Alexander Leidinger References: <0a3ddc685e54a289ff5cff569a95cd29@Leidinger.net> Content-Language: en-US Cc: Current , alc@FreeBSD.org From: =?UTF-8?Q?Bojan_Novkovi=C4=87?= Autocrypt: addr=bnovkov@freebsd.org; keydata= xjMEZdIQsxYJKwYBBAHaRw8BAQdA/V2uVmdN7VY2Ps8wDgLlWU3b9+kPdg9bf+FHgEEX49TN JUJvamFuIE5vdmtvdmnEhyA8Ym5vdmtvdkBGcmVlQlNELm9yZz7CmQQTFgoAQRYhBLAb6L2d hfD6hKflVB43npi7IZ8rBQJl0hCzAhsDBQkFo5qABQsJCAcCAiICBhUKCQgLAgQWAgMBAh4H AheAAAoJEB43npi7IZ8rzb0A/0aY3c/XubbtQzNyA0xzyKNZlDc9zesxEMVi6rOAZNz/AQC2 QmBTBEcbyOKDfJ5m02LpudVi9thZxlrr2n0ZX9kgA844BGXSELMSCisGAQQBl1UBBQEBB0Dn 3m+8g7KTp3yC4CLICis/CIonFfNqQcJOVv6Gd73adQMBCAfCfgQYFgoAJhYhBLAb6L2dhfD6 hKflVB43npi7IZ8rBQJl0hCzAhsMBQkFo5qAAAoJEB43npi7IZ8ruPcBAJM5wq5j64RFu4sc zrryK4FeCTt/Xhfyn3UhT2hHuYkPAQDWHDN6XZ097C5wUkWUr8ywHDlMM5gWIDbr9TMUudoc Aw== In-Reply-To: <0a3ddc685e54a289ff5cff569a95cd29@Leidinger.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.99 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FORGED_SENDER(0.30)[bnovkov@freebsd.org,bojan.novkovic@kset.org]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[209.85.218.45:from]; XM_UA_NO_VERSION(0.01)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[209.85.218.45:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_NEQ_ENVFROM(0.00)[bnovkov@freebsd.org,bojan.novkovic@kset.org]; RCVD_TLS_LAST(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[current@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; RCPT_COUNT_THREE(0.00)[3] X-Rspamd-Queue-Id: 4VZLcM41wDz4tF4 Hi, On 5/7/24 14:02, Alexander Leidinger wrote: > Hi, > > I created some graphs of the memory fragmentation. > https://www.leidinger.net/blog/2024/05/07/plotting-the-freebsd-memory-fragmentation/ > > My goal was not comparing a specific change on a given benchmark, but > to "have something which visualizes memory fragmentation". As part of > that, Bojans commit > https://cgit.freebsd.org/src/commit/?id=7a79d066976149349ecb90240d02eed0c4268737 > was just in the middle of my data collection. I have the impression > that it made a positive difference in my non deterministic workload. Thank you for working on this, the plots look great! They provide a really clean visual overview of what's happening. I'm working on another type of memory visualization which might interest you, I'll share it with you once its done. One small nit - the fragmentation index does not quantify fragmentation for UMA buckets, but for page allocator freelists. > Is there anything which prevents https://reviews.freebsd.org/D40575 to > be committed? D40575 is closely tied to the compaction patch (D40772) which is currently on hold until another issue is solved (see D45046 and related revisions for more details). I didn't consider landing D40575 because of that, but I guess it could be useful on its own. Bojan From nobody Thu May 9 00:28:55 2024 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 4VZXv12zJBz5K3g3; Thu, 09 May 2024 00:29:01 +0000 (UTC) (envelope-from philip@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 4VZXv12NqVz4jxf; Thu, 9 May 2024 00:29:01 +0000 (UTC) (envelope-from philip@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1715214541; 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=neNkO5Vu1HvdOYZChBpeUuTnngjIRjARQ5gAF43WPCE=; b=hHYdlENQn7pk3FuSAKV02P1SMyd/hRAzy+zEQ7eEXzR7wGExxAZLZEzd/5Bhm7ewrDe/MD zhqR3Ouofya9Zr3RD7R2bcma7zLqTFVXlTh+V0o/Ts+AC/d4bstkGlijcA8BD1mCaQAmfz edU14PHNJROt/g8/+HOUeLNdQVLV+xlDoOUWiUDDMxtHAzQ2erXcBGNuWDybpW2LUqkGnx ZcqEexxZVVeA8zrBzVmVNM8c829VPzeJyh2fR8OIT+hhYxqX2lnjTwxGoRUMSghDvEobQu ziWNUtnUM7cnn2ZueQBa9jElC2qktvaigRdIE6UH4mVePGuJzsCTG0KAjoXUug== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1715214541; a=rsa-sha256; cv=none; b=IbMx6L3sierAV9yDABBO7ACRp1ERFyvOs1gCLEPE51IM/tMtoVwEJ6Z6IzE324/rAgAETA eOf1PQTGws8vQRwv8FTRB7ZDBRCdxFM3HptctipdPob7B/UiWzJfN/udRL4Io9kvCWHfB/ 1hLydrN9++lI3Zi5zoYY66sV8h5FXbo6K9uhXGtCUY34gb0+kUYpYK4qAszIQ7wlZyGLE1 bl6wYFDkq/E2wAntnWs3KM/K0MEw33/7XtXtAmCeSAxESxqy9dnQGm6X0iJshc3chk3Irz 8G0t9GVdXItwJC+RoCo1IMs+LwFCSJ9EarsaSTBjEb+nEVl7pvMp7yS861PhUg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1715214541; 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=neNkO5Vu1HvdOYZChBpeUuTnngjIRjARQ5gAF43WPCE=; b=MJpH8TwxAupUqU6IKm7LCLc63RHorEcXSklwuuLu6rQh4dr1oo9TpedSKUXu9oNY5281CZ BC9QQP882e2ZQj2K32QCkMcVaW7KEiNSjxJgAGG6vAG2L4lb0cSwQiwKD+x5cDRhLg9ZFe qOPTyjGvq7ZS8pSZxXkiRZG29lg5i9QvDLDni4vlJzTWL7SL4nShUOsUyPSyVfjAnTWtB5 2345Bd9r4lebnBlpNO0kEu52reE4M1sNL9eZU9WGwPQspGexVS2orsLWSdeXQsfis5oFXv 84QRaTp6Yn4LLqLJahn9HH9fiBi5qmb4sCCnO5q3mw2a08DaWaBd5aSO37ByAQ== Received: from fauth1-smtp.messagingengine.com (fauth1-smtp.messagingengine.com [103.168.172.200]) (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: philip/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4VZXv111JMz1SVN; Thu, 9 May 2024 00:29:01 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailfauth.nyi.internal (Postfix) with ESMTP id 429171200066; Wed, 8 May 2024 20:29:00 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 08 May 2024 20:29:00 -0400 X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdefuddgfeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffokfgjfhggtgfgsehtqhhmtdertddtnecuhfhrohhmpefrhhhi lhhiphcurfgrvghpshcuoehphhhilhhiphesfhhrvggvsghsugdrohhrgheqnecuggftrf grthhtvghrnhepgefhveefgeehtefhieevtedulefftdejheefgffgfffhgfelvdeihfdu iedutdelnecuffhomhgrihhnpehskhhiphhpvggurdhgrhgrphhhihgtshdpfhhrvggvsg hsugdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhr ohhmpehphhhilhhiphdomhgvshhmthhprghuthhhphgvrhhsohhnrghlihhthidqudduie eivdeivdegkedqvdefhedukedttdekqdhphhhilhhipheppehfrhgvvggsshgurdhorhhg sehtrhhouhgslhgvrdhish X-ME-Proxy: Feedback-ID: ia691475d:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 8 May 2024 20:28:58 -0400 (EDT) From: Philip Paeps To: Mark Millard Cc: void , FreeBSD Mailing List , Current FreeBSD Subject: Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, . . .] [Update to Host OSVERSION 1500018 did not help] Date: Thu, 09 May 2024 08:28:55 +0800 X-Mailer: MailMate (1.14r6030) Message-ID: <11DB2E73-A765-47CD-9C5A-B4F8C6978704@freebsd.org> In-Reply-To: <8B799B49-C5BD-428B-AEFA-042E1371BF4D@yahoo.com> References: <03736C90-EE54-47B3-AEA7-ED1AC0343B4B@yahoo.com> <046DE453-9F01-4D07-9E14-EF22E537A163@yahoo.com> <5243EC66-2A75-4C06-B2F7-E9E6E6C2840A@yahoo.com> <3CF25092-E285-43E2-9B7A-F5108E4E0A7A@yahoo.com> <8B799B49-C5BD-428B-AEFA-042E1371BF4D@yahoo.com> 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; format=flowed Content-Transfer-Encoding: quoted-printable On 2024-05-08 23:53:57 (+0800), Mark Millard wrote: > On Apr 29, 2024, at 20:16, Mark Millard wrote: > >> On Apr 29, 2024, at 20:11, Mark Millard wrote: >> >>> On Apr 29, 2024, at 19:54, Mark Millard wrote: >>> >>>> On Apr 28, 2024, at 18:06, Philip Paeps wrote: >>>> >>>>> On 2024-04-18 23:14:22 (+0800), Mark Millard wrote: >>>>>> On Apr 18, 2024, at 08:02, Mark Millard = >>>>>> wrote: >>>>>>> void wrote on >>>>>>> Date: Thu, 18 Apr 2024 14:08:36 UTC : >>>>>>> >>>>>>>> Not sure where to post this.. >>>>>>>> >>>>>>>> The last bulk build for arm64 appears to have happened around >>>>>>>> mid-March on ampere2. Is it broken? >>>>>>> >>>>>>> main-armv7 building is broken and the last completed build >>>>>>> was the one started on Mon, 19 Feb 2024 12:32:10 GMT. It >>>>>>> gets stuck making no progress until manually forced to stop, >>>>>>> which leads to huge elapsed times for the incomplete builds: >>>>>>> >>>>>>> [...] >>>>>>> >>>>>>> My guess is that FreeBSD has something that broken after = >>>>>>> bd45bbe440 >>>>>>> that was broken as of f5f08e41aa and was still broken at = >>>>>>> 75464941dc . >>>>>>> >>>>>> >>>>>> One thing of possible note: >>>>>> >>>>>> Failing . . . >>>>>> >>>>>> Host OSVERSION: 1500006 >>>>>> Jail OSVERSION: 1500014 >>>>> >>>>> I have finished a package builder refresh this morning. All our = >>>>> builder hosts (except PowerPC - I don't touch those) are now on = >>>>> main-n269671-feabaf8d5389 (OSVERSION 1500018). >>>>> >>>>> ampere1 successfully finished its 140releng-armv7-quarterly build, = >>>>> so it looks like the problem with stuck builds was limited to = >>>>> ampere2 building main-armv7. I'll keep a close eye on this one = >>>>> when it starts its next build. >>>>> >>>> >>>> I see that main-armv7 started. >>>> >>>> It queued only 31935 instead of the prior 34528 (or more): it is = >>>> doing an >>>> incremental build instead of a full build. For example, pkg was not = >>>> built >>>> but instead the prior build is in use. Thus bad results from the = >>>> prior >>>> build might be involved in this new build. >>>> >>>> I'd recommend forcing a full "poudriere bulk -c -a" that does a = >>>> from-scratch >>>> build for the purposes of the main-armv7 test. >>> >>> Actually the test is not going to previde the information we are >>> after as things are. >>> >>> giflib-5.2.2 failed to build, which leads to devel/doxygen being >>> skipped. devel/doxygen was the first one to hang up in the prior >>> 2 failing attempts, if I remember right. >>> >>> giflib-5.2.2 also causes graphics/graphviz to be skipped. >>> graphics/graphviz was installed just before the hangup in all of >>> the example hanups. So the context will not be replicated. >>> >>> We need graphics/giflib to build to actually do the test. >> >> Looks like: >> >> https://cgit.freebsd.org/ports/commit/graphics/giflib?id=3D5007109903f= c271e3ef0ba01d78781c1fed99f3f >> >> is the fix for the graphic/giflib build failure. > > Well, main-armv7 is building again and things are still > getting stuck. So much for my idea. For reference I > list the over 10-hr-so-far ones: > > doxygen-1.9.6_1,2 build-depends 13:03:54 > py39-pydot-2.0.0 run-depends 12:24:04 > py39-pygraphviz-1.6 lib-depends 12:10:38 > > "ps -alxdww" would likely be appropriate to get a copy > of the otuput of. > > "procstat -k -k" usage and the like on stuck processes > would probably be appropriate. > > Does anyone with appropriate investigative background > have login access to ampere2 to take a look at what > is getting stuck? This is unfortunate. I'm sure I have the appropriate background, but = I'm spread very thin! I'll get as much information as I can about this = machine while it's stuck, before I bounce it again. I think it may be worth a try building those ports in isolation on = ref14-aarch64, and see what they're trying to do. I'll also set up a = set of refX-armv7 jails on that machine. Hopefully we can get to the bottom of this soon. This is a very tedious = failure mode. We could also try to put an older armv7 image on the builder jail on = ampere2. Depending on whether we have a sufficiently old image, that = will either be very straightforward, or a very deep rabbit hole. Thanks again for keeping an eye on this. We really should have better = monitoring for stuck builds than "Mark will tell us". :-) Philip From nobody Thu May 9 01:58:56 2024 X-Original-To: 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 4VZZv32yyWz5KDf6 for ; Thu, 09 May 2024 01:59:11 +0000 (UTC) (envelope-from mike.jakubik@gmail.com) Received: from mail-yb1-xb2e.google.com (mail-yb1-xb2e.google.com [IPv6:2607:f8b0:4864:20::b2e]) (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 4VZZv14pSTz4vwQ for ; Thu, 9 May 2024 01:59:09 +0000 (UTC) (envelope-from mike.jakubik@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=WW5ghmPE; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of mike.jakubik@gmail.com designates 2607:f8b0:4864:20::b2e as permitted sender) smtp.mailfrom=mike.jakubik@gmail.com Received: by mail-yb1-xb2e.google.com with SMTP id 3f1490d57ef6-de60d05adafso410134276.2 for ; Wed, 08 May 2024 18:59:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715219948; x=1715824748; darn=freebsd.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=+oqX0PQyjWUfEBwsGxLcUVL7O6RwdrAG5Fhly3fde5U=; b=WW5ghmPEtgoaTTqVGHlSPyuYKLcZhXgk45nR42m+rdbQufH2Qhwy0ncmrcvXRTRHDJ AZJSjHp1kXLZRYAdORftBi3ONdETZl67P/tXAFsfwhHZas6og4TR4ABsb6dAmAsj9Kdb gNiXNyVbEAI/kpriv+lW2kLboqiwmy6k6zmH3ecH/GgRFCbZvrao1QzdEQu+wqVNkmFx IB7yVqAFHrZbgIfam7LOFMrRIL8qg6F0q/DCj2fs1ty8Oh3gh/zoKEPcbuJKFs/uhY+9 KiFcPW3SWLjOcOMjKcqdcwSxQ5JTUJ9JVo40Xybi68NDO8CM7SQz8iO+iXmHGdPuxwR3 3Z5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715219948; x=1715824748; 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=+oqX0PQyjWUfEBwsGxLcUVL7O6RwdrAG5Fhly3fde5U=; b=nk80frhElxCiEa7gwtbYHTS9rZIH5GW05s+nUrjBQBHJZw3rXEYucnyuEbwM2WpAiG cz/DnENYmCy/9J1GV69YksvpvyL70DDBAbfr51LRl06pXe4Mm2syMf44j8r1Ura1rRfl H7oobEgxOLAIrAZ4zbbMQzknQ5VlV/y5GLAE+G5OR2qJbf0rF8fQgP9QDV55RLOlEQ6f KDMRtzKqvgljqzsWgKlewyVPmLsUq980myHe0+ljCFOnUoZB+Sbw5BN/M3YKn1A61g9C rwDnxb4IQ0d4ba/t+deI9bejLz7qJb1fD/KBgxsMUn3DU3kQjQ0I62zpG8NqoG7hFUKF sugg== X-Forwarded-Encrypted: i=1; AJvYcCU9dBn7TTIYpWTk/3JqHvzFEyyl1IqvwkmQAlZdsvpoO/YB3fh8tTOes939Wxc279DZghktHnxRVO7ty9Xh53eUlrgd X-Gm-Message-State: AOJu0YwWAKgyb0RLjk0dZw4CjNur68wt2CtE8sBcZMXR/pJAhulZOboU BbMcFXKZszahuKFmDCdasQdlHQJAnSWgNwawZyff3bLXHUVc298hfgYfmMikc3owDrxDkZgRsNi qopWRau2fEr2egU6vyu1DqHgD74FqNJdZ9pw= X-Google-Smtp-Source: AGHT+IEY8zy/NnceVRBGqiSOILQvJnDJ4iTOEdj4R8exNp+mhQpoJbQxuB6ATAlhyu106Wy0W/zPxM0SiD0w5nvxO64= X-Received: by 2002:a05:6902:4f4:b0:de6:b58:fe72 with SMTP id 3f1490d57ef6-debb9dc3424mr4744913276.58.1715219948542; Wed, 08 May 2024 18:59:08 -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: <0a3ddc685e54a289ff5cff569a95cd29@Leidinger.net> In-Reply-To: <0a3ddc685e54a289ff5cff569a95cd29@Leidinger.net> From: Mike Jakubik Date: Wed, 8 May 2024 21:58:56 -0400 Message-ID: Subject: Re: Graph of the FreeBSD memory fragmentation To: Alexander Leidinger , current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000bea43b0617fbc33e" X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.977]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; 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)[]; RCPT_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TAGGED_FROM(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; MISSING_XM_UA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MLMMJ_DEST(0.00)[current@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::b2e:from] X-Rspamd-Queue-Id: 4VZZv14pSTz4vwQ --000000000000bea43b0617fbc33e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Alex, No, i can't comment on the C code or it's change impact otherwise. But the graphs are impressive, i say lets try it. I can test i 14-stable. Ty. On Tue, May 7, 2024 at 8:03=E2=80=AFAM Alexander Leidinger wrote: > Hi, > > I created some graphs of the memory fragmentation. > > > https://www.leidinger.net/blog/2024/05/07/plotting-the-freebsd-memory-fra= gmentation/ > > My goal was not comparing a specific change on a given benchmark, but to > "have something which visualizes memory fragmentation". As part of that, > Bojans commit > > https://cgit.freebsd.org/src/commit/?id=3D7a79d066976149349ecb90240d02eed= 0c4268737 > was just in the middle of my data collection. I have the impression that > it made a positive difference in my non deterministic workload. > > Is there anything which prevents https://reviews.freebsd.org/D40575 to > be committed? > > Maybe some other people want to have a look at the memory fragmentation > and some of Bojans work > ( > https://wiki.freebsd.org/SummerOfCode2023Projects/PhysicalMemoryAntiFragm= entationMechanisms > ). > > Bye, > Alexander. > > -- > http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF > http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF > --000000000000bea43b0617fbc33e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Alex,

No, i can't=C2=A0comment o= n the C code or it's change impact otherwise. But the graphs are impres= sive, i say lets try it. I can test i 14-stable.

T= y.

On Tue, May 7, 2024 at 8:03=E2=80=AFAM Alexander Leidinger <Alexander@leidinger.net> wrot= e:
Hi,

I created some graphs of the memory fragmentation.

https://www.leid= inger.net/blog/2024/05/07/plotting-the-freebsd-memory-fragmentation/
My goal was not comparing a specific change on a given benchmark, but to "have something which visualizes memory fragmentation". As part o= f that,
Bojans commit
https://cgit.freeb= sd.org/src/commit/?id=3D7a79d066976149349ecb90240d02eed0c4268737
was just in the middle of my data collection. I have the impression that it made a positive difference in my non deterministic workload.

Is there anything which prevents https://reviews.freebsd.org/D4057= 5 to
be committed?

Maybe some other people want to have a look at the memory fragmentation and some of Bojans work
(https://= wiki.freebsd.org/SummerOfCode2023Projects/PhysicalMemoryAntiFragmentationMe= chanisms).

Bye,
Alexander.

--
h= ttp://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF=
htt= p://www.FreeBSD.org=C2=A0 =C2=A0 netchild@FreeBSD.org=C2=A0 : PGP 0x8F3= 1830F9F2772BF
--000000000000bea43b0617fbc33e-- From nobody Thu May 9 09:34:51 2024 X-Original-To: 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 4VZn204yHwz5JF16 for ; Thu, 09 May 2024 09:35:52 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (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 "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VZn2017ntz4hpL; Thu, 9 May 2024 09:35:52 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; none 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 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1715247339; 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=hV+Y6qfham2XKHEDdNQBo5TyH41M4JkWEhygxGmDbNw=; b=RzJaM9RzrpiN/iIrgcuh18F4vC6sAh9pwpw0qAKgXw9b/yQM23+AqIFG+DKmRrzcKGnDGp SniYBBVGWqSYb/LeAE4tfTgiMwgUJ7SZR8MRQo28Nd7vNHI2gHv52Dv81w7M79duKyiiQW NtISUlv9YoTth/+QhIctZrISiLkoSDQ+ghrIBV+BohpdaCk5PwGqYfIo2l98xf/gPDg/hT 0Ligm5nAz5Dwggif0w00gHyPvRUFnmPLEWxSmITRob2FmXsF1AzOycuCDtT21IxW8QPlw4 dNmgy+gRgUOFKdi16e/aEk0hqrU9s0OAhafUguX2xNkoPu0jvE8CevdQk8O2xQ== Date: Thu, 09 May 2024 11:34:51 +0200 From: Alexander Leidinger To: =?UTF-8?Q?Bojan_Novkovi=C4=87?= Cc: Current , alc@freebsd.org Subject: Re: Graph of the FreeBSD memory fragmentation In-Reply-To: <5c7357c3-5a10-4a8e-9245-8a5787c57f35@freebsd.org> References: <0a3ddc685e54a289ff5cff569a95cd29@Leidinger.net> <5c7357c3-5a10-4a8e-9245-8a5787c57f35@freebsd.org> Message-ID: Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_4c82248a7cf604e4aac14a20a26be955"; micalg=pgp-sha256 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:34240, ipnet:89.238.64.0/18, country:DE] X-Rspamd-Queue-Id: 4VZn2017ntz4hpL This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_4c82248a7cf604e4aac14a20a26be955 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8; format=flowed Am 2024-05-08 18:45, schrieb Bojan Novković: > Hi, > > On 5/7/24 14:02, Alexander Leidinger wrote: > >> Hi, >> >> I created some graphs of the memory fragmentation. >> https://www.leidinger.net/blog/2024/05/07/plotting-the-freebsd-memory-fragmentation/ >> >> My goal was not comparing a specific change on a given benchmark, but >> to "have something which visualizes memory fragmentation". As part of >> that, Bojans commit >> https://cgit.freebsd.org/src/commit/?id=7a79d066976149349ecb90240d02eed0c4268737 >> was just in the middle of my data collection. I have the impression >> that it made a positive difference in my non deterministic workload. > Thank you for working on this, the plots look great! > They provide a really clean visual overview of what's happening. > I'm working on another type of memory visualization which might > interest you, I'll share it with you once its done. > One small nit - the fragmentation index does not quantify fragmentation > for UMA buckets, but for page allocator freelists. Do I get it more correctly now: UMA buckets are type/structure specific allocation lists, and the page allocator freelists are size-specific allocation lists (which are used by UMA when no free item is available in a bucket)? >> Is there anything which prevents https://reviews.freebsd.org/D40575 to >> be committed? > D40575 is closely tied to the compaction patch (D40772) which is > currently on hold until another issue is solved (see D45046 and related > revisions for more details). Any idea about https://reviews.freebsd.org/D16620 ? Is D45046 supposed to replace this, or is it about something else? I wanted to try D16620, but it doesn't apply and my naive/mechanical way of applying it panics. > I didn't consider landing D40575 because of that, but I guess it could > be useful on its own. It at least gives a way to quantify with numbers resp. qualitatively visualize. And as such it may help in visualizing differences like with your guard-pages commit. I wonder if the segregation of nofree allocations may result in a similar improvement for long-running systems. Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_4c82248a7cf604e4aac14a20a26be955 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmY8mMoACgkQEg2wmwP4 2IZtTA//UAU+BhHhYcx9r0vnVGkhN4boRwCM6svxIecerIK25QbNcV+eRWCgYplQ 4XV/06plqhfSblHtPrxbITHbX/qgHYIYX/3RXB0/awDLlVjZNkhPNIf3MPilGjun X5ruvSaBCeNVd3yvW5oJNy69jLvjLY8AzDhGXC6rmid9vY+FAMLWakuzP5FbI2dD Vx0I6z5dzPaRRMie3kImvd6V/eduuvL136nEwv281LjtMoXWchoWSINE1HDFm/MJ TB9dL//P7cF3cFaHr3WCPsYSwfctKhjxTSVrpo1k2nFXG9fMjOBl03114yERhbhi NTYRqjiWNNnFZIAOjR1TD+mRDApR50rMA9jPahkVeBwKkl5tt+ioi5LRc/S+GvUs WMeWIgMdfTmXskzN7qNkPPNh0xUiWREXRtTEyPw7FvkUz0DKZfJjBNdTMUD8r4c9 sd6Ha3+iAPS4vAzSk1OBriFXVDlwA/C3zlZd5uIu6w0stbt5951R4w9JZu3hzvhj 6UW0Wn2bBj2d5ER1No5mhOhzw7Rck+c3gHBcGwQZpEL037+QNQUHEvMLEd0sXcpP +t7Oh9MgCCN5OmZjTqT1nb2zzp6xU7xaaWgNICVNfJsXMivGW+7Bnz0AeUG7RAB2 FmoNUCLUL1eOR3O0rvcIneTAJsn1VUoAVVpT23XpQrqGrdEY5SM= =s7/D -----END PGP SIGNATURE----- --=_4c82248a7cf604e4aac14a20a26be955--