Skip to main content

If you don't have an IBM ID and password, register here.

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. This profile includes the first name, last name, and display name you identified when you registered with developerWorks. Select information in your developerWorks profile is displayed to the public, but you may edit the information at any time. Your first name, last name (unless you choose to hide them), and display name will accompany the content that you post.

All information submitted is secure.

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

New to Cell/B.E., multicore, and Power Architecture technology

The Multicore acceleration technology zone on developerWorks contains articles, tutorials, and tips to help developers with Cell Broadband Engine™, multicore, and Power Architecture™ application development, optimization, and migration. For users trying to find their way in a new topic, all of that information can be overwhelming. This page provides an overview for readers who would like to learn about this technology but don't know where to start.

What is Power Architecture technology?

While some chip manufacturers have multiple architectures within a single company under a unified brand, Power Architecture technology offers a unified architecture spanning multiple companies under a single brand.

What's the Cell Broadband Engine (Cell/B.E.) processor, then?

The 64-bit Power Architecture provides the foundation on which the Cell Broadband Engine Architecture (CBEA) is built. CBEA-compliant processors support 32- and 64-bit Power and PowerPC applications. Cell not only supports the Power Architecture ISA, but it inherits the memory translation, protection, and SMP coherence model of mainstream 64-bit Power processors. CBEA also supports virtualization (logical partitioning), large pages, and other recent innovations in the Power architecture, making it quite easy to port an existing operating system, such as Linux®, from Power to a Cell/B.E. and leverage the Power processor core.

The CBEA extends Power Architecture in several ways:

Oh, and it was spawned as a collaboration by IBM, Sony, and Toshiba.

Why is Power Architecture technology important?

The really interesting (and important) thing about IBM Power Architecture technology is the unique way in which IBM and its partners have come together to make it an open hardware platform. Based loosely on the Linux model (where a cadre of insiders are responsible for maintaining a stable kernel, on which the wider community can base distributions, applications, and so on), the Power Architecture community has formed the not-for-profit organization Power.org™, where a cadre of insiders are responsible for maintaining a stable instruction set architecture (ISA) on which the wider community can base systems, code, cores, and so on.

OK, why is Cell/B.E. technology so important, then?

Have you been under a rock? It powers the Sony Playstation™ 3 game console (and while I'm at it, Power processors rule the other two latest top game consoles: the Nintendo Wii® and the Microsoft Xbox 360®). It is starting to show up in various hybrid supercomputers, such as the Los Alamos National Laboratories' Roadrunner Cell/B.E./Opteron hybrid and the IBM BladeCenter™ QS21 sports. And there are already third-party boards by Mercury Computer Systems (and even Sony and Toshiba) making their appearances. (Legal disclaimer: "The supercomputer was designed and developed for the DOE and Los Alamos National Laboratory (LANL) under the DOE / LANL project name Roadrunner. The Roadrunner project was named after the state bird of New Mexico.")

Cell/B.E. technology promises to make quite a splash anywhere compute-intensive applications are needed, such as on-the-fly, real-time rendering (games, medical imaging) and complex systems modeling (weather patterns, orbital object tracking, financial market prediction, genetic analysis, pharmaceutical synthesis).

Other than the Cell/B.E., which other different kinds of processors are based on the Power Architecture platform?

Power Architecture family members are stealthy chips, and they like to go by many different names. They can be hard to keep track of because they don't all use the Power or PowerPC trademark. The well-known and ubiquitous Motorola PowerQUICC chips are PowerPC, though most chips Freescale makes get names like MPCxxx. The Microsoft XBox 360's CPU, the Sony Playstation 3, and the chip for Nintendo's Wii console are all based around PowerPC, as are the ultra-low-power PWRficient multicore processors from P.A. Semi. Xilinx FPGAs are a hybrid architecture incorporating Power Architecture technology. And many other implementations of Power Architecture technology exist for printers, automobiles, routers, and the like.

Where can I find out about the Cell/B.E. processor?

The developerWorks Power Architecture zone provides lots of resources on the Cell/B.E. processor, including:

Which machines are based on Power Architecture processors?

The "PC" in PowerPC doesn't mean "personal computer"; it stands for Performance Computing. Now the POWER line of chips is found only in high-performance servers and workstations from IBM, but the PowerPC chips are found in everything from embedded devices to supercomputers (you may already own one, especially if you're a gamer, run a home network, or drive a late-model car).

Is Power Architecture buzzword-compliant? How about things like dual-core, multicore, hypervisors, partitioning, and virtualization?

Where do you think these terms come from? The IBM POWER4™ was the industry's first multicore design way back in 2001 (remember 2001 when the HAL 9000 ran amok?). Before that, the POWER3™ was one of the first 64-bit chips in the industry back in the 1990s (when the West was young). And we've been virtualizing virtually everything on the IBM mainframes since before many of you were born. Afraid of industry buzzwords? We eat 'em for breakfast (and will even happily run all of your Web 2.0 applications for you).

Aren't Power Architecture processors slower than x86 chips? Aren't they really only for niche applications?

