The multicore future, and how to survive it
Avoiding the proprietary extensions trap
Multicore processors may offer a wealth of powers, but writing efficient code for them is notoriously difficult. Thankfully, help is close at hand.
The Multicore Association created the Multicore Programming Practices (MPP) working group just over a year ago to produce a guide on best practices for writing multicore-ready software in C/C++ without proprietary extensions.
Why produce a guide, when it’s generally recognized that development environments will eventually evolve to better support multicore processors, anyway? The MPP doesn’t think it wise to wait - especially as the Multicore Association believes that C/C++ will be the predominant programming language for at least eight years.
MPP chairperson and chief executive of CriticalBlue David Stewart said that the MPP's goal is to provide guidance to "software engineers [who] don't know what they don't know."
“There's capability in [multicore] platforms which is not being utilized or not being optimized by the software development community," Stewart said.
Stewart was speaking during a web cast to update people on the MPP’s progress on the guide since the group’s creation in May 2008. Delivery is scheduled for later this year.
Stewart outlined forthcoming chapters such as Analysis and High-Level Design, Implementation and Low-Level Design, Debug, and Performance Tuning, indicating the guidebook has already drawn from the experiences - and painful learning - of the broad range of software developers who are members of the MPP working group.
Developers from 29 companies and institutions are participating in the MPP effort, including multicore veterans from Freescale Semiconductor, Carnegie Mellon, Intel, Nokia Siemens Networks, Samsung, Texas Instruments, Wind River (acquired by Intel in June for $884m), LG Electronics, LSI, MIPS Technologies, National Instruments, and VMware.
In addition to the MPP, other recent developments on the multicore-programming front should bring comfort to coders. Last week, for example, Intel acquired RapidMind to beef up its in-house software-parallelism braintrust.
It seems the marriage of RapidMind and Intel will birth help for coders at about the same time as the MPP guidebook appears. "Later this year," says RapidMind's announcement, "we will provide more details about the integration of the RapidMind platform and Intel software products and technologies, including the Intel Ct technology for data parallelism."
Intel parallelist James Reinders promised great things on the Intel Software Network blog. "Rapidmind proved itself to be an innovative company with advanced technology for helping software developers with data parallel programming for multicore processors and accelerators. Their joining Intel will let us do even greater things together," he wrote.
Reinders also points to later this year as when coders should see the release of a beta of Intel's Ct Technology, designed "to provide programmers with tools that would abstract data-parallel programming away from the hardware."
Cut to the Apple multicore
Developers coding for Mac OS X, however, don't have to wait for multicore assistance - they've got Snow Leopard, seeded to them earlier this year and shipping to the masses this Friday.
Snow Leopard includes a multicore-assistance technology known as Grand Central Dispatch (GCD) - a mid-level technical explanation of which can be downloaded here (PDF).
According to Apple's technical explanation, GCD was created because: "The dominant model for concurrent programming - threads and locks - is too difficult to be worth the effort for most applications." Also: "The complexity of these issues has a well-deserved reputation for introducing bugs that are difficult to find and fix."
As Apple's explains it: "GCD shifts the responsibility for managing threads and their execution from applications to the operating system. Because the system is responsible for managing the threads used to execute blocks, the same application code runs efficiently on single-processor machines, large multiprocessor servers, and everything in between."
Mac OS X developers with whom we've spoken swear that GCD is relatively painless to implement. How many of them will actually choose to use it to better exploit the Core 2 Duos and Xeons in today's Macs, however, remains to be seen.
Macs aside, in a world in which multicore processors are the new standard, it's good to know that those who build the applications that run on them will get the assistance they need to plumb their potent powers. ®
Sponsored: DevOps and continuous delivery