5 ms·
Why don't say intel laptop chips use that approach of say 4 high perf cores and 4 low perf efficiency cores? I get that they dynamically adjust the frequency b
by Havoc 8y ago
Why don't say intel laptop chips use that approach of say 4 high perf cores and 4 low perf efficiency cores?
I get that they dynamically adjust the frequency but surely cellphones can do that too?
- wmf 8y agoIt would probably take Windows five years to properly use the small cores.
- analognoise 8y agoSo? It's not like Linux on the desktop will suck less in 5 years.
- foobarbazetc 8y agoHow would any software know which CPU to use? Apple controls the entire OS and SoC so they can schedule different tasks onto different classes of CPU.
- seabrookmx 8y agoThe Linux thread scheduler already knows how to do this, which is why ARM's big.LITTLE architecture works fine in Android phones. There's zero reason MS couldn't implement this in Windows. In fact, it might already be done giving HP and others are currently shipping Windows on Snapdragon devices.
- foobarbazetc 8y agoI hadn’t looked at the sched code in a couple of years. Is this article up to date: https://community.arm.com/processors/b/blog/posts/ten-things-to-know-about-big-little https://community.arm.com/processors/b/blog/posts/ten-things... ?
- seabrookmx 8y agoI believe that patch referenced in the article for "global task scheduling" that allows you to use both the big and little cores at once is now in the mainline kernel. But I don't recall where I read this so apply a few grains of salt to my comment.
- unwind 8y agoWhy would it need to? Application-level software shouldn't need to care about that, it's way too low-level. If I do: #include <stdio.h> int main(void) { printf("Hello from some core!\n"); return 0; } that code doesn't need to think about which core it runs on, or even if there are multiple cores. Of course it does nothing to support multiple cores, but it does need some core to run on. The OS just schedules the process onto some core, and then it can of course monitor the process' performance and decide to move it, if it detects a better fit. All of that is invisible to the process itself. Of course high-performance/server software might want to actually care and use OS-specific API:s and services to deal with that, but those are the exception.
- umanwizard 8y agoI'm not exactly an expert. This is just speculation and I would love to be corrected if I'm wrong. I'd guess that the ratio of CPU power to display power is much higher in a phone (whose displays are small). If the Intel cores are idle anyway then their power consumption is probably so much less than the huge laptop display that it doesn't make a lot of sense to optimize further.
- nicoburns 8y agoI think because laptop chips tend to prioritise performance over battery life, at least compared to mobile chips.
- pcwalton 8y agoPretty sure this is the right answer. The power draw differential between your Intel laptop CPU and the ARM SoC in your phone is enormous.
- AgentOrange1234 8y agoEven when idle, extra cores still cost in terms of area (hence yield). So if you want to sell very cheap chrome books and such, that may not be attractive. Power isn’t at as much of a premium in a laptop cpu (bigger battery and also bigger screen, more ram, etc. so that the CPU part of the power draw is proportionally less)
- exrook 8y agoEDIT: After typing this up I realized big.LITTLE was mentioned and the article and it what OP was referring to but people may find the explanation useful so I'm posting it anyways I'm a little surprised no one else has mentioned this yet, but this is exactly what most modern cellphones do, the architecture is known as big.LITTLE [0]. There's basically three ways you can use the extra set of cores: 1. Either all high performance cores are used or all low performance cores are used, but never both. 2. The cores are paired up in twos, where only one member of each pair is active at a time. This is very similar conceptually to the way frequency scaling works in a desktop or laptop chip. 3. All cores are always available for use and processes are scheduled to either a high performance or low performance core as needed. Cores without any scheduled processes can be powered off or put in a low power state
- tigershark 8y agoNo, A12 can use all the cores at the same time, it is different from a traditional big.little. At least this is what they said during the event.
- floatboth 8y agoAs I understand it, all cores at the same time is traditional big.LITTLE, while paired cores are proprietary hacks (e.g. Tegra X1)
- zaarn 8y agoAMD might go for that IMO, they have the tech to "glue together a bunch of CPUs", to misquote Intel, they could feasibly make a low power and low perf CCX and pair it with a high power desktop CCX. The problem will likely be support by the OS, to my knowledge Windows doesn't have anything on board to manage switching to what essentially amounts a low-perf/low-power NUMA node to save power. I don't think Linux has something on board either.
- Narishma 8y agoARM's big.LITTLE works fine on Linux.
- zaarn 8y agoIIRC it doesn't work natively on Linux, ie needs a blob to work...
- pertymcpert 8y agoReally? I thought was just the job of the Global Task Scheduler in the kernel.