Slashdot Mirror


Nvidia Working on a CPU+GPU Combo

Max Romantschuk writes "Nvidia is apparently working on an x86 CPU with integrated graphics. The target market seems to be OEMs, but what other prospects could a solution like this have? Given recent development with projects like Folding@Home's GPU client you can't help but wonder about the possibilities of a CPU with an integrated GPU. Things like video encoding and decoding, audio processing and other applications could benefit a lot from a low latency CPU+GPU combo. What if you could put multiple chips like these in one machine? With AMD+ATI and Intel's own integrated graphics, will basic GPU functionality be integrated in all CPU's eventually? Will dedicated graphics cards become a niche product for enthusiasts and pros, like audio cards already largely have?" The article is from the Inquirer, so a dash of salt might make this more palatable.

50 of 178 comments (clear)

  1. Heard This One Before by eldavojohn · · Score: 4, Interesting
    Sounds like Nvidia is just firing back at the ATI-AMD claim from two months ago. Oh, you say that you're integrating GPUs and CPUs? "Well, we can say that too!"

    What I don't understand is that I thought GPUs were made to offload a lot of graphics computations from the CPU. So why are we merging them again? Isn't a GPU supposed to be an auxillary CPU only for graphics? I'm so confused.

    What I'm not confused about is the sentence from the above article:
    DAAMIT engineers will be looking to shift to 65 nanometre if not even to 45 nanometre to make such a complex chip as a CPU/GPU possible.
    Oh, I've worked with my fair share of DAAMIT engineers. They're the ones that go, "Yeah, it's pretty good but ... DAAMIT, we just need more power!"
    --
    My work here is dung.
    1. Re:Heard This One Before by everphilski · · Score: 4, Interesting

      What I don't understand is that I thought GPUs were made to offload a lot of graphics computations from the CPU. So why are we merging them again?

      a really, really fast pipe. It is a lot quicker to push stuff from CPU->GPU when they are on the same piece of silicon, versus the PCIe or AGP bus. Speed is what matters, it doesn't look like they are moving the load one way or another (although moving some load from CPU->GPU for vector based stuff would be cool if they had a general purpose toolkit, which I'd imagine one of these three companies will think about).

    2. Re:Heard This One Before by LWATCDR · · Score: 3, Insightful

      Well think of it like floating point.
      At one time floating point was done by software it still is one some cpus.
      Then floating point co-processors became available. For some applications you really needed to speed up floating point so it was worth shelling out the big bucks for a chip to speed it up. This is very similar to what we have now with graphics cards.
      Finally CPUs had floating point units put right on the die. Later DSP like instructions where added to CPUs.

      We are getting to the point where 3d graphics are mandatory. Tying it closer to the CPU is now a logical choice.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    3. Re:Heard This One Before by Ryan+Amos · · Score: 2, Interesting

      It is; but if you combine them on the same die with a large shared cache and the on-chip memory controller... you can see where I'm going with this. Think of it as a separate CPU, just printed on the same silicon wafer. That means you only need 1 fan to cool it and you can lose a lot of heat producing power management circuitry on the video card.

      Obviously this is not going to be ideal for high end gaming rigs; but it will improve the quality of integrated video chipsets on lower end and even mid range PCs.

    4. Re:Heard This One Before by Ironsides · · Score: 2, Insightful

      Then why not just have some connections that come straight out of the CPU and go directly to a graphics card, bypassing any bus entirely?

      --
      Fly me to the moon Let me sing among those stars Let me see what spring is like On jupiter and mars
    5. Re:Heard This One Before by drinkypoo · · Score: 3, Interesting

      ATI/AMD is working on that right now. I think it comes after the next rev of hypertransport.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    6. Re:Heard This One Before by purpledinoz · · Score: 4, Interesting

      It seems like this type of product would be marketed towards the budget segment, which really doesn't care about graphics performance. However, the huge advantage of having a GPU on the same silicon as the CPU would be a big boost in performance. The low cost advantage has already been attained with the integrated graphics chipsets (like nForce). So that would mean this might be marketed towards the high-performance crowd.

      But I highly doubt that nVidia will be able to get a CPU out that out-performs an Intel or AMD, which the high-performance junkies would want. Intel and AMD put a HUGE amount of money into research, development, and fabrication to attain their performance. This is going to be interesting to watch. Hopefully nVidia doesn't dig themselves into a hole with this attempt.

    7. Re:Heard This One Before by TheRaven64 · · Score: 5, Informative
      It's not just floating point. Originally, CPUs did integer ops and comparisons/branches. Some of the things that were external chips and are now found on (some) CPU dies include:
      1. Memory Management Units. Even in microcomputers there are some (old m68k machines) that have an off-chip MMU (and some, like the 8086 that just don't have one).
      2. Floating Point Units. The 80486 was the first x86 chip to put one of these on-die.
      3. SIMD units. Formerly only found in high-end machines as dedicated chips, now on a lot of CPUs.
      4. DSPs. Again, formerly dedicated hardware, now found on-die in a few of TI's ARM-based cores.
      A GPU these days is very programmable. It's basically a highly parallel stream processor. Integrating it onto the CPU makes a lot of sense.
      --
      I am TheRaven on Soylent News
    8. Re:Heard This One Before by Do+You+Smell+That · · Score: 3, Informative
      What I don't understand is that I thought GPUs were made to offload a lot of graphics computations from the CPU. So why are we merging them again? Isn't a GPU supposed to be an auxillary CPU only for graphics? I'm so confused.
      You're partially right. GPUs were made to execute the algorithms developed for graphically-intensive programs directly in silicon... thus avoiding the need to run compiled code within an operating system, which entails LOTS of overhead. Being able to do this directly on dedicated hardware (with entirely different processor designs optimized for graphical computations)makes it possible to execute ALOT more calculations per second. You can really see the difference if you, for instance, use DirectX on two nearly identical video cards; one with hardware based DirectX, the other with it running as software.

      Moving it right up next to the CPU will allow the data to flow between the two alot faster than currently where it has to go over a bus... they can finally get rid of the bottlenecks that have been around since the two were seperated.
      --
      I'm not good at making signatures...
    9. Re:Heard This One Before by arth1 · · Score: 4, Interesting
      At one time floating point was done by software it still is one some cpus.
      Then floating point co-processors became available. For some applications you really needed to speed up floating point so it was worth shelling out the big bucks for a chip to speed it up.

      Then people started using floats for the convenience, not because the accuracy was needed, and performance suffered greatly as a result. Granted, there are a lot of situations where accuracy is needed in 3D, but many of the calculations that are done could be better done in integer math and table lookups.
      Does it often matter whether a pixel has position (542,396) or (542.0518434,395.97862456)?
      Using a lookup table of twice the resolution (or two tables where there's non-square pixels) will give you enough precision for pixel-perfect placement, and can quite often speed up things remarkably. Alas, this, and many other techniques have been mostly forgotten, and it's easier to leave it to the MMU or graphics card, even if you compute the same unneccessary calculations and conversions a million times.

      Fast MMUs, CPU extensions and 3D graphics routines are good, but I'm not too sure they're always used correctly. Does a new game that's fifty times as graphically advanced as a game from six years ago really need a thousand times the processing power, or is it just easier to throw hardware at a problem?
    10. Re:Heard This One Before by NerveGas · · Score: 4, Interesting

      I don't think that the CPU->GPU pipe is any limitation. Going from AGP 4x->8X gave very little speed benefit, and on PCI-E connections, you have to go from the normal 16x down to a 4x before you see any slowdown.

      Memory size and bandwidth are the usual limitations. Remember that if you want 2x AA, you double your memory usage, and if you want 4x AA, you quadruple it. So, that game that needed 128 megs on the video card, with 4x AA, can suddenly need 512.

      steve

      --
      Oh, you're not stuck, you're just unable to let go of the onion rings.
    11. Re:Heard This One Before by LWATCDR · · Score: 4, Interesting

      Exactly.
      I was using floating point as an example.
      I don't know if Nvidia can pull this off without a partner. Too build a really good X86 core isn't easy. I wonder if they may not do a PPC or Arm core instead. That could make nVidia a big player in the cell phone and mobile video market. At some point there will be portable HD-DVD players.

      My crystal ball says.
      AMD will produce these products.
      1. A low end CPU it integrated GPU for the Vista market. This will be a nice inexpensive option for home and corporate users. It might also end up in some set-top boxes. This will the next generation Geode.
      2 A family of medium and high end video products that use Hyperchannel to interface with Opteron and Athlon64 line.

      Intel will
      Adopt Hyperchannel or reinvent it. Once we hit four cores Intel will hit a front bus wall.
      Intel will produce a replacement for the Celeron that is Duo2Core with integrated graphics on one die. This is to compete with AMD new integrated solution.
      Intel will not go in to the high end graphics line.

      nVidia will fail to produce an X86+GPU to compete with AMD and Intel.
      nVidia produces an integrated ARM+GPU and dominates the embedded market. Soon every cellphone and media player has an nVidia chipset at it's heart. ARM and nVidia merge.

      Of course I am just making all this up but so what, electrons are cheap.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    12. Re:Heard This One Before by LWATCDR · · Score: 5, Informative

      I am an old school programmer so I tend to use ints a lot. The sad truth if that float using SSE are as fast and sometimes faster than the old tricks we used to avoid floats!
      Yes we live in an upside down world where floats are faster than ints some times.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    13. Re:Heard This One Before by daVinci1980 · · Score: 2, Informative
      Does it often matter whether a pixel has position (542,396) or (542.0518434,395.97862456)?

      Yes. It absolutely matters. It makes a huge difference in image quality.

      It matters when we go to sample textures, it matters when we enable AA, it matters.
      --
      I currently have no clever signature witicism to add here.
    14. Re:Heard This One Before by Ironsides · · Score: 4, Insightful

      And, of course, the reason number one: you get a guaranteed GPU sale for each CPU sale - goodbye pesky competition ;).

      And vice versa. This might work where someone wants an embeded GPU for low to medium end graphics. However, I doubt gamers would like the idea of having to purchase a new CPU evertime a new GPU comes out and vice versa.

      There's something to be said for physically discrete components.

      --
      Fly me to the moon Let me sing among those stars Let me see what spring is like On jupiter and mars
    15. Re:Heard This One Before by nine-times · · Score: 2, Interesting

      What I don't understand is that I thought GPUs were made to offload a lot of graphics computations from the CPU. So why are we merging them again? Isn't a GPU supposed to be an auxillary CPU only for graphics? I'm so confused.

      You've already gotten some good answers here, but I'll throw in something that I haven't seen anyone else mention explicitly: GPUs aren't only being used for 3D animation anymore. GPUs started because, in order to make graphics for games better, you needed a specialized processor to handle the 3D calculations. However, GPUs have become, in some ways, more complex and powerful than the CPU, and as that has happened, other uses have been found for all that power. turns out that there are lots of mathematical transformations that are more efficient on the specialized graphics processors, including audio/video processing and some data analysis. Some clever programmers have already started offloading some of their complex calculations from the CPU to the GPU.

      This has lead many people to wonder, why don't we bring some of the GPU advancements back to the CPU somehow, so that we aren't swapping data back and forth between the CPU and GPU, the system RAM and video RAM? Apparently, it's not a stupid question.

    16. Re:Heard This One Before by FlyingGuy · · Score: 2, Insightful

      As other have replied its all about the bus speed. The amount of time it takes to move data from chip to chip can insert enormous overhead.

      Think back a little to the DEC Alpha. Now the ALPHA chip in and of itself was not really that remarkable. What was so VERY remarkable about the Alpha system was its bus switching. It was blazingly fast and could handle monster amounts of data from main memory to CPU, GPU, etc. The reason ( mostly ) that its now sitting in HP's vault is that the bus switch was/is really expensive to manufacture.

      So the way you do this without haveing to build this very expensice bus architecture is to just put the GPU on the die with the CPU. Everything runs at the internal speed of the processor and its fairly inexpensive, comparatively, to build.

      --
      Hey KID! Yeah you, get the fuck off my lawn!
    17. Re:Heard This One Before by arth1 · · Score: 2, Informative
      Yes. It absolutely matters. It makes a huge difference in image quality.

      No, it doesn't. Note that I said pixel, not coordinate.
      The coordinates should be as accurate as possible, but having a pixel more accurate than twice the resolution of the display serves very little purpose.
    18. Re:Heard This One Before by stevenm86 · · Score: 4, Informative

      That's sort of the point of building them on the same die. You can't just run a wire to it, as it would be quite slow. Wires tend to have parasitic inductances and capacitances, so the setup and hold times on the lines would be too large to provide a benefit.

    19. Re:Heard This One Before by julesh · · Score: 3, Interesting

      Memory size and bandwidth are the usual limitations. Remember that if you want 2x AA, you double your memory usage, and if you want 4x AA, you quadruple it. So, that game that needed 128 megs on the video card, with 4x AA, can suddenly need 512.

      Of course with the GPU integrated into the CPU you wouldn't need card-based RAM at all. You'd process your video on system RAM, and it would be as fast as the GPU accessing its own RAM at the moment is (not shit like shared-memory video cards are at the moment). This results in flexibility: if you're only using 128MB of RAM for your graphics, you can reuse the other 384MB as additional system RAM.

    20. Re:Heard This One Before by Intron · · Score: 3, Informative

      Typically, unimplemented instructions cause an exception. The operation can then be emulated in software.

      --
      Intron: the portion of DNA which expresses nothing useful.
    21. Re:Heard This One Before by joto · · Score: 3, Informative
      There are a couple of strategies:
      1. Write a specialized program that will only run at a single computer, the one the programmer owns, as everything is specialized and optimized for his/her hardware. If other people needs to run the program, write a new one, or at the very least use some other compiler options.
      2. Don't use non-portable features. Always go for the lowest common denominator.
      3. Manually testing for existence of coprocessor at each FPU instruction, branch to emulator if FPU doesn't exist.
      4. Same as above, but tests are inserted automatically by the compiler.
      5. Test for existence of coprocessor at start of program execution. If FPU doesn't exist, dynamically replace all FPU instructions with branches to emulator routines
      6. Same as above, but done automatically by the OS program loader
      7. Make it mandatory for CPUs to: either support the FPU instructions (with a coprocessor if necessary); or to issue some sort of trap/interrupt that can be used by software such as the OS kernel/libc to use an emulator routine instead.

      I believe the last option (option 7) is what x86/87 CPU/FPU combo actually used. That's why there is a coprocessor-prefix in front of the FPU instructions. They are not just unused opcodes.

      Option 5 (and sometimes even 3) is commonly used for MMX/3dNOW/SSE/SSE2/SSE3/whatever instructions.

      Unless they *really* need nonportable features, most programmers tend to go with option 2.

    22. Re:Heard This One Before by MojoStan · · Score: 2, Informative
      ... if you combine them on the same die with a large shared cache and the on-chip memory controller... you can see where I'm going with this. Think of it as a separate CPU, just printed on the same silicon wafer. That means you only need 1 fan to cool it and you can lose a lot of heat producing power management circuitry on the video card.

      Obviously this is not going to be ideal for high end gaming rigs; but it will improve the quality of integrated video chipsets on lower end and even mid range PCs.

      Do you remember how Intel tried to do this with their (code name) Timna processor in 2000? Timna was supposed to be a low cost solution that integrated a CPU, GPU, and memory controller on the same silicon wafer. The CPU was a Celeron CPU (Pentium III based), the GPU was based on Intel's new i740, and the memory controller used RAMBUS (yes, RAMBUS) memory. At the same time, Intel was also developing the first chipset with integrated graphics (i810 chipset) and the first RAMBUS chipset (i820 chipset). RAMBUS was supposed to be the successor to PC100 SDRAM.

      When Timna was initially finished, RAMBUS was still so expensive that Timna's release had to be delayed so that a (PC100-to-RAMBUS) memory translator could be added. Those of us who followed chipsets back then know how badly RAMBUS and memory translators bombed. The integrated RAMBUS memory controller had to be the biggest reason Timna was cancelled. This might also be a reason Intel doesn't integrate a memory controller onto their current CPUs.

      Interestingly, Timna was the first project of Intel's new Israeli design team. Not a great start, but their second project was pretty darned good (Pentium M/Centrino).

      --
      TO START
      PRESS ANY KEY

      Where's the 'ANY' key? I see Esk, Kitarl, and Pig-Up...

    23. Re:Heard This One Before by 644bd346996 · · Score: 3, Informative

      Having the GPU on the same chip or die as the CPU would reduce the latency by several orders of magnitude and allow a much higher clock for the bus between the two. The memory access could also be improved dramatically, depending on how it was implemented.

      I think the first example of this integration we see will use the HyperTransport bus and a single package with CPU and GPU on different dies, though fabbed on the same process. This could be done with an existing AMD socket and motherboard.

      Before this happens, though, I think we will see graphics cards on HTX slots. For those who do not know, HTX slots were introduced in a recent revision of the HyperTransport standard. They allow an add-in card to communicate with the CPU with much lower latency and higher bandwidth than PCIe, and no controller in between. The add-in card could even have another CPU on it, and the performance would be comparable to current AMD SMP systems. A GPU on an HTX card could have its own RAM, and be able to access system RAM much faster than PCIe allows. The neat thing is that with HT, the CPU would probably be able to use the graphics RAM as though it were system RAM.

      Note that Nvidia is a member of the HyperTransport Consortium due to their chipset business, and they could easily have HTX cards in their labs right now.

    24. Re:Heard This One Before by daVinci1980 · · Score: 2, Informative


      You'd be mistaken. See the slide on Texture Mapping.

      Perspective divide is performed before texture sampling. This is necessary to get proper texture step sizes, for correct sampling of the texture onto the pixel.

      Fractional pixel locations are also used in antialiasing.

      --
      I currently have no clever signature witicism to add here.
    25. Re:Heard This One Before by Doctor+Memory · · Score: 2, Interesting
      But I highly doubt that nVidia will be able to get a CPU out that out-performs an Intel or AMD
      Maybe they don't have to. If they can just make something that can accelerate MMX/3D Now (sort of a graphics pre-processor) and plug that into a Socket F slot, it'd be like a two-stage accelerator: first accelerate the calculations that produce the graphics, then accelerate the display. Maybe they could find a way to do a micro-op translation of MMX instructions into something more RISC-like, and run them on a RISC core.

      At least, I hope it's something like that, because I agree with PP: nVidia doesn't have much of a chance to beat both Intel and AMD at the x86 game.
      --
      Just junk food for thought...
  2. nVidia don't have a good chance with this. by purpledinoz · · Score: 2, Interesting

    AMD and Intel have their own fabs that are at the leading edge of semiconductor technology. I highly doubt that nVidia will open up a fab for their chips. But who knows, IBM may produce their chips for them.

    I think the better option would be to have a graphics chip fit into a Socket 939 on a dual socket motherboard, with an AMD chip. It will have a high-speed link through hyper-transport, and would act just like a co-processor. I'm no chip designer, so I have no idea what the pros/cons of this are, or if it's even possible.

  3. With integration.. by Hangin10 · · Score: 3, Interesting

    With this integration, does that mean a standard for 3-d? No more Nvidia/ATI drivers. The OSDEV guys would love this if it came to that. But how would this integration work? A co-processor space like MIPS? If so, does that mean that graphics calculations have somewhat been moved back to the CPU? And what about the actual workings itself, I'm guessing the actual registers would still be memory mapped in someway (or I/O ports for x86, whatever).

    I'm thinking way too much. It did alleviate boredom for about a minute though...

  4. Out of their league? by Salvance · · Score: 4, Insightful

    Unless Nvidia is partnering with Intel to release this chip, I think they're getting too far out of their confort zone to be successful. Sure, a dual or even quad core chip with half of the cores handling graphics would be great, but can Nvidia deliver? I doubt it ... look how many companies have gone down the tubes after spending millions/billions after trying to make an x86 compatible chip, let alone trying to integrate top end graphics as well.

    Nvidia is a fantastic graphics card company - they should continue to innovate focus on what they're good at rather than try to play follow the leader in an arena they know nothing about.

    --
    Crack - Free with every butt and set of boobs
    1. Re:Out of their league? by TheRaven64 · · Score: 4, Insightful

      The thing is, it doesn't need to be a very good x86 chip. Something like a VIA C7 is enough for most uses, if coupled with a reasonable GPU. I can imagine something like this being very popular in the sub-notebook (which used to mean smaller-than-letter-paper but now means not-as-fat-as-our-other-products) arena where power usage is king. If the CPU and GPU are on the same die then this gives some serious potential for good power management, especially if the memory controller is also on-die. This makes for very simple motherboard designs (and simple = cheap), so it could be very popular.

      --
      I am TheRaven on Soylent News
  5. I smell a pattern by doti · · Score: 2, Interesting

    There seems to be a cycle of integrating and decoupling things.
    We had separated math co-processors, that later were integrated in the CPU.
    Then the separated GPU, which will soon be integrated back too.

    --
    factor 966971: 966971
  6. Math co-processors, anyone? by cplusplus · · Score: 4, Insightful

    GPUs are going the way of the math co-processor. I think it's inevitable.

    --
    "False hope is why we'll never run out of natural resources!" - Lewis Black
  7. patents by chipace · · Score: 2, Insightful

    It's quite clear that the AMD-ATI merger was to aquire the IP and expertise necessary to integrate gpu core(s) on the same die as cpu core(s). Nvidia does not have to actually market a design, but rather patent some key concepts, and this could provide revenue or protection.

    I would very much doubt that they could compete with AMD and Intel who have already patented many x86 cpu concepts.

    It's a shame that Intel has decided not to buy nvidia, and go it alone with it's own design staff.

  8. Thank MicroSoft by powerlord · · Score: 5, Interesting

    Okay, I admit, I haven't RTFA yet, but if GPUs do get folded back into CPUs, I think we need to thank MS.

    No. ... Seriously. Think for a minute.

    The major driving force right now in GPU development and purchase are games.

    The major factor that they have to contend with is DirectX.

    As of DirectXv10. A card either IS, or IS NOT compliant. None of this "We are 67.3% compliant".

    This provides a known target that can be reached. I wouldn't be surprised if the DirectX10 (video) featureset becomes synonymous with 'VGA Graphics' given enough time.

    Yeah, sure, MS will come out with DX11, and those CPUs won't be compatible, but so what?, If you upgrade your CPU and GPU regularly anyway to maintain the 'killer rig', why not just upgrade them together? :)

    --
    This space for rent. All reasonable inquiries will be entertained at proprietors discretion.
  9. A cyclic process? by Kadin2048 · · Score: 4, Insightful

    A while ago -- and maybe it was in the Slashdot discussion about ATI, I'm not sure -- somebody described a cycle in computer design, where various components are built-in monolithically, then broken out as separate components, and then swallowed back up into monolithic designs again.

    Graphics chips seem to have done this cycle at least once; perhaps now we're just looking at the next stage in the cycle? We've had graphics as a separate component from the processor for a while, perhaps the next stage in the cycle is for them to combine together into a G/CPU, to take advantage of the design gains in general-purpose processors.

    Then at some point down the road, the GPU (or more likely, various GPU-like functional units) might get separated back out onto their own silicon, as more application-specific processors become advantageous once again.

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    1. Re:A cyclic process? by shizzle · · Score: 5, Informative
      Yup, the idea is pushing 30 years old now, and came out of the earliest work on graphics processors. The term "wheel of reincarnation" came from "On the Design of Display Processors", T.H. Myer and I. E. Sutherland, Communications of the ACM, Vol 11, No. 6, June 1968.

      http://www.cap-lore.com/Hardware/Wheel.html

    2. Re:A cyclic process? by levork · · Score: 4, Informative

      This is known as the wheel of reincarnation, and has come up several times in the last forty years of graphics hardware.

    3. Re:A cyclic process? by Rockinsockindune · · Score: 2, Funny

      Ohh... do you think that I could get a trademark on "G/CPU" and then try and auction it off to the two compaines?

      --
      I abuse commas, I cannot help myself.
  10. Pointless without documentation. by sudog · · Score: 3, Insightful

    Why is everyone getting excited about this? Now we're going to have a CPU that's only partially documented, and we lose even moreso to closed-source blobs.

    This isn't a good thing unless they also release documentation for it!

  11. Just my preference . . . by Orange+Crush · · Score: 3, Funny
    The article is from the Inquirer, so a dash of salt might make this more palatable.

    I prefer my articles with a dash of accuracy.

  12. Niche market? by gstoddart · · Score: 3, Insightful
    Will dedicated graphics cards become a niche product for enthusiasts and pros, like audio cards already largely have?

    Haven't they already???

    The vast majority of machines (at least, from my experience, which could not be broad enough) seem to be shipping with integrated graphics on the motherboard. Certainly, my last 3 computers have had this.

    Granted, I buy on the trailing edge since I don't need gamer performance, but I kind of thought most consumer machines were no longer using a separate graphics card.

    Anyone have any meaningful statistics as opposed to my purely anecdotal observations?
    --
    Lost at C:>. Found at C.
    1. Re:Niche market? by gbjbaanb · · Score: 2, Insightful

      Its hardly a niche market - every server wants onboard graphics, mainly because they don't need to be superpowerful. I imagine this is similar - a low-powered CPU on the same chipset as the graphics chip (and no doubt the network chip) would make making motherboards a bit cheaper, or give them more capabilities that they currently have to have managed with software installed as a driver.

      I really doubt the CPU part is going to compete with the latest super-quadcore chips from AMD or Intel, so no-one will use it for a mainstream computer. Possibly it'd have a market for embedded products but I thought they were already well catered for.

  13. It's a logical extension of the NVidia NForce line by Animats · · Score: 4, Interesting

    I've been expecting this for a while, ever since the transistor count of the GPU passed that of the CPU. Actually, I thought it would happen sooner. It's certainly time. Putting more transistors into a single CPU doesn't help any more, which is why we now have "multicore" machines. So it's time to put more of the computer into a single part.

    NVidia already makes the nForce line, the "everything but the CPU" part, with graphics, Ethernet, disk interface, etc. If they stick a CPU in there, they have a whole computer.

    Chip designers can license x86 implementations; they don't have to be redesigned from scratch. This isn't going to be a tough job for NVidia.

    What we're headed for is the one-chip "value PC", the one that sits on every corporate desk. That's where the best price/performance is.

  14. Re:Should Slashdot really insult other news outlet by vondo · · Score: 4, Insightful

    The Inquirer is more of a rumor site than a news site. They have a pretty good track record for their rumors, but they don't have people on record backing this one up.

    What NVidia eventually does may not bear much resemblance to the story.

  15. Jen-Hsun Huang: A True Asskicker by DeathPenguin · · Score: 2, Informative

    When I saw this headline I immediately thought of this article, an interview with Jen-Hsun Huang (CEO: nVidia) by Wired dated July '02. In it, the intention of overthrowing Intel is made quite clear, and ironically enough they even mention the speculation from a time when it was rumored that nVidia and AMD would merge.

    It's actually a very good article for those interested in nVidia's history and Huang's mentality. Paul Otellini ought to be afraid. Very afraid.

  16. Re:It's a logical extension of the NVidia NForce l by Doctor+Faustus · · Score: 2, Interesting

    do you really want to take away system ram for video ram?
    If using larger chips means I can get 2GB combined RAM for the price of 1GB system RAM and 256MB video RAM? Absolutely.

  17. Re:Why multiprocessor units suddenly most efficien by SillyNickName4me · · Score: 2, Informative

    Why are the multiprocessor units suddenly so popular, relative to why e.g. the Voodoo graphics cards failed? I remember them being ridiculed and ending up in the performance backwaters through their 2-4-8(-16) multiprocessor cards, but it seems that there are engineering reasons why multiple processors are now suddenly coming into favour, or?

    multiple processors (CPU, GPU or otherwise) are a way to add more 'cycles' based on current technology. This has the advantage of being able to get more out of your current designs and manufacturing technology, but comes at the cost of increased complexity in both the supporting hardware, and in software.

    Getting a single core implementation faster is always the more efficient way to add processing capacity, but it is very impractical beyond a certain point due to power and heat considerations (where that point is exactly depends on the state of technology at any given moment but in the end is limited by the physical size of molecules, at least for as far as current technology goes)

    So, multiple processors is not directly better from an engineering point of view, rather, it is a solution to overcome the speed limits of current technology, provided you can deal with the extra complexity (moving much of the hardware complexity into the chip itself like AMD and Intel are doing now removes the burden from systemboard designers, but the complexity itself is still there, esp. on the software side of the picture).

    With regards to 3dfx, it seems to me that:
    1. They failed to manage the additional complexity
    2. As their competition showed, limits of technology at that time were much higher then what 3dfx managed, which indicates there were problems with either their design or manufacturing technology, or more likely, with both.

  18. Not so much by Sycraft-fu · · Score: 4, Informative

    System RAM is SLOW compared to GPU RAM. PCIe actually allows very high speed access to system RAM, but the RAM itself is too slow for GPUs. That's one of the reasons their RAM amounts are so small, they use higher speed and thus more expensive RAM. Also because of the speed you end up dealing with cooling and signal issues which makes it impractical (or perhaps impossible) to simply stick it in addon slots to allow for upgrades.

    Even fast as it is, it's still slower than the GPU would really like.

    What you've suggested is already done by low end accelerators like the Intel GMA 950. Works ok, but as I said, slow.

    Unless you are willing to start dropping serious amounts of cash on system RAM, we'll be needing to stick with dedicated video RAM here for some time.

  19. Some things you forget by Sycraft-fu · · Score: 3, Informative

    1) Processors are wicked fast at floating point these days. Have a look at the benchmarks a modern chip using SSE2 can do some time. Integer doesn't inherently mean faster, and chips these days have badass FPUs.

    2) For many things, it DOES make a difference. You might ask why do we need more than 24-bit (or 32-bit if you consider the alpha channel) integer colour? After all, it's enough to look highly realistic. Yes well that's fine for a final image, but you don't want to do the computation like that. Why? Rounding errors. You find that with iterative things like shaders doing them integer adds up to nasty errors which equals nasty colours and jaggies. There's a reason why pro software does it as 128-bit FP (32-bits per colour channel) and why cards are now going that way as well.

    3) In modern games, everything is handled in the GPU anyhow. The CPU sends over the the data and the GPU does all the transform, lighting, texturing and rasterizing. The CPU really is responsible for very little. With vertex shaders the GPU even handles a good deal of the animation these days. The reason is that not only is it more functional but it's waaaaay faster. You can spend all the time you like trying to make a nice optimised integer T&L path in the CPU, the GPU will blow it away. You actually find that some older games run slower than new ones because they rely on the CPU to do the initial rendering phases like T&L before handing it off, whereas newer games let the GPU handle it and thus run faster even though having higher detail.

  20. What's that got to do with anything? by Sycraft-fu · · Score: 5, Informative

    Yes the SYSTEMS Tom used to test have normal speed ram for systems. Duh. The graphics cards, however, have much faster RAM. For example my system at home has DDR2-667 RAM. That's spec'd to run at 333MHz which is 667MHz is DDR RAM speak. My graphics card, a 7800GT, on the other hand has RAM clocked at 600MHz, or 1200MHz in RAM speak.

    Not a small difference, really. My system RAM is rated to somewhere around 10GB/second max bandwidth (it gets like 6 in actuality). The graphics card? 54GB/sec.

    Video cards have fast RAM subsystems. They use fast, expensive chips and they have controllers designed for blazing fast (and exclusive) access. You can't just throw normal, slow, system RAM at it and expect it to perform the same.