At the Consumer Electronics Show this week, Samsung Electronics unveiled the world’s first mobile application processor with eight general-purpose processing cores in total. Samsung’s Exynos 5 Octa takes advantage of ARM’s Big.Little technology and features four high-performance cores as well as four low-power cores.
Samsung Exynos 5 Octa has four ARM Cortex-A15 high-end general-purpose cores for demanding applications as well as four more ARM Cortex-A7 low-power cores for use cases where maximum computing performance is not required. Samsung did not disclose any additional details about the chip, but it is likely that the new application processor will feature new ARM Mali graphics core as well as support for advanced graphics technologies, such as output to UHD 4K (3840*2160) resolutions. The chis is made using 28nm HKMG process technology at Samsung's manufacturing facility near Austin, Texas.
“The new Exynos 5 Octa introduces a whole new concept in processing architecture designed for high-end smartphones and tablets. When you want multiple applications to perform at their best, you want the best application processor currently available – the Exynos 5 Octa,” said Stephen Woo, president of system LSI business at device solutions division of Samsung Electronics.
Big.Little processing combines two different, but compatible processors within the same SoC and allows the power management software to seamlessly select the right processor, or multiple processors, for the right task. The efficient and seamless switching of workloads between the two processors is supported by advanced ARM system IP, such as AMBA 4 ACE coherency extensions, which ensures full cache, I/O and processor-to-processor coherency between the Cortex-A15 and Cortex-A7, and across the complete system. Software and applications can therefore continue to run unhindered, and unnoticed by the user, as the tasks are rebalanced to provide the optimum Big.Little user experience.

Glenn Roland, vice president and head of new platforms and OEM at Electronic Arts, helped Samsung to demonstrate the processing power of the Exynos 5 Octa by showing off one of EA’s latest 3D racing games, Need for Speed Most Wanted. Atop the reference device, the application processor delivered an elevated real-life gaming experience within the mobile platform, rendering stunning graphics performance and real-time response speed, according to Samsung.
Samsung Exynos 5 Octa system-on-chip will probably power Samsung’s flagship smartphones and tablets due this year and will compete against products like Nvidia Tegra 4, Qualcomm Snapdragon S4 and other high-end solutions.
Tags: Samsung, Cortex, Big.Little, ARM, 28nm, Exynos
Comments currently:
8
Discussion started: 01/12/13 01:17:43 PM
Latest comment: 01/29/13 05:55:28 AM
Expand all threads |
Collapse all threads
[1-2]
1.
This isn´t a true octacore, the big.LITTLE concept is about of duos of cores that show to the system like a unique core. A weak (little) core to low workload, and a strong (big) core to high workload.
The two cores doesn´t run simultaneously, only one of them.
So, exynos 5 is a Quad Core, like the Tegra3/4 is a Quad Core too, and itsn´t a "Pentacore".
BUT all of this crap of "octacore" is marketing in action. Xbitlabs should be more skeptic about marketing material for the press.
show the post
0
3
[
Posted by: er_wendigo

|
Date: 01/12/13 01:17:43 PM]
+ expand thread (2 answers)
- collapse thread
Actually it depends how the scheduling is done. There is a simple scheduling model which simply pairs the high and low power cores as you describe and transparently switches between them based on load. There is however a more sophisticated scheduling model that may be used if both the hardware and operating system support it where all 8 of the cores are visible to the OS and can be individually assigned tasks in any combination by the scheduler.
3
0
[
Posted by: Prosthetic_Head

|
Date: 01/13/13 05:12:40 AM]
No, this trick doesn´t work. Read my answer to vampire36.
show the post
0
3
[
Posted by: er_wendigo

|
Date: 01/14/13 03:56:57 AM]
2.
Bla Bla Bla !
Samsung > Everyone else.
2
0
[
Posted by: Vampire36

|
Date: 01/13/13 08:30:03 AM]
+ expand thread (4 answers)
- collapse thread
No, it isn´t that at all.
You´ll needs at least a very explicit support from the task scheduler of the O.S.
So, now and in the near future, this is zero support for it.
But, whatever, this is speculation, the truth is that you can´t do:
"In the big.LITTLE task migration use model the OS and applications only ever execute on Cortex-A15 or Cortex-A7 and never both processors at the same time. This use-model is a natural extension to the Dynamic Voltage and Frequency Scaling (DVFS), operating points provided by current mobile platforms
with a single application processor to allow the OS to match the performance of the platform to the performance required by the application."
http://www.arm.com/files/...ig_LITTLE_Final_Final.pdf
Page 5:
"the OS and applications only ever execute on Cortex-A15 or Cortex-A7 and never both processors at the same time."
Both cores never runs at the same time. This is the big.LITTLE way of running code, so it´s a quad core. A 4+4 core, maybe, but itsn´t a real octocore, like Tegra3/4 aren´t a pentacore.
show the post
0
3
[
Posted by: er_wendigo

|
Date: 01/14/13 03:55:04 AM]
I love it. Some people deny reality with "dislikes".
You see, it´s about the docs of ARM about big.LITTLE configs of cores.
If you has a "better argument" than ARM documentation, show us.
show the post
0
3
[
Posted by: er_wendigo

|
Date: 01/14/13 09:00:05 AM]
You are wasting your time.
You already know the truth.
2
0
[
Posted by: Vampire36

|
Date: 01/15/13 05:04:52 AM]
These are real quotes from arm documentation and they are relevant so I have no idea why people are down-voting you for posting them to support your case.
I mention the alternative scheduling model since it was discussed at the ARM conference late last year and has been mentioned in other documentation. It probably will be the case that the first uses of big.LITTLE will be as you describe, using the simpler scheduling model and that the more sophisticated model where all cores are visible to the OS scheduler is currently still a concept in development. The big.LITTLE concept isn't necessarily limited to switched pairs of cores, although many implementations probably will be.
0
0
[
Posted by: Prosthetic_Head

|
Date: 01/29/13 05:55:28 AM]
[1-2]