Content deleted Content added
Guy Harris (talk | contribs) Undid revision 1296784354 by 240E:47D:8F8:5A:60D3:F521:F587:2D0D (talk) - there are many reasons why implementing SMP may be complex; these are reasons why it may not scale. |
Guy Harris (talk | contribs) →Variable SMP: As "not only" was removed, "but" should also be removed. |
||
| (One intermediate revision by the same user not shown) | |||
Line 17:
Processors may be interconnected using buses, [[crossbar switch]]es or on-chip mesh networks. The bottleneck in the scalability of SMP using buses or crossbar switches is the bandwidth and power consumption of the interconnect among the various processors, the memory, and the disk arrays. Mesh architectures avoid these bottlenecks, and provide nearly linear scalability to much higher processor counts at the sacrifice of programmability:
<blockquote>Serious programming challenges remain with this kind of architecture because it requires two distinct modes of programming
SMP systems allow any processor to work on any task no matter where the data for that task is located in memory, provided that each task in the system is not in execution on two or more processors at the same time. With proper [[operating system]] support, SMP systems can easily move tasks between processors to balance the workload efficiently.
Line 88:
Variable Symmetric Multiprocessing (vSMP) is a specific mobile use case technology initiated by NVIDIA. This technology includes an extra fifth core in a quad-core device, called the Companion core, built specifically for executing tasks at a lower frequency during mobile active standby mode, video playback, and music playback.
Project Kal-El ([[Tegra 3]]),<ref name="AutoMQ-4" /> patented by NVIDIA, was the first SoC (System on Chip) to implement this new vSMP technology. This technology
== See also ==
| |||