The Big Interview: Pat Gelsinger

The Big Interview: Pat Gelsinger

Summary: Intel's Pat Gelsinger on the future of Itanium, technology in the developing world and the one-chip blade server of tomorrow

TOPICS: Emerging Tech

Pat Gelsinger is one of Intel's best-known executives. In nearly 30 years with the company, he has led the design team for the 80486 processor, produced the ProShare videoconferencing system and been chief technical officer during some of the most exciting — and troubled — times for the chip manufacturer. Now in charge of Intel's biggest and most important division, the Digital Enterprise Group, he's responsible for both the Core and Itanium processor lines.

In London for a conference on power management in data centres, Gelsinger sat down with ZDNet UK to discuss a wide range of issues, in particular how Itanium is converging with the new Core architecture, how quickly the developing world is catching up in supercomputing, and the debate he doesn't expect to see concluded before 2020.

Q: How are you getting on with moving developments in the Core architecture onto the Itanium?
A: Itanium used to be a shared development process between HP and Intel. We've consolidated that with the agreement we announced two years ago, which allowed us to integrate all of the Itanium development activities and get a consistent development methodology. Since that move, we've basically hit all of our timings — the first Montecito slip aside, we're back on track.

Part of that on-trackness means we can leverage the same circuit design libraries, process technologies, all of those other things we were not doing a good job with before. So going forward, the circuit techniques, the power-management technologies, all those sorts of things are much better leveraged. The first realisation of that is Tukwila [quad-core Itanium] in late 2008, the next step in the product family, where we move to common system architecture elements, as well as full alignment on design tools and process. It's still a different microarchitecture, a different instruction set, still aiming at a different market segment than the core of our product line. I'm driving for more convergence in Poulson [post-Tukwila Itanium] and beyond.

Presumably the cache architectures are converging as you move to a common bus?
Yep. You just get more and more, and some of the differences that we had before weren't for good reasons, and we're bringing those together, so I'm pretty happy that this gives us much better leverage for the R&D investments. As you move to common systems architecture it's much better investment for the customers as well. HP can say: "I can do a platform development, so I have a lower-end Xeon platform that can be used to bring Itanium lower in my product line", so you start to get that not just in our developments, but also in the OEM developments.

Do you see convergence continuing to the point where there's one chip with a mode bit [making it compatible with Core and Itanium]?
I don't see it getting that far, but I am driving these things to be as common as possible.

How's the heterogeneous versus homogeneous multicore debate going within Intel?
I expect that debate to be going until 2020, and I expect — in my crystal ball — different market segments coming to different conclusions in that discussion. You can clearly envision, and this is an easier discussion to have after IDF [Intel Developer Forum] than it is today, so we'll have to have the next instalment of this discussion after 17 April, but you can see the lower end of the product line having homogeneous, little cores. You could imagine the mid-range of the product saying: "We need some big cores, for performance, but little cores are more efficient for certain portions of the workload. You can imagine some embedded applications where you have big cores but with some special purpose cores for other, specific applications, maybe XML acceleration or packet processing or other things like that. A range of building blocks from little cores to big cores to special purpose cores. You now have a fabric of choices to mix and match for the market segment.

Won't you need some complicated design and verification tools to maintain a large library of very complex cores? Is that a limiting factor in the speed at which you can develop them?
Sure. Verification is already a limiting factor. That ends up being the rate-limiting portion of new products coming to market. That continues to be the case looking forward, although I do expect that to be helped by formal verification methods and formalisation of on-die interconnect. What happens is that near the CPU is a great sucking sound...

Some CPUs suck more than others...
In multiple respects... ah, anyway, the CPU starts hauling everything in. What you saw as the system architecture yesterday, tomorrow is the on-die architecture. As that starts to come together, some of these formalisations, interfaces, etc become part of the die. It's not that far away until you'll see the one-chip blade.

On 45nm, you've just announced a new transistor design. How far will it take you before you have to have another look at the transistor architecture?
There's the structure of the transistor and the materials of the transistor. The materials we just announced, the move to hafnium and metal gate is good for quite some time. We don't expect to change the material structure for a while — improve it, tune it, perhaps, but it's going to last us for several generations. In terms of the structure of the transistor, we're already been talking about changing to a tri-gate structure, changing the physical structure...

Topic: Emerging Tech

Rupert Goodwins

About Rupert Goodwins

Rupert started off as a nerdy lad expecting to be an electronics engineer, but having tried it for a while discovered that journalism was more fun. He ended up on PC Magazine in the early '90s, before that evolved into ZDNet UK - and Rupert evolved with them into an online journalist.

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to start the discussion