Newsmaker: AMD's man of the future

(continued from previous page)

What do you guys think about things like (IBM's) Cell processor--that notion of the one larger processor with many smaller cores that do the heavy lifting?
It has its place. Again, it gets back to the question (of) how well does it run across a diverse set of workloads?

For graphics processing, it's a great model, but not for all the applications you are running. Software development is also hard. I mean, look at what's happening with the PlayStation 3, for example. I would argue that a lot of the issues around that are the complexity of the software.

It's a hard programming model. If you do it right, it's got some big benefits. (One model we might look at is) potentially a lighter-weight co-processor for specific workloads (around) an architecture that runs well across the diverse set of workloads. If you look at the client or server workloads that we see, you can't optimize for one thing without (hurting) the performance of something else that would be a big issue to enough customers.

The end user has to have a good experience across the whole range of workloads. Some of those workloads and applications--if you were able to accelerate those without penalizing the others, you'd like that. So we kind of start off with the range they use to perform well. Then you could add in things--externally or, at some point, internally--to deal with specialized workloads, where enough of a time you are going to use the benefits from that extra cost.

What do you make of this debate over the proper way to bring computing to the rest of the world?
Somewhere between 15 percent and 20 percent of the world has a PC. Well, some of those (other) people will need a traditional PC, and there will also be something that merges a cell phone and today's notebook. There will be a lot of focus on power efficiency and cost in those devices, so part of that is also to enable different ways to sell these platforms.

One of the things that we've seen is that...inside emerging countries, the purchase price of the cell phone was an issue that you could fix with a kind of subscription model. There's a similar sort of thing we think would happen on the PC. If you tell somebody this is going to cost $250, and it's a one-time payment before you can get access to it, that's a harder discussion. But if you can make 25 payments of $10 apiece, spread over a period of time--and by the way, you're not going to be forced to pay that amount on regular basis, you'll pay it when you can afford it and the device will work when you cannot afford it.

You also have to deal with the protection of components. When you first get a lot of these devices, someone other than you is on the hook for the liability of the cost. You are in there, you pay for it over time, right, but there is a phenomena that can happen like stripping cars. If somebody steals it, tries to take the components out and sell the components as individual piece parts, for some period of time, there is a higher value in trying to do that than in protecting the device. So you need to think about how you protect the components of these systems to do as much as possible to prevent that sort of thing from happening.

Some participants at the conference have promoted a thin-client architecture for developing nations, which wouldn't require much processing power in each device. What's your take on that?
You just look at, for example, the rural areas, what goes on at the neighborhood school. In number of cases, it would be restricting to say that you have to have a networking infrastructure in place to be able to take the first step. We think there will be devices which would certainly have the ability to run as a thin client with the network attached. But they are still alone going to be standalone-capable computing devices.

I think here in the U.S. and in a lot of developed countries, we now take broadband and, in general, even wireless broadband pretty much for granted. That's not the case in number of these countries. In lot of these places power, for example, is unreliable. They don't even have AC power other than couple of hours a day.  

More Newsmakers

[sexlove2046]

dual-core

i like dual-core pc

[NRecob]

My Opeteron ROCKS

I love my Opteron 175-it leaves my old Intel P4 2.6HT in the DUST.

[sexlove2046]

dual-core

i like dual-core pc

[NRecob]

My Opeteron ROCKS

I love my Opteron 175-it leaves my old Intel P4 2.6HT in the DUST.

[baswwe]

AMD RULEZ

dual core quad core sex core

you name it they are the best

[baswwe]

AMD RULEZ

dual core quad core sex core

you name it they are the best

[NRecob]

INTEL=REAR VIEW MIRROR/ OPTERON=RULES

AMD IS KICKING INTEL'S A$$. NOBODY BUT N00BIES BUY INTEL ANYMORE.

OPTERON RULES!

[NRecob]

INTEL=REAR VIEW MIRROR/ OPTERON=RULES

AMD IS KICKING INTEL'S A$$. NOBODY BUT N00BIES BUY INTEL ANYMORE.

OPTERON RULES!

[Blito]

Stealing chips?

"You also have to deal with the protection of components. When you first get a lot of these devices, someone other than you is on the hook for the liability of the cost. You are in there, you pay for it over time, right, but there is a phenomena that can happen like stripping cars. If somebody steals it, tries to take the components out and sell the components as individual piece parts, for some period of time, there is a higher value in trying to do that than in protecting the device. So you need to think about how you protect the components of these systems to do as much as possible to prevent that sort of thing from happening."

I understand if they are selling it AMD should take a share of the profits but taking the chips out is another matter that isn't stealing other then breaking the AMD warrenty. They shouldn't create a total Orwellian Thin Client scenrio totally either; although it would be good in allot of other minor ways.

If AMD is going open source the specs on it's co-processors that could be a good thing for them against Intel.

[Blito]

Stealing chips?

"You also have to deal with the protection of components. When you first get a lot of these devices, someone other than you is on the hook for the liability of the cost. You are in there, you pay for it over time, right, but there is a phenomena that can happen like stripping cars. If somebody steals it, tries to take the components out and sell the components as individual piece parts, for some period of time, there is a higher value in trying to do that than in protecting the device. So you need to think about how you protect the components of these systems to do as much as possible to prevent that sort of thing from happening."

I understand if they are selling it AMD should take a share of the profits but taking the chips out is another matter that isn't stealing other then breaking the AMD warrenty. They shouldn't create a total Orwellian Thin Client scenrio totally either; although it would be good in allot of other minor ways.

If AMD is going open source the specs on it's co-processors that could be a good thing for them against Intel.

[ilover2]

Conroe is gonna getch ya

watch out slow mo

[ilover2]

Conroe is gonna getch ya

watch out slow mo