From nobody Wed Jan 21 23:36:22 2026 X-Original-To: freebsd-hackers@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 4dxLDz06nGz6Ptns for ; Wed, 21 Jan 2026 23:36:35 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (udns.ultimatedns.net [24.113.41.81]) (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 "ultimatedns.net", Issuer "R12" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4dxLDy3w4qz3mhf; Wed, 21 Jan 2026 23:36:34 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Authentication-Results: mx1.freebsd.org; none Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 60LNaMFM019687; Wed, 21 Jan 2026 15:36:28 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bsdforge.com; s=bsdforge; t=1769038588; x=1769039188; r=y; bh=8SDP6QdGktTZlAM8h/eDemH3gGqdkDfBbnsr/qCtiRY=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=Q+H4z0JKjs6KKSubSqea4B7FfJ/ZanMQze6NoGLI5KAtbC/f/5ZsnvsS+W/ZVXSS4 MpG4StHpsy4gGg9BKSzHJOR1rrK57RzKAcLa3jvmZc0S/tevKyaFbOUlHdQ+M4udT2 tNH+MLEcEC+c8ytHjtmmwpfukTLGUgQbmoE7RrXRBUgSb04sFFypkVPNw/x8qPmsxM C8/0cNi/WfO0DNK9x7ytetknVeIUWd+srCxhhYuZZNVRXUMOE0JTrWm9XUGuFfvqi1 XjtJYu9FMNTypT9qQCVhlB/JM1i7Ikslcm6V8VdQ3IgmovNs32kdmr7HFyr/zg6+Q8 fH/hn3ThkQQkg== List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@FreeBSD.org MIME-Version: 1.0 Date: Wed, 21 Jan 2026 15:36:22 -0800 From: Chris To: Olivier Certner Cc: freebsd-hackers@freebsd.org Subject: Re: Current ULE state and plans (was Re: HMP scheduling on FreeBSD) In-Reply-To: <3453224.qJGKkgxtO6@ravel> References: <0Ng09S3rEB0BvT9vzHqVKU7rWxoad96kjEc7U2LCwDFJKmmswXujip7qbRlo_BIhNKcI7d-2CUHdp9Dxr3-7hhafpD6uagJSFUCjtC9qRr4=@proton.me> <7e707d4d-fc1b-46d1-be9c-89bed98f9269@comcast.net> <9a0e73cc0ed6536ab809e71126454d81@bsdforge.com> <3453224.qJGKkgxtO6@ravel> User-Agent: UDNSMS/17.0 Message-ID: X-Sender: bsd-lists@bsdforge.com Content-Type: multipart/mixed; boundary="=_d5d2256c0c28877f294f503da42c58e9" X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4dxLDy3w4qz3mhf --=_d5d2256c0c28877f294f503da42c58e9 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed On 2026-01-21 05:34, Olivier Certner wrote: > Hi, > >> FWIW we use 4BSD exclusively on some 1,200 servers. As it has proven to >> return the best results for our own use case, >> as well as our clients use cases. > > Results measured how? When was the last time a comparison was made? > >> Not looking for an argument here. > > Hmm... Hoowee. That's some passive aggressive stuff, right there. ;) > >> But we'd feel ill served should you decide to pull it. While I can't speak >> for our clients, I'd venture a they'd feel the same. > > Some people in this thread are apparently getting emotional with this topic > of > potentially retiring 4BSD to the point where they cannot even grasp simple > propositions. You may have your reasons, I certainly don't dispute that. > But at > least I would like my real message to be understood for what it is and that > you > stop talking past me. I'm not attempting to "talk past you". Nor do I have an emotional viewpoint on this matter. My perspective is purely pragmatic. > > So I'll try again with another formulation, even if it is redundant as it is > logically implied by what I've already said. Please read it carefully: > I do not intend to retire 4BSD if (we know for sure that) there are > workloads > where it performs significantly better than ULE. > > Does that reassure you? No... You have gone to great lengths to indicate that you have put alot of time and effort into spearheading the task of improving ULE scheduling and that your findings will dictate it's outcome. Even to the demise of 4BSD: > Once these problems are fixed, it's likely that, experiments confirming, > there won't be any more reason to keep 4BSD around. One of my personal > goals is to deprecate 4BSD in 16 if possible, as it is more and more > irrelevant on modern machines and seems too lightly tested. You clearly have an axe to grind. IMHO I find it astounding that you're so dismissive toward 4BSDs relevance. You're quick to dismiss anyone's suggestion to the contrary. With the possible exception of Steve. You have zero knowledge of anyone else's use case for choosing 4BSD over ULE. This is not taking an objective view on scheduling. Nor does it make a good case for your "improvements" on ULE. Make no mistake; I'm *thrilled* that *anyone* is willing to take another look at scheduling and even more so, to actually make the time to do it. But scheduling is the epitome of objectivity and nothing in this thread suggests objectivity. I'd like to suggest that we take a whole other look at this and how we might *all* make contributions to improve FreeBSDs scheduler or schedulers. These contributions might only be to present actual use cases, and or the results of those use cases. A predisposition to nuke 4BSD does not suggest a well conceived plan for improving the scheduling/schedulers on FreeBSD. We may well discover that one-true-scheduler is not practical and that having several is a more realistic choice. FWIW My corporation is NET centric. I'm the president and CTO. As such, I'm largely responsible for what gets done. I write a lot of the code. Our systems are largely autonomous. Meaning, nobody's launching DE's or opening a browser, media player,... They perform their assigned tasks. Reacting if/as they're intended. IOW these systems require almost no human "inter-action". As a result, they don't produce loads "typical" to most experienced by "FreeBSD users". It is for this reason (I assume) that we discovered that 4BSD achieved better results in "flattening" the graph than ULE. This is the reason I chose to defend 4BSD. I have no emotional attachment to it. My concerns are pragmatic. I'm responsible for the bottom-line at the corporation and for us, 4BSD makes us more money than ULE. It's as simple as that. Let's "reboot" this thread. What do you say? :) > >> As our time to delivery will increase should we be required to create >> additional local patches to circumvent 4BSD removal. >> Which would be a long term commitment. > > I hope you understand this as an argument for actually testing ULE and > especially > responding to future test calls in the area, as doing so will likely cost > you much > less than keeping 4BSD around by yourself. > > Thanks and regards. --Chris --=_d5d2256c0c28877f294f503da42c58e9 Content-Transfer-Encoding: 7bit Content-Type: application/pgp-keys; name=0xE512722F.asc Content-Disposition: attachment; filename=0xE512722F.asc; size=3074 -----BEGIN PGP PUBLIC KEY BLOCK----- mQENBGf/G0IBCADARuJc6IcwOe3jv7dQsP1X/EIHvCFExPbTmlMNFMXbMMccQUnV o8ayEn+wmTvPhw7uL3PDk7DQs16W1sN2b8UMFc804cVWNGtoG3rA+Np+TFEYlXJx eh5Q42VHptkuwzHKl+q2utkpRlS7uHyfjsInQAoHxLyi/wrsaZTHHhDbLLhJ5Ez0 arohQ2Q1w0M5e9rW8Fy5rpC7RpC6uO1SZMxcbdqURI/BBqxbiD1iW62cDWFkfFX+ dtaEXghFV7BIBMDSrgIunGoEfdMZgXys7O6bPWn8z0cuOZIPj4HrjoCYARyQ+sdc rjz/k06SLM/UvEZDorJhT4DbYrwMNvaPWJiPABEBAAG0HkNocmlzIDxic2QtbGlz dHNAYnNkZm9yZ2UuY29tPokBNQQQAQgAHwUCZ/8bQgYLCQcIAwIEFQgKAgMWAgEC GQECGwMCHgEACgkQVKBqaOUSci8bSwf/fK3QcTYXRMrv82HIp4SiGCSD7/bRmyWr ipv2vzknGFHxPBN4AEWIqF/U4j5oDXaodyU6xsy59Z47/lgbyzyZiVR6nmJVgZVf el/EgwnLt7ZuYGLLEhIN2pd9itJkB8PMPZrUHMWgIw8BxX5YFYGuyiNe9pGn0Coj 98t/v3fouhqksH+BpB4TBHJBBDSxSiMm66VTJX4Xcnpf0ZnQVP4GBuoyodnFBfdI wqftPLESsCC08lUhD2j7v2NRWwMi/q3ed8D6VCKPImBByYnBZL5gu56K5bwqaQfN itu06APuIYnG71qxgn1EPO63lovWP5NZGgOKvzs3K+JfPF79BiOUFbQjQ2hyaXMg PG1haWxvcEBocmNvbW11bmljYXRpb25zLm5ldD6JATEEEAEIABwFAmf/G0IGCwkH CAMCBBUICgIDFgIBAhsDAh4BAAoJEFSgamjlEnIvBH8H9RGwzZuU6+zvH1WjQa97 yWpEt9rC+BIBJThev2Cpls2LqBqIeIQVZPnyLAZWgFaiezL6+xbvcNt6OnfidIYa x8iRwCMC6/Bs8H2Wef9qfGxXi+jHPLYQk3juiZVmBhIK6FJZkzaW4wSiawofwzbp zqNxO8dZ0j4foaJZrNi8iqsvKjiiHoSFaJtumIThAeydI18CNLeFaS53sk5nad6I wCYeFKmJ/22dMP7DOFEgyG1iNYgY+AGREMkEsBiLpqYjJ5asK+1UdUy/TRly1hOt HHxCiX0Fh9ZYM2vLIj7sq4LKaMPGeYC3qTqBYugVeyz7LkiI2ft/BKveA5JxuYKk ZrQiQ2hyaXMgPG5hbm9nQGhyY29tbXVuaWNhdGlvbnMubmV0PokBMgQQAQgAHAUC Z/8bQgYLCQcIAwIEFQgKAgMWAgECGwMCHgEACgkQVKBqaOUSci+4Bwf8D0Ogk2/X ud/CsAgHozwzKPqfesL5SRWM14hLnU9/EHoplnZgNexbVY1wXIi2FYPo5cve9QxW Nmt3S3UTF9j2fGqv0wmeHv3EqogFUHnftLyWpbeTPOFDMIQp/BOD6ygfeXxXWxRT L6zvUkSrDtHvkQHPWGRxwP+ihWjpw9AQR/R4/qAuTAZZM0O7UnJEo4mWXatl+utF wegG2giwFTTxfF+1rMpFtUDjYCpRQ6ZmE+gC1mHUMoH7GJMQv12DbqwKrxtwGfd0 AJNO3ZDnxl24BmIfl1YqQGZQ5iIH7At4YItESbU45hoNNsG9oDrsil78EUCAtXHd UPScj+eXaeAkgrQfQ2hyaXMgPHBvcnRtYXN0ZXJAYnNkZm9yZ2UuY29tPokBMgQQ AQgAHAUCZ/8bQgYLCQcIAwIEFQgKAgMWAgECGwMCHgEACgkQVKBqaOUSci9o7Af+ Lwu5hJlI5HZNGwAll7QTIFZVW+y4OEg+amhxTDGbAAqlnSIkHC1KgkmIOOrThme3 kTFCqfIIsuP73yKxHq6kRG0zH5/7asAPNAUOfzD7B2o/gMyuTRKyG5r9f3UmACr4 6qvtFhIwROXr6+NNT2IKg3l0/8F58A0N/TR8D2PTHeo4x6jYcZQDCrCy7BAdk3cu V16k4z/1UzRa07b5McezbWL20cIaZ+dqNcCjKZpzPlTyTCGgrNNtaDpNVhoWUKMB YNcKql+tfC1IpX8l+IU6OBKcDKMkQojvO1QrZqY8MDJGo8jq/CtotQ8+IpAai3Bx dQEsxrxlcKTR4rUqvd8VGbkBDQRn/xtCAQgAv5Nv/aQN72xsLik+K73PJwpUmyhu vnI6stM6dSecylXVHjZ7C4n/m0eQEeQCl+9lByHR9N8H+WS3DtAd4pmciiIxRQLA JZiuaLYcy9ziy1h7130VoR7hhJHzo9FIhWkTGlCDX3egUZrYhMiwFUO8lNltLB8o TBvIrMSsnUzawtQjq/otv0Jf+oBPbG+gIYnAm7w6r86n/l+eVxf5eEoS7wV0DJfp b2jE5zWErWk8I/tq4e8T+1VQeVQR6wz+NrUCSxkPkpNAm19AFUHOk//yvMGWVlDW F6gr3ErN2a0w/kZ0lz3Msxsb87QT+MnJf/T3cuEqdTIoSk74BfNEAdMohQARAQAB iQEfBBgBCAAJBQJn/xtCAhsMAAoJEFSgamjlEnIvyvIH/26zytSVNDaxtprg7XtX LerIWf9RyVx8omCw/lXKRCcgkfwD7QR+nSZ0thWOGMpcnivjuReeVRkz/webUF47 BXJ/Tge07nrxdtyTIHBbp35fPIriaKaII6YWc2Ufdxwv+cD8PADS6gQWAlgrWLmn VmYtyHs4kwtiPZyUyuBdWnZal2GyYY0WVwYjvbk95eInwOaIdoTjesJ7ZhUFu155 r4hh9GlvM0uv8WJ5Mw9wvHa5fIM205I5g0IWC7yvTwwwKHlV4JQQOqMwfv569OEl 1GKqA12nSVziB1+UV+I0NqOABWi/MOi+IySPzYP+XgdPfRNx4vmoHYZwWOQ3t4Jd TEM= =oj6y -----END PGP PUBLIC KEY BLOCK----- --=_d5d2256c0c28877f294f503da42c58e9--