big.LITTLE Software Update - Open source software for ARM SoCs - Linaro
linaro.org/linaro-blog/2013/07/10/big-little-...Posted Jul 13, 2013, 10:03 AM UTC
286
Posted Jul 13, 2013, 10:03 AM UTC
[deleted]
It means future implementations of big.Little ARM SoC's are expected to have much better performance and possibly lesser power consumption. Right now, Samsung implemented arguably the worst form of big.Little (but easiest to develop) in the Exynos 5410 (Octa). Unfortunately due to a required hardware component that is either botched or not implemented properly, these two new forms of big.Little won't be supported on the currently available Exynos 5410. But on the bright side, future big.Little SoC's should be pretty competitive with Qualcomm SoC's (theoretically at least).
[deleted]
But what does this mean?
Well, right now, the i9500 can only use one quad-core cluster at a time. Imagine two different teams of people who are in two salary tiers. You have to pick either the highly skilled team that costs a lot or the team that is cheap and will get the job done a little more slowly. Each team is package deal and won't work without the rest of the team.
What this development hopes to introduce is allowing the system to pick and choose either two of each team, or one from one team and three from another.
This is a lot cheaper from a power perspective. If you had to constantly switch from one team or another (current case), you expend a lot of power in team A informing team B of what A had been doing so that B could continue the work (let's say this communication requires a lot of effort to write up a pretty report for the other team to understand). This new case allows all eight members to be in the loop of the current operations so that you could pick any combination of four from both teams and they would be able to work without expending the time and effort of bringing up to speed the members that just got into the office.
A bit more technically but still dumbed down explanation (I really can't provide any deeper insight than my dumbness permits): instead of needing to push per core memory from one cluster to shared memory and then to the other cluster's cores, they all read from shared memory and push their progress back onto it. While the time savings are minimal on such fast and low latency memory, the power savings should be immense.
big.LITTLE has the potential to be really power efficient for how fast it can scale up to, but its implementation on the Galaxy S4 was lazy. To make you really appreciate how big of a leap this could be, know that the Exynos 5 Octa's power consumption is on par with that of the Snapdragon 600 family, despite containing a lot more silicon.
For more info, you can check out the latest AnandTech podcast (21).
[deleted]
Regarding the current situation:
I don't understand the difference between what I said and what you said. Could you explain?
I was under the impression that this was the case. Could you provide any documentation? I can only refer back to the AnandTech podcast I previously linked.
Regarding how big.LITTLE will be implemented from now on:
Oh, well that's impressive while also being a shitshow. Eight asymmetric with disparate instruction sets... good luck kernel devs.
[deleted]
So you're saying the in-order and out-of-order chips don't need a little meditation to maintain coherency?
Also, I'm pretty sure the Exynos 5 Octa functions as described in this white paper from a while back. In it,
Aren't they both ArmV7?
Well right now, the Exynos 5410 can either use only the A15 cluster or the A7 cluster. It's not possible to run, say 3 A7's and one A15 cores right now, but it will be possible in future variants to do this through the code developed by Linaro and also the other version allows all 8 cores to be used like you said.