Date: Tue, 07 Feb 2023 07:29:15 -0600 From: Mike Karels <mike@karels.net> To: mike tancsa <mike@sentex.net> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: Raptor Lake / Alder lake on RELENG_13 ? Message-ID: <C95CE8CE-F545-4B09-81E9-EFC5C6F6F35C@karels.net> In-Reply-To: <0600fbab-035f-fd23-a6d7-27cd2f58665e@sentex.net>
index | next in thread | previous in thread | raw e-mail
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. Mikehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C95CE8CE-F545-4B09-81E9-EFC5C6F6F35C>