Slashdot Mirror


AMD Fusion To Add To x86 ISA

Giants2.0 writes "Ars Technica has a brief article detailing some of the prospects of AMD's attempt to fuse the CPU and GPU, including the fact that AMD's Fusion will modify the x86 ISA. From the article, 'To support CPU/GPU integration at either level of complexity (i.e. the modular core level or something deeper), AMD has already stated that they'll need to add a graphics-specific extension to the x86 ISA. Indeed, a future GPU-oriented ISA extension may form part of the reason for the company's recently announced "close to metal"TM (CTM) initiative.'"

53 of 270 comments (clear)

  1. Am I the only one? by man_of_mr_e · · Score: 4, Insightful

    Am I the only that thinks this is a bad idea? Either I change video cards more often than CPU's or CPU's more than graphics cards, but in either case I seldom want to upgrade both at the same time. Although I suppose I wouldn't mind a better GPU "for free" with my CPU, I suspect it won't be "for free".

    1. Re:Am I the only one? by r_jensen11 · · Score: 4, Informative

      I'm guessing that, as with integrated graphics, having (a) shared GPU/CPU(s) would allow having an additional video card. I seriously doubt they're going to remove the PCIe 16x slot from motherboards any time soon.

    2. Re:Am I the only one? by hawkbug · · Score: 4, Informative

      Yeah, I thought that same thing at first. However, I don't think we are the target market. I think Laptops and OEMs will be the market for this. Just imagine a mac-mini type computer from Dell or somebody. Onboard video has been around for ages, but if the board could be smaller since the gpu is on the cpu, then you'd save space and power so the machine could be smaller and theoretically cheaper.

    3. Re:Am I the only one? by Anonymous Coward · · Score: 2, Interesting

      Well that all depends on how much performance can be gained by the integration. I seem to remember this as a weak argument for why numeric co-processors shouldn't be
      integrated into the 486DX...

    4. Re:Am I the only one? by Rosco+P.+Coltrane · · Score: 2, Insightful

      Am I the only that thinks this is a bad idea? Either I change video cards more often than CPU's or CPU's more than graphics cards, but in either case I seldom want to upgrade both at the same time. Although I suppose I wouldn't mind a better GPU "for free" with my CPU, I suspect it won't be "for free".

      Look at it this way: nowadays you can get a computer with a video "card" onboard the motherboard, but nothing prevents you from disabling it and installing a separate video card. Most likely, that's what's gonna happen in this case. But remember, one of the advantage of merging the cpu and gpu is to get around the bus bottleneck, so presumable an embedded gpu may well blow any separate video card out of the water in terms of performance. Unless of course this is just a marketting stunt, or a consumer lock-in scheme, which is just as likely...

      --
      "A door is what a dog is perpetually on the wrong side of" - Ogden Nash
    5. Re:Am I the only one? by cnettel · · Score: 4, Insightful
      On the other hand, the real payoff of low latency won't surface if every operation means going through a driver, which only then realizes "oh, I have a single instruction for this thing, let's head back to the caller". This means that game writers will either still need to batch up complex operations, that the driver will then translate into batches of suitable instructions, or that we'll see games/applications with radically different codepaths. Any attempt to benefit optimally from the integrated approach will perform badly on a separate card, while code tuned to a separate card won't come close to harnessing the good points of an underpowered, but lower latency, local graphics implementation.

      It's almost like they would add L3 in a non-transparent manner, that is, expecting the developers to write the code moving suitable data into the cache and addressing that data in a radically different manner, while still also supporting the normal style of memory access, where you of course need to care about the cache, but not so explicitly. (The Cell's explicit local RAM for each unit, and the whole design of that beast, comes to mind. At least ALL PS3s will have one, but the expected target market for Fusion-only adaptations is much less clear cut.)

      And, yeah, this is quite like the situation almost ten years ago, when 3D cards were hot and new. Writing a pipeline to feed those cards was quite different from rolling your own hacked-up software rendered. (And with T&L and shaders, the move has been even greater.)

      But maybe then I'm just speculating a bit too much here. It would make sense that AMD is designing these instructions to fit into the existing driver model (or at least the DX10 one), so that you can get pretty good performance by just doing the relevant translation there.

    6. Re:Am I the only one? by drinkypoo · · Score: 4, Informative
      All they're doing is shifting the GPU (as well as the cost) to the CPU core from the motherboard.

      They're also eliminating all of the components between the CPU core and the GPU. In theory they could have a HT chip that handled all of the I/O and didn't even present a traditional system bus, if they felt they didn't need expansion slots. Thus you could eliminate the PCI/PCI-E bus and all the things needed to support it; at minimum however you are eliminating the bus between the North Bridge and the GPU and all that entails... which is a lot.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    7. Re:Am I the only one? by mrchaotica · · Score: 4, Interesting
      I seriously doubt they're going to remove the PCIe 16x slot from motherboards any time soon.

      What I'd like to see is for AMD to put the CPU and GPU on separate chips, but make them pin-compatible and attach them both to the hypertransport bus. How cool would it be to have a 4-socket motherboard where you could plug in 4 CPUs, 4 GPUs*, or anything in between?

      *Obviously if it were all GPUs it wouldn't be a general-purpose PC, but it would make one hell of a DSP or cluster node!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    8. Re:Am I the only one? by mrchaotica · · Score: 2, Insightful

      Shouldn't this kind of thing be the compiler or library writers' problem, not the application developers'?

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    9. Re:Am I the only one? by timeOday · · Score: 2, Informative
      in either case I seldom want to upgrade both at the same time.
      What if the new architecture's "graphics" pipelines aren't dedicated exclusively to graphics and can be used to speed up other tasks? Or if the total power consumption of the integrated component is 50% of separate components? Or if a non-upgradeable "PC on a chip" with no expansion bus offers great performance at 50% the cost of a traditional PC?
    10. Re:Am I the only one? by gripen40k · · Score: 4, Insightful

      From what I understand I think the parent is right. If you use OpenGL, you don't worry about pipelining or however else the computer actually 'makes' the graphics, you just code it. Buuuutt.... I guess you would need to compile two versions of the same thing and put it on the same game disk, or figure out some kind of neat system so that translations are done in real time with hardware (much faster than the soft approach).

      --
      Har?
    11. Re:Am I the only one? by ruiner13 · · Score: 4, Informative

      Dead on. Think of the power savings for laptops, not needing to have to use energy to drive a pci-e slot with a graphic chip that only gets replaced when the laptop does. It would also allow for really slick interfaces on smaller devices, such as tablets, pdas, etc. It would also have one hell of a bandwidth rate to the processor, including full speed access to the computer's RAM. I don't think they'd give it dedicated memory die to die size, but it sure would beat going over a pci-e bus like today's shared memory integrated chipsets.

      --

      today is spelling optional day.

    12. Re:Am I the only one? by Sparohok · · Score: 2, Insightful

      The history of computer architecture is a ceaseless march toward higher integration and higher generality. That is, what was once special purpose hardware in a seperate unit is now implemented in firmware as part of a more flexible, general purpose processor.

      This march is littered with those standing by the wayside saying things like, "Who needs floating point in the CPU? Leave it on a seperate chip!" or "I want to be able to upgrade my CPU without buying a new memory controller!" or "If you integrate sound on the motherboard, I'll just have to buy a seperate sound card."

      So, while I'm sure you're not the only one who thinks GPU integration is a bad idea, that doesn't mean it is a bad idea.

    13. Re:Am I the only one? by Alien+Being · · Score: 2, Insightful

      "Buuuutt.... I guess you would need to compile two versions of the same thing and put it on the same game disk, or figure out some kind of neat system so that translations are done in real time with hardware (much faster than the soft approach)."

      I don't think so. The application can be linked against a single graphics library. The GL just swaps some function pointers when special hardware is available.

    14. Re:Am I the only one? by obeythefist · · Score: 2, Interesting

      Remember the characteristics of performance GPUs at the moment - AMD's Fusion technologies are not aimed at performance gaming at all, they're squarely aimed at the imbedded/budget/mobile segments of the market.

      Just look at the memory speed of your average CPU (667MHz DDR2) and your average GPU (1GHz DDR3 is good).

      Now, hooking your GPU up to the main system memory takes away a huge chunk of your performance. Saves you a lot of money though. If you're not sure, go look at how overclocking video memory affects performance, just about any of your THG/Anandtech/Extremetech sites will tell you.

      This is just another method of doing your onboard graphics solution. It will perform much better than current integrated graphics solutions. But there's no way it can outperform a quad-SLI rig, even on paper.

      --
      I am government man, come from the government. The government has sent me. -- G.I.R.
    15. Re:Am I the only one? by rbanffy · · Score: 4, Insightful

      As added benefits:

      - With a public and standard ISA, you will have Linux-compatible drivers shortly

      - With a public and standard ISA, people will have a single standard to code against. Library support should be excellent.

      - While your über-FPUs/vector accelerators/stream processors (what GPUs are made of) are not GPU-ing something, they can accelerate SSL, physics processing and any other vector-friendly activity you may have. Playing Flash content, maybe.

      - GPUs are memory-hungry. The added memory bandwidth will benefit all software, not only graphics-intensive stuff.

      - There is nothing that precludes you from using a stand-alone GPU, provided you have the drivers. But your CPU will have a couple high performance units that can give it a hand. Think asymmetric SLI.

      We will see how well the idea performs by watching the Cell processor (a CPU with 8 "GPU"s attached) in the PS3. That's roughly the same idea.

      In the meantime, I bet it will work just fine.

    16. Re:Am I the only one? by man_of_mr_e · · Score: 2, Insightful

      Gamers aren't the only ones driving the market. You'll want a fast dual core processor for Vista, for instance. Software will always expand to fill all available CPU Cycles. I just see software becoming more powerful, not just games. Thinks like more AI in real-world apps, star trek level stuff.

    17. Re:Am I the only one? by 241comp · · Score: 2, Insightful

      How about the ability to have dual video cards within a laptop? The low-power on-cpu video driver for when you're just browsing the web or whatnot and the latest Nvidia/ATI pci-e power-hog for when you're gaming... think of the battery life you could have when reading your email at the airport without sacrificing the ability to play your favorite games at full res.

    18. Re:Am I the only one? by mrchaotica · · Score: 2, Interesting

      A couple of questions for you to consider:

      1. Which has more bandwidth, 16x PCIe or HyperTransport?
      2. What's stopping AMD from simply putting a memory controller that can talk to 1GHz DDR3 on these chips (remember, AMD CPUs have on-die memory controllers)?

      Also, keep in mind that we're talking about a technology in the early stages of development. The current performance of off-the-shelf hardware is irrelevant; the issue is whether the basic technology has the potential to be made to do it.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    19. Re:Am I the only one? by mrchaotica · · Score: 4, Insightful
      Maybe I'm just projecting, but what I think that you want, and many others out there want is simply a better bus, bridge, magic, glue or whatever you want to call it between the major parts of a computer.

      Hmm... you might be right. But an equally important aspect is that I want a socketed GPU and graphics memory, so that it would be modular just like the CPU and system memory.

      A combo CPU/GPU either only targets the very low end generic computer or a specialized graphics type of computer. With the failure of the other addons to computers, I don't see the advantage. Graphics simply don't matter in the server market.

      You're thinking too small. Modern GPUs don't just do graphics; they are becoming able to do just about any kind of very-parallel computations.

      For example, imagine a server of some kind that processes every packet it sends in the same way. Let's say it has 1000 connections, and that each one is handled by a separate thread. Now, imagine that the thread can somehow be implemented as a shader. Then, instead of processing 1 or 2 packets at a time (as on a single- or dual-core CPU), you can suddenly process (tens? hundreds?) of packets simultaneously! Even if the thing is clocked lower than a CPU, I'll betcha it'll still have better overall performance -- assuming you can make it work.

      Personally, I think there are quite a few problems like this, that could be parallel even though they aren't usually implemented that way now. I think it's a matter of how most programmers are used to traditional CPUs, and so don't think in a parallel way. I'm actually banking on this becoming a big deal in the future, which is why I'm taking a bunch of graphics, systems and HPC classes (I'm a CS student). And it had better do so, because otherwise computers are going to stop getting faster -- the whole reason everybody's so focused on multi core systems now is that they've hit a wall wrt. the laws of physics.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    20. Re:Am I the only one? by jhfry · · Score: 2, Insightful

      I have made a similar argument, I want a FPGA on the HT bus. A Fully Programmable Gate Array would allow software developers to create hardware "programs" to accelerate their products. For example, Photoshop and Premiere could re-program the FPGA to accelerate processor intensive tasks. Codecs could be implemented on the chip for realtime encoding (for example http://www3.elphel.com/en/products is a camera that does OGG Theora in a FFPGA in realtime at 640x480x90fps). And game writers could optimize any part of their applications they wish. Sure FPGA's are not as fast as a non-programmable processor, but they are infinately more flexable, and if it's sitting on the HT bus with direct access to system RAM, you would see some amazing uses. Accelerated encryption/decryption, email filtering and virus detection, or any other process that is sequential in nature and done repeatedly.

      --
      Sometimes the best solution is to stop wasting time looking for an easy solution.
  2. Yeah that's the future by Rosco+P.+Coltrane · · Score: 4, Funny

    ISA is definitely the future to interface a CPU and a GPU, but I keep hearing about this VLB technology that's even hotter!

    --
    "A door is what a dog is perpetually on the wrong side of" - Ogden Nash
  3. How long until a physics extension? by User+956 · · Score: 4, Insightful

    'To support CPU/GPU integration at either level of complexity (i.e. the modular core level or something deeper), AMD has already stated that they'll need to add a graphics-specific extension to the x86 ISA.

    x86 is a great multi-purpose, but the reason we're seeing greater and greater offload onto a GPU is because that's great at a specific task. So my question is, how long until we see widespread PPU (Physics processing unit) usage, and beyond that, a Physics extension to the x86 ISA? Or will we all just be computing on the grid at that point?

    --
    The theory of relativity doesn't work right in Arkansas.
    1. Re:How long until a physics extension? by Wesley+Felter · · Score: 2, Insightful

      So my question is, how long until we see widespread PPU (Physics processing unit) usage, and beyond that, a Physics extension to the x86 ISA?

      Never, since it looks like physics can efficiently run on GPUs now.

  4. Re:One unanswered question? by zpapasmurf · · Score: 2, Insightful

    no, but SLI isn't economical either. it's not the most bang for the buck, its the most bang.... period

  5. Re:One unanswered question? by Anonymous Coward · · Score: 5, Insightful

    Can it run Linux? OK JUST KIDDING!

    Why joke? It is an important question.

    All the current nvidia and ati graphics cards require proprietary, closed-source drivers.
    If the GPU is to be integrated into the CPU, either they will have to keep the new ISA a secret or we will finally start getting access to the information required to really write Free graphics drivers.

  6. Advantages? by Tainek · · Score: 3, Insightful

    A lot of people seem to be having issues working out why AMD is doing this

    people are forgetting that they are not always the target market for computers (this isnt aimed at you if you upgrade one more than the other)

    for example, what is easyer for your computer illiterate father to do, change one slot component, or install a graphics card , and a cpu.

    it also allows for even smaller form computers

    i will concede, that these gains are pretty small though, i cant see it being worth it

    1. Re:Advantages? by fatty+ding+dong · · Score: 3, Interesting
      people are forgetting that they are not always the target market for computers

      Until this was posted, I couldn't figure out the "why" to this problem. The "why" is indeed, pre-built home systems.

      Think about your average Joe that doesn't know a USB from USPS. He's not going to concern himself with more statistics than he has to when it comes to buying a computer. If he can get his CPU and his graphics rolled into one component at a lower cost than having them separate, he will without a thought. It doesn't even come down to ease of repair since most average users will have someone else repairing their system. It will simply come down to cost.

      I've had the same home built box for 4 years, I just upgrade as needed (and sometimes as wanted). Average pre-built buyer doesn't care for upgrading. As soon as it breaks: fix it. If it costs too much to fix it: replace it. The word "upgrade" isn't in an average computer purchaser's vocabulary. If the Fusion can last even a year and a half on average, that would be adequate given that most pre-built buyers are conditioned to buy a new box every 2 years give or take. For average computer buyers, it will work as long as AMD can keep the cost down. I will agree however, its definitely not practical for those of us who buy new video cards almost as often as we buy milk.

      --
      -Now I may be an idiot, but there is one thing I am not sir, and that, sir, is an idiot.
  7. Showing my age by WidescreenFreak · · Score: 5, Funny

    I guess I'm showing my age. As soon as I saw "ISA" I immediately thought, "Why the HELL are they thinking about bringing this back?

    :(

    --
    The Overrated mod is for reversing inappropriate, positive mods, not for voicing disagreement with a post.
    1. Re:Showing my age by njchick · · Score: 4, Funny

      It's not your age. It's just a problem of the current TLA namespace. Another reason to switch to XTLA (extended three letter acronyms).

  8. Hm, an ISA extension for 3D graphics... by wirelessbuzzers · · Score: 2, Funny

    ... maybe they should call it 3DNow or something?

    --
    I hereby place the above post in the public domain.
  9. What happened... by dduardo · · Score: 3, Insightful

    What happened to the RISC philosophy? Keep the hardware simple and let the compiler do the work.

    No, lets create 1000 more instructions for graphics, 1000 for physics and 1000 more just for the heck of it.

    1. Re:What happened... by forkazoo · · Score: 2, Informative
      What happened to the RISC philosophy?


      We decided we wanted cheap, fast hardware, and we decided the philosophy made more sense at the software level.
    2. Re:What happened... by Guy+Harris · · Score: 3, Insightful
      What the programmer sees may be CISC, but what happens inside is RISC.

      The article is discussing what the programmer sees, i.e. the instruction set architecture.

    3. Re:What happened... by Sj0 · · Score: 2, Informative

      That decrepit arcitecture is the fasteest consumer hardware platform in existance.

      --
      It's been a long time.
    4. Re:What happened... by forkazoo · · Score: 2, Interesting
      Uh... More likely you folks have decided you want to run DOS and Windows.
      Since both were (are) locked to the x86 ISA, it gave this decrepit architecture a reason to live.


      Personally, I have no particular ties to x86 or DOS or Windows. I wrote my previous post from an Ubuntu box, and I am writing this one from a PPC box. But, all that "decrepitness" that makes x86 unclean is actually pretty damned useful. The wacky instruction encoding is horrible to look at, but also means that you generally see better code density on x86 than you do on a more pure RISC architecture. RISC came at a time when instruction decoders were a really significant part of a CPU. Now, with increased transistor budgets, on a high performance CPU the decoder is a non-issue. Making the decoder simpler wouldn't get you any benefit, and it would reduce the effectiveness of your instruction bandwidth and instruction caches.

      I'm no x86 evangelist. My main personal server is an Alpha, I love my MIPS hardware and I even have a VAX. But, x86 hardware can't be beat for cheap speed. Not with anything currently out, anyhow. If somebody comes out with something that is elegant, cheap, and beats x86 for my typical workloads, I'll jump on board in a heart beat. :)
  10. Re:ISA? by MadEE · · Score: 4, Informative

    ISA = Instruction Set Architecture

  11. Nuclear power by erice · · Score: 2, Funny

    I'm sorry. I can't help it.

    Every time I see an article about AMD's "Fusion", I think
    "Everyone knows that the power consumption of modern cpu's has gotten out of hand. Still, you gotta give AMD credit for having the guts to propose the obvious solution: An on chip fusion reactor"

  12. Doesn't this imply open source compatibility? by macemoneta · · Score: 2, Interesting

    If the video uses a documented instruction set, doesn't this imply that AMD/ATI CPU/GPU chips will be open source compatible? Shouldn't that be all the information needed (from the GPU perspective) to create a 3D hardware accelerated driver?

    --

    Can You Say Linux? I Knew That You Could.

  13. it died back in the 90's by RelliK · · Score: 2, Insightful

    I guess I should clarify. RISC "philosophy" lives on, but practicality has long been dead. Modern CPUs have RISC microcode with a x86 -> RISC translator in front. The translator adds a bit of overhead and uses up some silicone, but on the other hand CISC instructions are smaller, so you can fit more of them in a given amount of L1/L2 cache.

    --
    ___
    If you think big enough, you'll never have to do it.
    1. Re:it died back in the 90's by serviscope_minor · · Score: 2, Insightful

      I guess I should clarify. RISC "philosophy" lives on, but practicality has long been dead. Modern CPUs have RISC microcode with a x86 -> RISC translator in front. The translator adds a bit of overhead and uses up some silicone, but on the other hand CISC instructions are smaller, so you can fit more of them in a given amount of L1/L2 cache.

      You are just plain wrong on many counts.

      RISC outsells CISC my a massive margin. Just look at the presence of PowerPC, MIPS and (the biggest of all) ARM in the embedded market. Comparing number of cores sold anually, RISC is the winner by a very wide margin.

      Dead is a funny description for something which sells far more units.

      Secondly, Intel keep the micro-ops in the L1 instruction cache (known as trace cache), so the CISC instruction set doesn't help there (it does for the L2 cache).

      And thirdly, its silicon. Rubber processors don't exist yet.

      --
      SJW n. One who posts facts.
  14. A super-FPU by thue · · Score: 3, Informative

    As described by Ars Technica, the new NVIDIA G80 generation of GPUs are actually collections of general stream processors, a type of FPU. The GPU functionality is then programmed in software. The article from Ars Technica points out that "These threads could do anything from graphics and physics calculations to medical imaging or data visualization.". I assume the ATI GPU is moving in the same direction.

    So what AMD is adding to x86-64 is probably not just a GPU, but a new powerful general purpose massively parallel FPU.

    1. Re:A super-FPU by Anonymous Coward · · Score: 4, Informative

      Yes. I've pointed this out every time that Fusion has been mentioned here: a GPU is parallel vector processor. The resources available for rendering games can just as easily be used to accelerate scientific applications, and integrating it into one die will reduce the power and cost requirements. Since the GPUs are already becoming more general-purpose for more sophisticated shader programs, it makes a lot of sense to utilize those same resources for other applications without depending on incompatible shader architectures or PCI-Express add-on cards. It also gives AMD something to do with future die space besides creating 32-core processors that will be largely underutilized by software. People should think of this as AMD taking SSE out back and and just say, "to hell with the amateur hour, we're going to have some monster fp power." The end result is that you'll also be able to have superawesome graphics in games, as well as efficient scientific simulations.

  15. AMD's Fusion by smoker2 · · Score: 3, Funny

    Now with 5 cores ! (and a seperate core for those tricky areas)

  16. Fusion and CUDA lead the way. by ravyne · · Score: 4, Interesting

    I've been following GPGPU stuff for awhile now, casually at first but much more closely now with the AMD/ATI merger and the release of nVidea's G80 architecture. Both of these represent the first big steps toward GPGPU technology (buzzword: stream computing) becoming reality.

    The initial approach I suspect from the Fusion effort will basically be an R600-based, entry-level GPU tacked onto the CPU die. I'd imagine that this would have 4-8 quads (GPU 4-wide SIMD functional unit) as standard. This would mostly be targetted at the IGP market for laptops and small and/or cheap desktops. Its likely that CTM will enable this additional horsepower to be used for general clculations, but its primary purpose will be to replace other IGP solutions.

    A little further out I see the new functional units being woven into the fabric of the CPU itself. This model likens closely to having many 128-bit-wide extended SSE units, likely to have automatic scheduling of SIMD tasks (eg - tell the CPU to multiply 2 large float arrays and the CPU balances the workload across the functional units automatically.) A software driver will be able to utilize these units as a GPU, but the focus is now much more on computation. It functions as a GPU for low-end users, and suppliments high-end users and gamers with discreete video cards by taking on additional calculations such as physics. Physics will benefit being on the system bus (even though PCIe x16 is relatively fast) because the latancy will be lower, and because the structures typically used to perform physics calculations reside in system memory.

    Even further out I see computers very much becoming small grid computers unto themselves, though software will take a long time to catch up to what the hardware will be capable of. I see nVidea's CUDA initiative as the first step in this direction - Provide a "sea of processors" view to the machine and allow tight integration into standard code withought placing the burden of balancing the workload onto the programmer (which nVidea's CUDA C compiler attempts to do.) nVidea's G80 architecture goes one further by migrating away from the vector-based architecture in favor of a scalar one - rather than 32 4-wide vector ALUs, they provide 128 scalar ALUs. Threading takes care of translating those n-wide calls into n seperate scalar calls. Most scientific code does not lend itself well to the vector model, though over the years it has been shoe-horned into vector-centric algorithms because it was neccesary to get addequate performance. Even graphics shaders are becoming less and less vector-centric, as nVidea research shows, because many effects (or portions there-of) are better suited to scalar code.

    Eventually, I think this model will grow such that the CPU will be replaced by, to coin a phrase, something called a CCU (Central Coordination Unit) who's only real responibility is to route instructions to the correct execution units. Execution units will vary by type and number from system to system depending on what chips/boards you've plugged into your CCU expansion bus. The CCU will accept both scalar and broad-stroke (vector) instructions such as "multiply the elements of this array by that array and store the results in this other array" which will be broken down into individual elements and assigned to available execution units.

    All of this IMHO of course.

  17. I like your solution by TubeSteak · · Score: 2, Interesting

    It neatly sidesteps the fact that high-end GPUs are massive compared to a CPU core

    Intel Core Duo CPU
    ATI X1800 GPU

    BUT, you'd also have to squeeze all the other microchips that are on a high-end graphics card board... I don't know if you'd be able to squish all that into a CPU sized area. And if you can't, you're just changing the form factor & moving the graphics card onto a faster bus.

    Anyone have a better idea how you can put quality graphics into a CPU?

    --
    [Fuck Beta]
    o0t!
    1. Re:I like your solution by mabinogi · · Score: 4, Insightful

      Why don't you ask AMD, as they've apparently already considered it, or they wouldn't be talking about putting both the CPU and the GPU in the same package.

      Without knowing anything about it, it would seem that if CPU+GPU in the same package is possible, then CPU + GPU in two separate CPU sized packages would be possible.

      --
      Advanced users are users too!
  18. Forget OpenGL/Direct3D... by Svartalf · · Score: 2, Informative

    Most people associate these with their fixed functionality paths and the coding for the same.

    That'd be right for the older games or the older hardware.

    It'd not be right for the new hardware or the new games...

    The new GPUs use programmable vertex and fragment shaders and the fixed functionality paths go
    through an emulation of those paths in GLSL or HLSL. There's not much left that
    isn't merely a simplified computer like a DSP is for signal processing- this is merely one that
    is designed for graphics and similar operations instead.

    The new games use their own shaders, etc. which is why GLSL is such a big deal and a tool to migrate
    HLSL over is as much of one.

    Who can say for certain that this doesn't make sense? I'm not going to venture a yes or no- because
    I can see where they could pull it clean off and I can see some where it could let them fall flat on
    their face.

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
  19. Is the real goal just bundling? by tap · · Score: 3, Interesting

    It used to be that CPUs didn't come with floating point units. You had to buy a 287 or 387 to go with your 286 or 386, and they weren't cheap either. I think we paid $400 for a 20 MHz 387 back in the early 90s. Around the end of the 386s' use in desktops, competitors to Intel (Weitek, Cyrix, some others I think) had produced 387 compatible chips that were faster and cheaper than Intel's. For the 486, Intel decided to integrate the floating point unit, which made it pretty much impossible to buy someone else's chip. Sure there were technical merits to that, but I'm sure that fact that it killed any possible competition in the FPU market wasn't lost on Intel's execs.

    Trying to bundle products is nothing new. A company that makes a whole package doesn't like it when parts of the package can be bought from other companies. Instead of just competing for the whole package (and the few companies who can provide that), they need to compete for each individual part, and every company that can make any one of those parts. If AMD puts the GPU in the CPU, then it's pretty hard for nvidia get OEM's to include their GPU. Nvidia will have to build a CPU that's as good as AMD's, and that's not going to happen any time soon.

    1. Re:Is the real goal just bundling? by Prof.Phreak · · Score: 2, Insightful

      I can imagine the real goal being DRM. With everything on the CPU, making some instructions priviledged, they can force any program that wants to manipulate (decode?) video at a ``fast'' rate to call the OS to perform the decoding---allowing the OS to ensure the video has valid signatures before it proceeds.

      Sure folks would still be able to use libraries that run on the CPU, but if those are inefficient/slow compared to the specialized instructions... then who knows.

      Just being paranoid...

      --

      "If anything can go wrong, it will." - Murphy

  20. nforce? anyone? by sam0vi · · Score: 2, Funny

    To me this sounds like some nforce-Mega-integration thing. I dont like it because when i think about it i think about: Drivers?! Maybe for the PS$ or something

    --
    When my Karma level reaches 0 I feel in piece with the Universe
  21. Aren't we forgetting something? by Driving+Vertigo · · Score: 3, Interesting

    I think people are forgetting the idea that the integrated "GPU" is going to be more like a programmable DSP than an actual graphics accelerator. We know the CPU is wonderful at computing integer math, but it's always been lacking in floating point. The modern GPU has become a floating point monster. The integration of this new element, including instructions to utilize it in native "stream processing" will likely cause a small leap forward in computing power. So, please, don't think of this as a replacement to your video card, put more like an evolution in the area of math-coprocessors.

    --
    To a noob, root is like a gay bar...and he's wearing assless chaps
  22. Instruction Set Architecture by dunc78 · · Score: 2, Informative

    I believe it stands for Instruction Set Architecture, with x86 being an example of an ISA, not the old bus of which you are thinking.