Triple Play

Tejas To Be A Modular Processor?

Here’s the article mentioning this.

The concept itself is fascinating. In theory, you could “build your own CPU,” including the things you do want, and exclude the things that you don’t.

If you’re Joe Sixpack, or his mom, you can go with the minimum. More rabid folks can get (and pay) more.

Please note what this scenario would do eventually, though. It would free Joe Sixpack from the geeks.

As it stands now, the geeks have essentially dragged Joe Sixpacks along the road of faster CPUs, and having Joe foot most of the bill. The advanced R&D got spread among all the CPUs, whether used or not.

What modular CPUs do is not only isolate basic and advanced CPU functions, it also isolates their cost. If, for instance, Intel makes a core 32-bit processor, gives people a 64-bit option, and only 5-10% want it, those who want it are likely to bear most or all of the costs for that technology. Not Joe.

That would mean cheaper processors for most people, and significantly more expensive ones for those who want or need more.

That’s good for Joe. It’s no big deal for the professionals for whom time is money.

For those inbetween (like most in this audience), you’re caught between a rock and a hard place.

We’ve thought for years that the PC market would eventually split into two much separate markets: the PC as a cheap consumer electronics good for most, business-as-usual (but with much higher prices) for those who need more than that.

This is another step in that direction.

However, Intel’s near-term intentions are probably rather more modest.

How To Do A Multicore

I suspect that this is going to be Intel’s way to implement multicores. What should be noted is that multicores can be implemented a number of ways, and do different things.

First, there is the simple dual-processor concept. You have two identical chips working together on the notion that two heads are better than one.

I don’t doubt they’ll do that. Indeed, we may very well see something like this within a couple years: Intel puts together two cores running at relatively low-speeds, and then claims to have the equivalent of a 8 or 10GHz processor.

They’ve made comments hinting at that in the past, and this modular structure could well be how they’ve planned to it.

That’s not the only possibility, though.

The article linked above mentioned the possbility of a 64-bit add-on. As the article put it, “The idea seems to be that people can buy a 32-bit module, and then add in the 64-bit processor.”

Hmmmm. There’s no need to have a separate CPU if you’re going to have x86-64, all you need is a few million transistors. Just stick them in the CPU and be done with it if that’s all you’re out to do.

Nor would there need to be a different version of Windows; the only change MS would have to make is to change the name of Windows for AMD64.

But what if that 64-bit add-on is an IA64 processor? Then all of this makes a great deal of sense, at least in Santa Clara.

Such a chip could knock out many of Opterons’ advantages and Itanium disadvantages. Such a chip could outperform Opterons in both 32- and 64-bit operations, and would let people move from 32-bit to 64-bit operations at their own pace with an add-on.

Elements for Windows would need to be an OS that could seemlessly handle two separate processors. a little different task than the 64-bit Windows we have today.

And how much would such a chip cost? Well, that would likely be a big problem, now wouldn’t it? 🙂 Certainly more than the average desktop user would pay.


Triple Play…

” onMouseOver=”window.status=’Talk to Ed!…’; return true” onMouseOut=”window.status=”; return true”>Ed