From nobody Wed Apr 12 18:43:08 2023 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 4PxWmx26Nmz44WkK for ; Wed, 12 Apr 2023 18:43:13 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail2.karels.net (mail2.karels.net [3.19.118.201]) (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 "freebsd", Issuer "freebsd" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PxWmw0GwZz4V0g; Wed, 12 Apr 2023 18:43:12 +0000 (UTC) (envelope-from mike@karels.net) Authentication-Results: mx1.freebsd.org; none Received: from mail2.karels.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by mail2.karels.net (8.16.1/8.16.1) with ESMTP id 33CIh9F1056032; Wed, 12 Apr 2023 13:43:09 -0500 (CDT) (envelope-from mike@karels.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=karels.net; s=mail2; t=1681324989; bh=w8UrvL+opMvr4l38L4sm0BmKhE7HkBk89RYfK5WREhE=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=KSALKskXS/i2dksTS8MNkJpBcA5pk/lC2y1Lm0n48lYkdnoO4i7ODO/K7MKNZAUZE 0lv0lUyncazOZhSRUIhy9ksm876c0aOPc8RlbYWbvaMP1M6q5ceKsHTVEhmPqXzVoL PmFpPH/SoMXpF2oS58v0+xuzLy34OWsjvc9BHpDsz5dnrtI2FU54Hm3zmX6s40T6lW UJwWN2OHw+bRXVJdoYnEI2QnljrOy5P/pMikVq2aLtUryp7+OAKDIqz9tAc2wG2uzQ wreRa7qczk8U2dK9LAeEfKJlTmFuiTht6uStSS97vM/3D69ofsvF7bns99uj7egGZq es3oE29+4Y37A== Received: from [10.0.2.130] ([73.62.165.147]) by mail2.karels.net with ESMTPSA id KapDCr37NmTe2gAAs/W3XQ (envelope-from ); Wed, 12 Apr 2023 13:43:09 -0500 From: Mike Karels To: Dries Michiels Cc: freebsd-current Subject: Re: Status of Alder and Raptor lake on FreeBSD Current Date: Wed, 12 Apr 2023 13:43:08 -0500 X-Mailer: MailMate (1.14r5937) Message-ID: <1B74CD55-A473-42AC-AE8B-73AE60121143@karels.net> In-Reply-To: References: 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=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4PxWmw0GwZz4V0g X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16509, ipnet:3.16.0.0/14, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 12 Apr 2023, at 9:59, Dries Michiels wrote: > Hello current mailing list, > > I was wondering what the status of Alder/Raptor lake support is on FreeBSD? > Does it boot? Integrated graphics are supported from what I recall with the > newest drm drivers. -current and 13.2 boot and run on Alder Lake, and probably Raptor Lake (I haven’t heard of any tests). There is a bug, probably in hardware, that affects page invalidation on E-cores, but a workaround changes the mechanism on the E-cores to compensate. I have no information on graphics, maybe someone else does. > Are there any plans for changes to our scheduler to account for efficiency > and performance cores? > Are there real world downsides of not having such a scheduler when running > an Alder or Raptor lake CPU? I have been working on scheduler changes, but slowly. Things work surprisingly well without them though. An E-core is slower than the first thread on a P-core, but faster than the second thread. The scheduler puts fewer processes on the E-cores because of the shared cache in groups of 4 CPUs (vs 2 for SMT on the P-cores). Of course, with enough processes, they all get used. > Interested to hear from users using these CPU's right now in there system! > The Reason I ask is that I'm interested in upgrading my home server > hardware :-). I’m running -current on an i7-12700K, and it feels fast compared to my i7-10700K. Mike