With regard to the issue identified in the story and video (coordination of process, thread, and vector level parallelism), I think there is a positive and a negative aspect for embedded developers. The negative aspect for embedded developers is that much of the work for addressing this issue is being done in the desktop & server space. The balance between OpenMP and automatic vectorization mentioned in the article is available in a compiler for desktop and server. OpenMP is not supported on traditional embedded OSes to my knowledge.
The positive aspect is that embedded developers typically have more control over the other applications that may be executing on the system. For example, you may have one process that is taking full advantage of the number of cores on the system, however if there is another application that is doing the same, you will typically end up with non-optimal performance. On a desktop system, a developer doesn’t typically know the other applications that a customer may choose to execute.
An embedded systems developer would have better knowledge of other apps on the system and would be in a better position to do something about it.
Just thought I’d share some further thoughts on the interview.
MaxPosted on: Friday, February 20, 2009 at 2:45 pm
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.