First, no. Raw processor clock speed is no longer as important as it once was in the world of chips (in fact, it was never really all that important in the first place). The Power Architecture-based Cell/B.E. processor beats even the newest x86 chips in performance, hands-down, and the Blue Gene®/L is still at the top of the Top500 list, setting new speed records with satisfying regularity.

As for the niche argument, that too is complicated. On the one hand, x86 gets an awful lot of attention because it's in a lot of desktops. But desktops themselves are a niche market (albeit a high-profile one). Desktops make up just a tiny fraction of worldwide microprocessor sales annually; a much larger majority of semiconductor devices finds its way into things like cars and cell phones and the like.

On the other hand, it's true that things like supercomputers, gaming consoles, UNIX® servers, automotive controllers, routers, and so on could each be considered their own separate markets—and Power Architecture technology and performance dominates in all of those segments. With the flexibility to scale from controllers for elevators and traffic lights to gigantic superclustered supercomputers, you might say that with Power Architecture technology, "one architecture fits all."

Which operating systems and software run on the Power Architecture platform?

To paraphrase Henry Ford, you can have any flavor operating system you want, as long as it's orange, uh, POSIX!

Are there specific considerations that should go into writing code for or porting code to Power Architecture technology?

Not really. Because we're talking about POSIX, the apocryphal story of a porting effort amounting to "just typing >make" pretty much applies—provided you are working with well-behaved code, of course.

For those developers who favor scripting languages such as Perl, PHP, Ruby, and so on, you should not notice any differences. For developers attempting to write cross-platform Java™, the chip architecture is the least of your worries (snark, snark). And for those among you who stick to solid performers like C and Cobol, a simple recompile really should be enough, be it from one chip architecture to another or from one Power Architecture processor to another (although Power Architecture binaries usually do work just fine from one family member to another, thanks to the stability of the ISA).

If you have to dip into assembly, you will notice a difference, although it's a breath of fresh air if you're coming from a slightly more old-fashioned architecture with few general-purpose registers. The only things you won't be able to easily just run on PowerPC are proprietary, platform-specific languages, such as Visual Basic or .NET (although, even there, projects like Mono might get you the support you need).

So how do I design a PowerPC-based processor?

While some chip manufacturers offer desktop processors that are, oddly enough, called "cores," IBM offers you the actual, real core: the basic building block for a processor, just waiting to be customized with your intellectual property (IP) or others'. Cheaper than ASICs, the proven stability of a mature core can shave many a man-hour from design and testing schedules. The Power ISA-compliant design likewise enables easier coding and, in general, speeds your time to market. Of course, ASICs are available as well for when you require truly custom solutions.

What is the IBM foundry, and why is it so special?

IBM holds thousands of patents in new materials, devices, and design methodologies for microelectronics (and IBM Research just keeps cranking out more every year). Our building 323 at East Fishkill won Semiconductor International's 2005 Top Fab award, and our foundry is recognized industry-wide as a leader in both process and technology. IBM was even awarded the National Medal of Technology for semiconductor innovation. And that's not even to begin to discuss the IBM-Chartered Common Process technology, thanks to which customers have even more choice—and leverage—when it comes to the crucial milestone of finally executing your carefully crafted design. That's what's special.

By the way, did you know that it takes US$7 billion to US$8 billion of revenue to support a 12-inch fab? And yet it's fabulous to be fabless, as Xilinx can attest: this Power Architecture technology partner pioneered fabless semiconductor manufacturing back in 1984. And if you are fabless, you couldn't choose a better partner than IBM: in recent years, IBM foundries and technology have been thrown open to outside customers like never before, while Common Platform technology from IBM, Chartered, and Samsung offers design enablement and cross manufacturing on broadly supported CMOS process technologies.

How can I improve my Power Architecture skills?

First, read every article posted to the developerWorks Power Architecture zone. Then, read them again. (Good, that will get our page view statistics nice and high -- thanks!) Next, explore some of the following resources:

But what if I want more on Power Architecture technology?

The most important thing you can do is check the developerWorks Power Architecture technology zone several times each day! Just kidding. (Not really.) Add some of these fine sources to your online repositories:

What's your favorite color?

Blue. Big blue.

This NEWTO is a living, breathing document that is regularly updated. Let us know if there's something you'd like to see us add.

Help: Update or add to My dW interests

What's this?

This little timesaver lets you update your My developerWorks profile with just one click! The general subject of this content (AIX and UNIX, Information Management, Lotus, Rational, Tivoli, WebSphere, Java, Linux, Open source, SOA and Web services, Web development, or XML) will be added to the interests section of your profile, if it's not there already. You only need to be logged in to My developerWorks.

And what's the point of adding your interests to your profile? That's how you find other users with the same interests as yours, and see what they're reading and contributing to the community. Your interests also help us recommend relevant developerWorks content to you.

View your My developerWorks profile

Return from help

Help: Remove from My dW interests

What's this?

Removing this interest does not alter your profile, but rather removes this piece of content from a list of all content for which you've indicated interest. In a future enhancement to My developerWorks, you'll be able to see a record of that content.

View your My developerWorks profile

Return from help

Content navigation