Feeds

The long slog to multicore land

Chip future must wait

Build a business case: developing custom apps

Multicore Expo Open standards and development tools are needed to accelerate the transition to a multicore future, according to minds at this week's Multicore Expo in Santa Clara, California.

As Markus Levy, president of the Multicore Association, put it: "Hardware's easy." Brian Carlson, Texas Instrument's Open Multimedia Application Platform (OMAP) marketing Manager agrees, saying, "The hardware's in place already to enable some really exciting applications that just aren't there yet.

"The challenge is closing that gap between hardware and software."

And when Carlson and others talk about multicore hardware, they're not simply talking about multicore processors such as the familiar CPUs from Intel and AMD. They're talking about multicore systems-on-chip (SoCs), digital signal processors (DSPs), graphic processing units (GPUs), and other specialized silicon.

Creating applications that run seamlessly on a diverse array of multicore silicon is no easy feat - especially when those elements are sharing processing duties by means of emerging industry standards such as OpenCL.

Levy says that what has yet to be solved is the methodology and not the technology. "Everybody knows these days," he says, "that the technology seems to be running at a much faster pace than the methodology."

Key to multicore methodology are parallel-programming approaches, "which everybody is going crazy about trying to figure out," says Levy. "How do you debug these things? What kind of new problems arise as you move into multicore land?"

To make matters even tougher, there's the problem of legacy-code conversion, which Levy described as "How do I take my quadrillion lines of code and convert it to a multicore platform?"

What's missing is a widely accepted, standardized multicore programming model that goes beyond traditional symmetric multiprocessing (SMP). SMP is well-suited for a world in which identical processor cores sit in their own packages and communicate over external datapaths, but it's a limited model for cores of different types - CPUs, GPUs, DSPs, and so on - that share resources and tasks on a single die.

Without open standards such as OpenCL, all developers will be forced to invent their own methodologies. Carlson was emphatic about standards, calling them "critical." Nokia's Kari Pulli agreed, saying that "We need to create something that protects developers from change - that's why standards are crucial."

Without an appropriate set of standards, many multicore system and software designers are developing their own proprietary systems, which limits software from being used on multiple platforms. If a developer creates a vertical product - whether hardware or software - it stays in that vertical space, able to run only the software designed specifically for it. Also, that software can't be run on other silicon.

That's a recipe for a fragmented market and for end-users getting locked into a particular vendor's "solution."

As Levy says, "There's a lack of a flexible general-purpose multicore programming model," a situation that "limits a programmer's ability to transition to multicore programming. Everything has to be hand-done and redone."

Help is on the way, however. For their part, the Multicore Association is currently working on a set of "cohesive" APIs (application programming interfaces - essentially agreed-upon sets of commands that software developers use to communicate with hardware) for multiple multicore platforms. The Association has completed a communications API and is working on one for application-level resource management. A task-management API is also in the works.

The Association also has a working group that's developing a "best practices guide" for multicore programming.

The development community is pitching in, as well. For example, PolyCore Software has been providing multicore tools since shortly after its founding in 2004, focusing primarily on the communications industry. At the Expo, the company announced Poly-Mapper, a new tool designed, as the company explains, "for rapid creation of validated multicore communications topologies."

PolyCore's contributions, however, are aimed deep inside multicore systems, focusing on such nitty-gritty as inter-core communications. At a slightly higher level comes help from CriticalBlue, which at the Expo introduced a new tool for embedded-system designers called Prism that lets developers test their existing linear code to see how it might benefit from a transition to a multicore SoC.

Tools are coming and standards are arriving along with APIs. But as Tony King-Smith, VP of marketing for chip-designer Imagination Technologies put it when referring to the OpenCL standard, "It's not a universal panacea - we have a couple years of pain ahead."

But the performance and power-saving promise of a multicore future is inarguable. It's just that the future's not here yet. ®

The essential guide to IT transformation

More from The Register

next story
Reg man looks through a Glass, darkly: Google's toy ploy or killer tech specs?
Tip: Put the shades on and you'll look less of a spanner
So, Apple won't sell cheap kit? Prepare the iOS garden wall WRECKING BALL
It can throw the low cost race if it looks to the cloud
One step closer to ROBOT BUTLERS: Dyson flashes vid of VACUUM SUCKER bot
Latest cleaner available for world+dog in September
Samsung Gear S: Quick, LAUNCH IT – before Apple straps on iWatch
Full specs for wrist-mounted device here ... but who'll buy it?
Apple promises to lift Curse of the Drained iPhone 5 Battery
Have you tried turning it off and...? Never mind, here's a replacement
Now that's FIRE WIRE: HP recalls 6 MILLION burn-risk laptop cables
Right in the middle of Burning Mains Man week
Apple's iWatch? They cannae do it ... they don't have the POWER
Analyst predicts fanbois will have to wait until next year
Tim Cook in Applerexia fears: New MacBook THINNER THAN EVER
'Supply chain sources' give up the goss on new iLappy
HUGE iPAD? Maybe. HUGE ADVERTS? That's for SURE
Noo! Hand not big enough! Don't look at meee!
prev story

Whitepapers

Top 10 endpoint backup mistakes
Avoid the ten endpoint backup mistakes to ensure that your critical corporate data is protected and end user productivity is improved.
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Backing up distributed data
Eliminating the redundant use of bandwidth and storage capacity and application consolidation in the modern data center.
The essential guide to IT transformation
ServiceNow discusses three IT transformations that can help CIOs automate IT services to transform IT and the enterprise
Next gen security for virtualised datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.