... and their current hybrid CPUs are just these two glued together on a single die.
Intel generally has two families. One is regular 'Core' CPUs (with HTT enabled or not) that originate in Nehalem arch: - en.wikipedia.org/wiki/Nehalem...en.wikipedia.org/wiki/Intel_A...
... and that is a disaster for OS scheduler ... imagine how many more lines of code it would need to at least TRY to succeed in this scenario ... and to make it more fun - there is also NUMA. Curtain falls.
What is even more interesting - is that there are actually THREE types of thread speeds in modern Intel CPUs. 1. Real fast 'performance' core. 2. Real slow 'efficiency' core - which is about 0.5x of 'performance' core. 3. Virtual 'HTT' thread - at about 0.1-0.2x speed of 'performance' core.
Some OSes just 'attach' processes known to be less CPU hungry - like cron - or some periodic(8) like tasks - but its just a workaround. For example a database engine will by default use all the cores and would not know which are which - and this will kill performance.
At least its possible to disable these 'efficiency' in BIOS ... but then - they still take space on CPU die. IMHO the idea of having - for example - two small really efficient cores is not bad - but its hard for OS to decide which ones to use and when - which kills power efficiency.
Its available on FreeBSD as 'graphics/gmic' package % cd /usr/ports/graphics/gmic % head -1 pkg-descr G'MIC is a full-featured open-source framework for image processing, distributed under the CeCILL free software licenses (LGPL-like and/or GPL-compatible). It
Here you have everything covered: vermaden.wordpress.com/2023/08/18/f...
The Bhyve FreeBSD hypervisor (called/spelled 'beehive' usually) was created almost 10 years ago. Right now it offers speed and features that other similar solutions provide - such as KVM/VMware/XEN. Y...
Today was that lucky day for me.