Wind River Multicore Regional Conference Oct 2010 - Don Dingee


Published on

My presentation on the changing multicore landscape and how programming models are shifting to cope.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Wind River Multicore Regional Conference Oct 2010 - Don Dingee

  1. 1. <ul><ul><li>Don Dingee </li></ul></ul><ul><ul><li>October 20, 2010 </li></ul></ul>Wind River Multicore Regional Conference Solving the Multicore Maze: Today’s Challenges, Trends, and Solutions
  2. 2. The maze looks confusing <ul><li>What is a multicore processor capable of? </li></ul><ul><li>How does development have to change? </li></ul><ul><li>Will my application benefit from multicore? </li></ul>“ People don’t understand what they have.” - Tony King-Smith, Imagination Technologies
  3. 3. What you don’t know can hurt Charts courtesy VDC, September 2010 “NEXT GENERATION EMBEDDED HARDWARE ARCHITECTURES: Driving Onset of Project Delays, Costs Overruns, and Software Development Challenges”
  4. 4. Somebody is seeing the way
  5. 5. <ul><li>SoCs </li></ul><ul><li>General purpose CPUs </li></ul><ul><li>Graphics processors (GPUs) </li></ul><ul><li>Network processors (NPUs) </li></ul>Entering the maze is easy
  6. 6. Huge numbers of SoCs Is this single core, or multicore?
  7. 7. One flavor of CPU
  8. 8. But wait, there’s more
  9. 9. Another flavor of CPU
  10. 10. GPU 1600 streams in this, latest has 3200
  11. 11. NPU 32 cores designed around the network interface
  12. 12. Now that we’re in the maze <ul><li>It’s not getting smaller, or simpler – but that’s creating disruptive opportunity </li></ul><ul><li>Integration of EDA, silicon, operating systems, and tools providers is increasing </li></ul><ul><li>Competitive advantage = understanding your goal and what your app is trying to do </li></ul><ul><li>There will still be multiple approaches and tools, and no “magic bullet” </li></ul>
  13. 13. Understand the platform
  14. 14. Leverage the OS and runtime SW
  15. 15. Look around threading
  16. 16. Expose bugs dynamically
  17. 17. Looking deeper into threads
  18. 18. Hybrid approaches
  19. 19. Higher level middleware
  20. 20. So what, so what, … <ul><li>Range and speed of innovation is incredible </li></ul><ul><li>Embedded devices are connected life now </li></ul>
  21. 21. Smartphones everywhere <ul><li>Lots of drivers here: </li></ul><ul><li>Reliable connection </li></ul><ul><li>User interface </li></ul><ul><li>Multimedia streaming </li></ul><ul><li>Secure transactions </li></ul><ul><li>More apps by the hour </li></ul>
  22. 22. Tablets taking over <ul><li>Just watch while most PCs get replaced in next couple years </li></ul><ul><li>More space for multicore, battery means even more innovation coming </li></ul>
  23. 23. Digital home taking off <ul><li>TVs and STBs are gaining app content </li></ul><ul><li>Watch 2 channels, record 2, plus over the top content stream </li></ul>
  24. 24. Appliances getting smarter <ul><li>Wake on data </li></ul><ul><li>Do the job </li></ul><ul><li>Be aware </li></ul><ul><li>Sleep </li></ul>
  25. 25. Eye in the sky <ul><li>More mission, but less room onboard </li></ul><ul><li>Very dense and fast compute core requirements </li></ul>
  26. 26. In the network <ul><li>Deep packet inspection becoming mandatory </li></ul><ul><li>Look at every packet in transit </li></ul><ul><li>Make very sophisticated decisions based on content: security, priority, handling </li></ul>
  27. 27. What will you do next? <ul><li>Multicore is your next career! </li></ul><ul><li>This is just as big as the transition from digital logic to microprocessors </li></ul><ul><li>Or the transition from assembly to C </li></ul><ul><li>It will take some retraining, rethinking, redoing </li></ul><ul><li>The vendors get it and are actually ahead of the customers in most cases </li></ul><ul><li>Gap will close fast as competitive forces take over – just look at the applications we saw </li></ul>
  28. 28. Left to my own devices @dondingee [email_address]