From nobody Wed Mar 22 19:40:53 2023 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 4Phf3K66bKz41Cx4 for ; Wed, 22 Mar 2023 19:41:01 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [74.104.188.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 (2048 bits) client-digest SHA256) (Client CN "m5p.com", Issuer "R3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Phf3K4Ff5z4GnZ for ; Wed, 22 Mar 2023 19:41:01 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Authentication-Results: mx1.freebsd.org; none Received: from [IPV6:2001:470:1f07:15ff::26] (court.m5p.com [IPv6:2001:470:1f07:15ff:0:0:0:26]) (authenticated bits=0) by mailhost.m5p.com (8.16.1/8.15.2) with ESMTPSA id 32MJesGt002753 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 22 Mar 2023 15:40:59 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Message-ID: <952d9795-19dc-8ad1-bb75-5c556ca6795a@m5p.com> Date: Wed, 22 Mar 2023 15:40:53 -0400 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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.4.0 Subject: Re: Periodic rant about SCHED_ULE Content-Language: en-US To: Mark Millard , FreeBSD Hackers References: <6BD317F2-7EDD-45C0-9DC9-5B94C1BBB8E1.ref@yahoo.com> <6BD317F2-7EDD-45C0-9DC9-5B94C1BBB8E1@yahoo.com> From: George Mitchell In-Reply-To: <6BD317F2-7EDD-45C0-9DC9-5B94C1BBB8E1@yahoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=10.0 tests=HELO_NO_DOMAIN,NICE_REPLY_A autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on mattapan.m5p.com X-Rspamd-Queue-Id: 4Phf3K4Ff5z4GnZ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[freebsd]; ASN(0.00)[asn:701, ipnet:74.104.0.0/16, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 3/22/23 15:21, Mark Millard wrote: > George Mitchell wrote on > Date: Wed, 22 Mar 2023 17:36:39 UTC : > [...] >> Here are the very complicated instructions for reproducing the problem: >> 1. Install and start misc/dnetc from ports. > > Installing is likely easy, as likely would be building > with default options (if any). I know nothing about > starting misc/dnetc so that is research. (Possibly > trivial, although if it has alternatives to control > then I'd need to match that context too.) service dnetc start > >> 2. Run "make buildworld". > > So on the 32 hardware-thread (16 cores) amd64 machine that > I have access to, the test is to only have buildworld use > about one hardware thread, no matter what else is going on. > I never would have guessed that the steps would not involve > more like -j$(sysctl -n hw.ncpu) (so around -j32 in this > context). So it is good that you provided your note or > I'd not know if I'd done similarly or not when trying such. > > [Note: -j1 and lack of -j are not strictly equivalent in > how make operates. As I remember, the distinction makes > a notable difference in the number of subprocesses created > directly by make (one per action "line" vs. one for the > whole block?). So even using -j1 might make a difference > vs. what you specified. I'd have to test to see.] I am literally running "make buildworld" with no additional options. > >> Standard out conveniently reports how long it took (wall clock). > > But nothing in your instructions indicate about how > to get an idea much progress dnetc made during the > various tests? [...] Honestly, I've never worried about this part. But dnetc logs its progress in /usr/local/distributed.net/dnetc.txt, though not in terms that are easy to relate to real-world progress. Oddly, when I run "make buildworld," I'm primarily interested in getting the world built. Perhaps others feel differently. > [...] > FYI: I've never built with and run the alternate > scheduler so if there is any appropriate background > for that that would not be obvious on finding basic > instructions, it would be appropriate to provide > such notes. > [...] You have to build a new kernel, using a config file in which you have replaced "options SCHED_ULE" with "options SCHED_4BSD". -- George