From nobody Tue Feb 07 13:41:07 2023 X-Original-To: freebsd-stable@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 4PB45x53Rfz3n0PG for ; Tue, 7 Feb 2023 13:41:09 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (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 "smarthost1.sentex.ca", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PB45x2wwmz3PqD for ; Tue, 7 Feb 2023 13:41:09 +0000 (UTC) (envelope-from mike@sentex.net) Authentication-Results: mx1.freebsd.org; none Received: from pyroxene2a.sentex.ca (pyroxene19.sentex.ca [199.212.134.19]) by smarthost1.sentex.ca (8.16.1/8.16.1) with ESMTPS id 317Df6PN019046 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL); Tue, 7 Feb 2023 08:41:06 -0500 (EST) (envelope-from mike@sentex.net) Received: from [IPV6:2607:f3e0:0:4:d4f2:9647:fa6a:7176] ([IPv6:2607:f3e0:0:4:d4f2:9647:fa6a:7176]) by pyroxene2a.sentex.ca (8.16.1/8.15.2) with ESMTPS id 317Df6uK093623 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Tue, 7 Feb 2023 08:41:06 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <8b609a35-cd3c-b191-ec8e-a0819cfc013e@sentex.net> Date: Tue, 7 Feb 2023 08:41:07 -0500 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: Raptor Lake / Alder lake on RELENG_13 ? Content-Language: en-US To: Mike Karels Cc: FreeBSD-STABLE Mailing List References: <0600fbab-035f-fd23-a6d7-27cd2f58665e@sentex.net> From: mike tancsa In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4PB45x2wwmz3PqD X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:11647, ipnet:2607:f3e0::/32, country:CA] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 2/7/2023 8:29 AM, Mike Karels wrote: > On 6 Feb 2023, at 16:04, mike tancsa wrote: > >> Hi All, >> >>     I have seen a couple of commits around these CPUs, but wondering if anyone is running 13 on these newer hybrid CPUs ? Do the slower cores just get disabled or are they made use of somehow ? >> >>     ---Mike > I have been testing the changes on -current, and they are working fine. I have not tested on 13, but I would expect the same result. The workaround is on 13-stable, but not yet a RELENG branch. Presumably it will be in 13.2 when it is branched. If no one else has reported, I will test the 13.2 branch. Also, I haven’t heard of tests on Raptor Lake, but I have heard that the behavior should be the same as Alder Lake. > > The E-cores are not disabled. They are forced to use a less efficient method of page invalidation. They are scheduled as if they were P-cores without threads, but they are less used because of the shared cache among 4 cores rather than 2. I have some preliminary scheduler changes that recognize the slower cores, but there are still issues to be dealt with. > Thank you very much for the detailed update!  Apart from some performance tweaking, would you say performance overall is pretty good, or will the scheduler enhancements need to be made still ?     ---Mike