Slashdot Mirror


Nvidia Mulls Cheap, Integrated x86 Chip

CWmike writes "Nvidia is considering developing an integrated chip based on the x86 architecture for use in devices such as netbooks and mobile Internet devices, said Michael Hara, vice president of investor relations at Nvidia during a speech that was webcast from the Morgan Stanley Technology Conference this week. Nvidia has already developed an integrated chip called Tegra, which combines an Arm processor, a GeForce graphics core and other components on a single chip. The chips are aimed at small devices such as smartphones and MIDs, and will start shipping in the second half of this year. 'Tegra, by any definition, is a complete computer-on-chip, and the requirements of that market are such that you have to be very low power and very small but highly efficient,' Hara said. 'Someday, it's going to make sense to take the same approach in the x86 market as well.'"

211 comments

  1. oh god, please no. by girlintraining · · Score: 2, Insightful

    For those of us who dealt with intel's "integrated" graphic cards on laptops for the past several years now... on their behalf I just want to say PLEASE FOR THE LOVE OF ALL THINGS SHINY AND SILICON, DON'T DO IT! Anything with the word "integrated" near it makes me want to cringe... it's a post traumatic stress response caused by watching a myriad of good video games shutter, blink, crash, and burn right in front of me. It's a black day indeed when Warcraft 3 can't run at full resolution on a laptop produced only a year ago.

    --
    #fuckbeta #iamslashdot #dicemustdie
    1. Re:oh god, please no. by aliquis · · Score: 2, Informative

      Heh, funny that you mention it.

      I run WC3 on my Macbook Pro 1.5 year old and I use 1024x768, medium, high, medium, high, high, on, on, high. So medium models and textures ...

      And I agree, especially in this price range :D

    2. Re:oh god, please no. by aliquis · · Score: 1

      Anything with the word "integrated" near it makes me want to cringe...

      But then again Apple claim the new Mac Mini with 9400M and shared RAM can run the latest games ..

      Reality distortion field [checked]

    3. Re:oh god, please no. by Anonymous Coward · · Score: 0

      wtf? It's only a step up from the 8600 to the 9600, barely any difference in speed, and I'm running WC3 with all settings on high...

    4. Re:oh god, please no. by Anonymous Coward · · Score: 1, Informative

      For what most people do though, Intel's integrated graphics are more than enough (and use less power than discrete cards on notebooks). Gamers are a niche market, especially for notebooks.

    5. Re:oh god, please no. by aliquis · · Score: 1

      But while I'm already burning karma maybe I should point out this:
      http://www.nvidia.com/object/product_geforce_9100m_g_mgpu_us.html

      So motherboard GPU GeForce 9100M G + SLI connected discrete GPU 9200M/9300M GS = 9400M.

      So it seems like it's not an improved 8400m, and the 9300M GS is slower than the 8400M GS (which is slower than 8400M GT:)
      http://www.nvidia.com/object/geforce_9100m_g_mgpu.html

      Faster than X4500 but still suck for anyone who actually need any graphics power and to claim that it will run the latest games is absurd, even though DX10 pick-up has been slim and demands seem to have stalled somewhat for the last two years or so.

    6. Re:oh god, please no. by nedlohs · · Score: 5, Funny

      Yes, because what I want to do is slot a PCIe card into my damn cell phone.

    7. Re:oh god, please no. by Yomer333 · · Score: 1

      Warcraft III is a special case. For a lot of integrated intel cards, it's better to disable hardware T&L and just use software T&L. I can play WC3 with all the settings maxed on my x3100 on my laptop, but it was hardly playable at low before disabling the hardware T&L.

    8. Re:oh god, please no. by physburn · · Score: 1

      True, but only for Intels integrated graphics. Nvdia, and ATIs are a lot better. They won't play new games at best resolution and 16 time antialiases, but they probably would play a newish game at medium resolution.

    9. Re:oh god, please no. by cjb658 · · Score: 3, Insightful

      It's being designed for netbooks, which aren't typically designed for gamers.

      Fortunately, the one good thing that's come from Vista is that now almost all new computers come with decent graphics cards.

      I hated looking for new laptops that were $800 and finding out they had integrated graphics, then being forced to pay for the "premium" product tier to get discrete graphics, which included a much more expensive processor and RAM.

      With a desktop, you can just buy a $500 PC at Walmart and drop in a decent graphics card.

    10. Re:oh god, please no. by maxume · · Score: 1

      How 'bout you pay attention to what you are buying, and other people who want a cheap, lower power chip have more choices?

      --
      Nerd rage is the funniest rage.
    11. Re:oh god, please no. by Samah · · Score: 1

      Anything with the word "integrated" near it makes me want to cringe...

      So you don't want to use any silicon chip then?
      http://en.wikipedia.org/wiki/Integrated_circuit

      --
      Homonyms are fun!
      You're driving your car, but they're riding their bikes there.
    12. Re:oh god, please no. by Anonymous Coward · · Score: 0

      "watching myriad good video games"

      It is NOT a standard collective noun you TWAT!

    13. Re:oh god, please no. by tepples · · Score: 1

      With a desktop, you can just buy a $500 PC at Walmart and drop in a decent graphics card.

      With a desktop PC, it's also a lot harder to move the PC from your home office to the TV room when you want to play games on the 32" flat screen. But then, I guess you could buy a second desktop PC for the TV room with the money you save vs. a laptop PC.

    14. Re:oh god, please no. by coxymla · · Score: 2, Informative
      Any MacBook Pro ought to be able to slaughter WC3 at all full settings on the high resolution. Maybe not in the nv9400 mode (although I wouldn't be surprised if even that chip could handle the awesome power of a 4 year old game) on the latest unibody models, but still.

      Are you sure that you're running a Universal Binary version? If not, then your CPU has to emulate PPC instructions. Get the latest updates from Blizzard and your experience should be a lot better.

    15. Re:oh god, please no. by Anonymous Coward · · Score: 0

      But atleast your 9600M GT got a decent amount of VRAM with 256 MB, Apple was retarded and opted for 128 MB on the 8600M GT MBPs (unless you wanted to pay 700 dollar more..)

      Also we may demand different things, I play 3on3 and want to be able to notice the action in bigger fights even if there may be some light effects and such, you may not.

      I will try higher res again, maybe Leopard improved things somewhat, earlier I ran everything on medium so ..

    16. Re:oh god, please no. by morgan_greywolf · · Score: 2, Insightful

      "Most people"? Please define what "most people" do. Have you seen how crappy Google Earth and Google Sketchup are on integrated Intel graphics?

    17. Re:oh god, please no. by aliquis · · Score: 1

      Well, since we talked about it I raised res to 1440x900 all the same (medium textures and models), and it lagged like crazy even when there was only heroes + like 5 units each or so during early rush.

      Though then I play 3on3 RT and in OS X, I'm confident it would run smooth in Windows. I think my 6800 LE may have run better in Windows than this 8600m GT in OS X.

      Well, my 8600m GT doesn't come close so no, no change in hell 9400m would do it.

      I don't remember where to see if it's PPC or Intel version but I'm quite sure I've installed it all and got the updates before running it so should be universal binary.

      Program (Universal) says more info for the ROC icon, and I can't click run in Rosetta on it. So should be universal.

      I'm not doing anything wrong, it's just that all mac users live in denial.

    18. Re:oh god, please no. by Anonymous Coward · · Score: 0

      watching a myriad of good video games

      Try "watching myriad good video games" next time, although "watching many good video games" is better; it's likely to be more readily understood and doesn't make you sound as though you're trying to show off your vocabulary (which fails with your original phrasing).

    19. Re:oh god, please no. by NeoStrider_BZK · · Score: 1

      Try programming a 3D application for a mobile device without such a integrated chip on it. Im not talking about your Ghz laptop, but about a smartphone or a PDA or even maybe a netbook (the line between those devices is now too blurred to clearly define it)

    20. Re:oh god, please no. by timeOday · · Score: 2, Funny

      Fine, but I refuse to use any newfangled CPU that has integrated cache memory and can't harness the power of my math coprocessor.

    21. Re:oh god, please no. by White+Flame · · Score: 2, Insightful

      Or you could get a 30" flat screen for your desktop, a nice audio system, and a comfortable chair and not have duplicate media setups.

      For bonus points, put a couch behind your chair & move the chair out of the way when you have guests.

    22. Re:oh god, please no. by slyn · · Score: 3, Informative

      Um, wat? I have the same model you do (it's the santa rosa MBP with the 8600m GT yes?) and it has no problem running WC3 at full res and everything maxxed. Anything less and your computer probably has something wrong with it.

      I can run WoW in dalaran (for those not familiar with the game, the busiest city) on a packed server or do a full 25 man raid with everything but view distance maxxed and view distance at around 1/3 of max and still average ~30+ FPS. If I go any higher on distance I need to lower most other settings, as I think thats when all the various armor/player/model/building/etc textures start causing the 256 mb of graphics ram to have to swap out and things start getting shitty. WC3 is much less graphically intense than that even if you've got two huge armies going at it.

      Maybe an early sign of this: http://support.apple.com/kb/TS2377

      I got that but Apple fixes it for free warranty or not since its Nvidia's manufacturing problem (my understanding is its the same problem (conceptually) as the RRoD only on your laptop).

    23. Re:oh god, please no. by RzUpAnmsCwrds · · Score: 1

      It's a black day indeed when Warcraft 3 can't run at full resolution on a laptop produced only a year ago.

      Frozen Throne runs fine on my stinking EEE PC 900HA. And it has a three-generation-old, under-clocked Intel GMA 950.

      Frozen throne should run great on a GMA X4500. Even WoW runs OK on a GMA X4500.

    24. Re:oh god, please no. by Anonymous Coward · · Score: 0

      According to this site the 9400M G has higher core and shader clocks than the 9300M G, but the 9300 has dedicated memory.

      The benchmark results listed there show:

      9300M G
      3DMark 05: 3252
      3DMark 06: 1958
      Doom3: 38 FPS (Ultra detail 1024x768)

      8400M GT
      3DMark 05: 3587
      3DMark 06: 1033
      Doom3: 49 FPS (Ultra detail 1024x768)

      9400M G
      3DMark 05: 3930
      3DMark 06: 2067
      Doom3: 83 FPS (Ultra detail 1024x768)

    25. Re:oh god, please no. by Anonymous Coward · · Score: 0

      That takes care of video. Now what about audio, keyboard, mouse and game controllers?

    26. Re:oh god, please no. by Waccoon · · Score: 1

      I think graphics with an integrated motherboard will fare much better than the opposite.

    27. Re:oh god, please no. by msormune · · Score: 1

      Warcraft 3 requires something like a Voodoo 3 card. Even the slowest integrated gfx chips today outperform that by something like 5-10 times.

      In fact, you could get faster frame rates with a dual core CPU doing ALL the rendering into the frame buffer.

      There's something wrong with your laptop.

    28. Re:oh god, please no. by jabithew · · Score: 1

      I have to say, WC3 runs happily on my year-old MacBook.

      --
      All intents and purposes. Not intensive purposes.
    29. Re:oh god, please no. by tepples · · Score: 1

      [A 15 meter DVI cable] takes care of video. Now what about audio, keyboard, mouse and game controllers?

      Audio is easy; USB is harder, as USB cables can't be longer than 5 meters. You can use a chain of five hubs in a row, but that gets expensive, and at least some of your hubs will have to be self-powered (that is, using their own wall wart instead of sucking 5 V from upstream). In fact, USB.org recommends something that amounts to tunneling USB over Ethernet for long distances. But by far, the hardest step is drilling holes in your walls, especially if you live in a state with a restrictive electrical code or your landlord isn't technically adept. And it's still a pain in the behind to insert the game disc (the one that you bought, or the one that you burned when you purchased a download) to play if the PC's in another room.

    30. Re:oh god, please no. by frieko · · Score: 1

      Yea, I was sorta going for a laugh, although I DO run ridiculous cables to things in my house.
      http://www.iofast.com/product_info.php/products_id/3452

    31. Re:oh god, please no. by CompMD · · Score: 1

      Not all computers are for gamers.

    32. Re:oh god, please no. by Anonymous Coward · · Score: 0

      If you had been using a Mac mini with a GMA950 for over two years, you'd be welcoming the 9400M with open arms and a little tear of joy.

    33. Re:oh god, please no. by aliquis · · Score: 1

      My information came from:
      http://forum.notebookreview.com/showthread.php?t=309769

      But maybe that was too early speculations then.

    34. Re:oh god, please no. by aliquis · · Score: 1

      Yeah, I've had lots of scrambled web pages and just a few times really messed up graphics screen so I think my GPU is broken as well, don't know if that should make it lag though.

      I mailed them just before one year had passed with all my issues but they wanted me to call them which I haven't since it would had been easier to list it all and explain it in text but whatever.

    35. Re:oh god, please no. by slyn · · Score: 1

      A while before mine fully shat itself I got this: http://img141.imageshack.us/img141/9207/distortion.png

      I was surprised after I restarted that it still took a proper screenshot despite being messed up, but if that's the sort of distortion you get, its probably an early sign of bad things to come.

      The last time my MBP worked before it totally crapped out I was playing a game and it got extremely laggy (like 2-3 fps), and because that sort of lag was not normal in my playing, I tried restarting the computer to see if something had gotten borked randomly. The computer would boot fine, but the screen wouldn't "start". Your unit is probably not 100% poopy, but somehow halfway broke, which gives you occasional distortion and poor performance rather than a completely dead card.

      I would recommend you back up whatever you've got and call up Apple support and explain the distortion and poor graphics performance you've been getting. I went to a store but the tech there thought it was something else, the cost of which to repair (when you factor in both parts and labor + taxes) would have been as much as a refurbished model of what I had. However, the Apple phone support person suggested that it was the problem in the support document I posted earlier right off the bat. The repair is free as long as your within two years of buying your computer, so since you noted your computer is around 1.5 years old earlier in the thread, it would probably be best for you to get that repaired soon.

    36. Re:oh god, please no. by CAIMLAS · · Score: 1

      You do realize that what you're talking about has nothing to do with 'integrated' anything, and everything to do with half-assed products from Intel put on the market to keep their market share up, and competition down, right?

      Integrated Intel solutions have always been crap. As a general rule, integrated things -are- crap, but that's largely because they're the cheap solution from some unknown vendor (hey, cool, an integrated motherboard for $35!) or the cheapest solution from Intel.

      SoCs are awesome. Let's just clear that up.

      Also, AMD has managed, for quite a few years now, to have very 'integrated' systems which perform well. Did you know their north bridge is integrated with the processor now? Also, the integrated ATI chipsets are pretty decent (good enough for gaming), especially when compared to what Intel pushes.

      I've BTDT with integrated crap, myself. I currently suffer with all the crap Intel's got out there (from i810 through the current generation) that under-performs ATI chips from 10 years prior in 2D, and slower than software in 3D. Back in the mid-90s, when integrated stuff was fist coming out, I suffered with it then, too.

      Yes, it is generally crap - but because it's usually a half-assed effort by the company, as a stopgap product. Intel makes processors, so such things as graphics and chipsets are secondary. NVidia makes graphics cores/cards, so the graphics section, at least, will be pretty solid. I imagine they'd license the x86 spec from Intel, or maybe try and join up with Via, to produce something that can at least run a basic desktop with good graphics (which is the main bottleneck in desktop performance these days, it seems - not CPU).

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
  2. Prediction.. by pak9rabid · · Score: 5, Funny

    Nvidia develops a very basic x86 CPU thats tightly coupled to one of their embedded GPUs that doesn't implement any x86 technology that's still currently patent-protected. The basic x86 CPU acts as a shim for software that expects to talk to an x86 CPU and offloads as much as possible to the significantly more advanced GPU running the bulk of the load. The end result? An x86-compatible embedded system that vastly outperforms anything currently on the market that doesn't violate anyone's active x86 patents.

    1. Re:Prediction.. by Anonymous Coward · · Score: 5, Funny

      Wow, do you even know anything about x86?

    2. Re:Prediction.. by larry+bagina · · Score: 4, Funny

      almost as much as he knows about GPUs.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    3. Re:Prediction.. by Fulcrum+of+Evil · · Score: 4, Interesting

      x86 in an instruction set and a bunch of semantics. The decoder takes about 1% of a modern CPU, and if you're able to lop this off and run it on a GPU or something for cheap, your software won't care.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    4. Re:Prediction.. by fuzzyfuzzyfungus · · Score: 1

      Or, they could just talk to VIA, which already has everything in order to produce basic but unexciting x86s; but has long suffered from high levels of graphical suck. NVidia's contention has been that x86 performance is minimally important compared to GPU performance; but, obviously, you need some x86 to run Wintel stuff: thus, VIA's not all that exciting; but cheap and almost definitely up for licence/collaboration or purchase, x86 as an option.

    5. Re:Prediction.. by physburn · · Score: 1

      Nvdia would might have to buy VIA, as the only way to get a x86 license, which Intel hardly likes to give away. I don't know how else Nvida will get one. Nvdia is probably worried about AMD's Fusion, with a ATI graphics chip and Phenom on the same bit of silicon. Fusion might well come to rule the low end system, and Nvida wants a peace of the action.

    6. Re:Prediction.. by aztektum · · Score: 1

      You forgot the part about it somehow, some way, being litigated to death and never seeing the light of day.

      --
      :: aztek ::
      No sig for you!!
    7. Re:Prediction.. by Anonymous Coward · · Score: 1, Interesting

      Why bother with a license? The 386 patents are over, and the 486 patents ought to all be expiring right about now. So make the new chip a 486 clone. A really fast and modern 486 clone.

    8. Re:Prediction.. by setagllib · · Score: 4, Funny

      Wow, now all we need is to connect the GPU to the FSB/QPI, make it support pagetables, interrupts, DMA, CPU-style L1/2/3 coherent cache, memory controller with synchronous fencing, legacy and long modes for pointers and instructions, etc.... and then we'll have something that can possibly emulate an x86 CPU at only 99.9% performance penalty!!

      Or, you know, not.

      --
      Sam ty sig.
    9. Re:Prediction.. by Anonymous Coward · · Score: 0

      The funny thing is when they are planning to get in on the action

      > He didn't discuss specific plans but said such a move might make sense in two to three years

      Hmm. I'd say the netbook market will be either very solidly established or dead by then.

    10. Re:Prediction.. by morgan_greywolf · · Score: 1

      Hold up! What makes you think he isn't right? What he described is almost exactly what the IBM Cell processor is, except with the Power Architecture.

    11. Re:Prediction.. by salimma · · Score: 1

      and miss out on MMX, SSE, SSE2, SSE3?

      --
      Michel
      Fedora Project Contribut
    12. Re:Prediction.. by Jorophose · · Score: 1

      VIA's got a pretty strong CPU; the Nano holds its own for the low-power segments.

      An nVidia-VIA partnership would have worked wonders but nVidia went there and came back. For some reason they wanted to do ION instead. What a sick joke; and here I was hoping for a VIA Nano wiht a 9400 chipset.

    13. Re:Prediction.. by mgblst · · Score: 2, Funny

      Not just x86, but this guy clearly doesn't know anything about CPU/GPUs at all. Kinda like an old friend of mine, convinced he was going to design his own CPU, despite not knowing anything about computer hardware. Or even computer software. Sure could play games though, and smoke a lot of dope.

    14. Re:Prediction.. by mgblst · · Score: 1

      If we could somehow integrate the photon torpedoes to initiate a reverse tachyon beam, I think we might have a real challenger on our hands.

      Too much Star Trek?

    15. Re:Prediction.. by Anonymous Coward · · Score: 0

      I'd expect the GPU to be doing most of the work as cell phones advance. We all like eye candy.

      Good point though.

    16. Re:Prediction.. by SpazmodeusG · · Score: 1

      Well yes, the standard practice for making a modern x86 CPU is to make a RISC core and then put a decoder in to translate x86 instructions (see the AMD K5 for a good example of this).

      However, GPUs are a little different. The programming model of a GPU is as follows;
      Load in a block of code that performs some kind of mathematical operation (known as a kernel).
      Specify the block of data to run the kernel against and the block of data to put the output.
      Run the kernel.

      For an x86 program that typically consists of a series of sequential operations on small data sets there is a hell of a lot of overhead. You're spending more time loading and unloading kernels than you are actually processing blocks of data.
      Not to mention that GPUs have limited branching capabilities (all GPGPU tutorials tell you to avoid branching and the cost it incurs).

      If nVidia changed the way its graphics cards worked, all this would be possible, but then if they have to change the graphics cards that much they may as well just make an x86 from scratch.

    17. Re:Prediction.. by Fulcrum+of+Evil · · Score: 1

      Given the content of TFA, Nvidia may well be building an integrated chip that's just something like a 486 on 45nm silicon. The actual shared silicon may be nothing much at all - MMU or something.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    18. Re:Prediction.. by Anonymous Coward · · Score: 0

      x86's strongest (possibly only) advantage is support for legacy code/windows. A cell-eron will have atrocious performance for any code not specifically designed for it.

    19. Re:Prediction.. by Anonymous Coward · · Score: 0

      The x86 standard has nothing specific to the FSB/QPI, these are just custom additions to the x86 core. The same custom additions could be done to any core giving it the same FSB/QPI connectivity.

      The MMU, interrupts, priviledge rings and legacy modes are all implemented in software via microcode on the actual type of CPU the x86 is underneath (no modern x86 is entirely an actual x86 in hardware - that's why there is a decoder). You could put a decoder on any turing-complete CPU and have all of those features.

    20. Re:Prediction.. by Klintus+Fang · · Score: 1

      in theory yes. in practice, it is a lot more complicated then that. GPU's are very good at crunching floating point style operations on wide data sets and have very wide and deep pipelines that are heavily optimized for that purpose. their pipelines are not well suited for the general purpose computing problems that an OS has to deal with which are riddled with branches and interrupts. without a branch predictor, the GPU pipeline would have to stall on every branch and if it had a branch predictor the branch mispredict penalty would be atrocious because the pipelines are so deep.

      Slapping the trappings needed to support all those nitty gritty OS-level details onto a GPU pipeline would suit no useful purpose. It would be like taking the trailer off the cab of an 18 wheeler and hitching it to the back of a ferrari. Yes, its theoretically doable, but none of the ferrari's strengths are suited for the purpose of hauling freight and the end result would be comical.

      I think the fact that nvidia is talking about coupling x86 cores with a GPU proves that they agree. Packaging them together into a single die for low-power applications makes sense. Forcing them together even further so the GPU pipeline is also handling the general purpose side of the computing needs does not.

      --
      In a minute there is time For decisions and revisions which a minute will reverse. -T.S. Eliot
    21. Re:Prediction.. by Elledan · · Score: 1

      Even better. An instruction set like x86, MIPS, PPC, ARM and so on can not be patented or licensed. It is a pipe dream from Intel (and others) and a perversion of the system that people think that an API could be patented or licensed. That would be like a project such as ReactOS (Windows clone) getting nuked by MSFT because it had the nerve to use its proprietary, license-only APIs. Heck, you better buy a license if you want to program anything which uses the Windows API...

      There are perfectly valid patents and such related to x86/CPU technology, but the x86 API isn't one of them.

      --
      Site & blog: http://www.mayaposch.com
    22. Re:Prediction.. by Anonymous Coward · · Score: 0

      The grandparent suggested a stripped down x86 core, (say, an i486 logic core, which has all those shiny features you speak of) and then implements "Patented" technologies in a wrapper so that they run on the GPU instead. These being things like the SSE/SSE2/SSE3/3DNOW and friends, which are by their nature highly repetitious, and in some rather gross terms arguably convertible into GPU code.

      NOT coaxing a stand alone GPU into performing full CPU memory protection, cache management and memory allocation functions and general purpose x86 instructions, like you suggest.

    23. Re:Prediction.. by Anonymous Coward · · Score: 0

      yeah right. What is this emulation you speak of?

    24. Re:Prediction.. by setagllib · · Score: 1

      Interrupts, DMA, memory control, etc. are NOT implemented in software, they require cooperation from the motherboard at minimum. Your GPU would need significant hardware extensions to be able to function as a CPU sufficiently that a BIOS could use it to bootstrap and access host hardware directly. At that point it may as well be a CPU.

      There's a "cycle of reincarnation" with hardware. First new hardware is created to meet new requirements, then as it is refined, optimised and physically shrunk, it is integrated deeper into its host system. Sometimes the external version is never marketed again since it has no remaining advantages. Examples:

      Card -> motherboard integration
      * Onboard audio (good enough for 99% of users)
      * Onboard LAN (99%)
      * Onboard video (maybe 80%, I don't have figures)

      Board device -> CPU component integration:
      * Floating point coprocessors (integrated into the instruction set itself)
      * Memory controllers (in CPU since Athlon64 and Core i7)
      * Temperature sensors (integrated into the CPU per-core)
      * RAM (now 3 layers of CPU cache, each larger than entire computers used to have, but we still use RAM for general purposes)

      And very soon, GPU in CPU, thanks to projects from Intel and AMD.

      This is the way of things. nVidia will drag out a few more years providing high-performance GPUs, but they're kidding themselves if they think they won't also be absorbed into the motherboard or CPU.

      --
      Sam ty sig.
    25. Re:Prediction.. by morgan_greywolf · · Score: 1

      Only? No, it's other advantage is that it's readily available in large quantities and it is cheap. Other than that, yeah, you're right.

    26. Re:Prediction.. by smallfries · · Score: 1

      Although you are correct in a moral indignation sense, sadly you are wrong in an actual reality sense. Instruction sets have been patentable for may years, and form a large part of the Intel / AMD war-chest that they can threaten impudent upstarts with. The standard trick that gets used (and has been defended in court) is to claim that the instruction is a method of encoding a particular process. Once you reduce things to a process a patent examiner, and then a court are more likely to go along with you.

      --
      Slashdot: where don knuth is an idiot because he cant grasp the awesome power of php
    27. Re:Prediction.. by Sal+Zeta · · Score: 1

      It would be like taking the trailer off the cab of an 18 wheeler and hitching it to the back of a ferrari. Yes, its theoretically doable, but none of the ferrari's strengths are suited for the purpose of hauling freight and the end result would be comical.

      Well, that's exactly what the Chrysler did with the Dodge Viper. from the wikipedia:

      The team asked the then-Chrysler subsidiary Lamborghini to cast some prototype aluminum blocks based on Dodge's V10 truck engine for sports car use in May.

    28. Re:Prediction.. by Simetrical · · Score: 1

      Wow, now all we need is to connect the GPU to the FSB/QPI, make it support pagetables, interrupts, DMA, CPU-style L1/2/3 coherent cache, memory controller with synchronous fencing, legacy and long modes for pointers and instructions, etc.... and then we'll have something that can possibly emulate an x86 CPU at only 99.9% performance penalty!!

      Or, you know, not.

      Okay, the fact that this is modded Funny instead of Informative is pretty pathetic.

      --
      MediaWiki developer, Total War Center sysadmin
    29. Re:Prediction.. by Klintus+Fang · · Score: 1

      Yes. But taking the engine out of one car and putting it into a completely redesigned chassis is analogous to taking the GPU pipeline apart and putting it back together in a way that no longer resembles a GPU pipeline.

      --
      In a minute there is time For decisions and revisions which a minute will reverse. -T.S. Eliot
    30. Re:Prediction.. by Fulcrum+of+Evil · · Score: 1

      they're kidding themselves if they think they won't also be absorbed into the motherboard or CPU.

      Nvidia already makes chipsets, so they're covered there. There will always be a place for fancy graphics cards - I don't see even a 30W onboard chip, realistically - a GPU with a small heat draw is fast enough for all business users and some less demanding games. Anything bigger and you're probably in the GPU upgrade cycle anyway. It's a niche now and in the future, but it won't disappear anytime soon.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    31. Re:Prediction.. by Dogtanian · · Score: 1

      And do you know that current Intel and AMD processors emulate x86?

      yeah right. What is this emulation you speak of?

      The emulation that has formed the basis of all Intel's x86 processors from the Pentium Pro/Pentium II onwards, that's what!

      The core of the processors are RISC-like (unlike the "genuine" x86 CISC cores of the original Pentium and older chips). x86 instructions are converted internally to RISC format before execution. (More).

      To the best of my knowledge, this is transparent to the rest of the system and any code running on it. In fact, that's an interesting question- is there *any* way of accessing the CPU at the RISC level? My guess is that there must be, because IIRC Linux (and possibly Windows) can alter the behaviour of the CPU to compensate for bugs.

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    32. Re:Prediction.. by Dogtanian · · Score: 1
      (I don't know why this comment was considered "troll", so I'm replying anyway).

      Do you also know that this non-native execution downgrades performance by 5 times?

      Relative to what? If (say) Intel can build a RISC-based chip that runs 5 times faster by some metric(s), and stick an x86 CISC -> RISC wrapper on that, then it's just as good.

      If it had been more productive- or practical- for Intel to continue basing their x86 line on "native" x86 cores, I'm sure that they would have.

      I remember reading about the x86 design, its accumulated cruft and architectural legacy and being amazed that the Intel engineers could do *anything* with such a design while retaining compatibility. When I found out that the newer chips were in effect transparently emulating x86 on a RISC core, it made a lot more sense.

      Your "5 times" comment is only meaningful if Intel could have continued improving their chips while still basing them around an actual x86 core, and I'm not convinced that that would have been possible.

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    33. Re:Prediction.. by setagllib · · Score: 1

      nVidia wants to make chipsets which are potentially not covered by their agreement with Intel. Intel seems to want to take that market back, and as anticompetitive as it is, it might just work. nVidia will be stuck making only niche products which are guaranteed to be crippled by anticompetitive behavior. If you think this can't possibly work, look where it got Microsoft.

      --
      Sam ty sig.
  3. If they bail out, then the headline will by davidsyes · · Score: 4, Funny

    read:

    "Nvidia NULLS Cheap, Integrated x86 Chip "

    --
    Previously: "Linux... Toward the Sunrise..." Now: "Linux... Toward the-- No, now, part of Every Sunrise"
    1. Re:If they bail out, then the headline will by Ninnle+Labs,+LLC · · Score: 3, Funny

      No, you need something more graphics related like "Nvidia Culls Cheap, Integrated x86 Chip".

    2. Re:If they bail out, then the headline will by davidsyes · · Score: 1

      But, if they cripple it for Linux, then...

      "Nvidia DULLS Cheap, Integrated x86 Chip "

      and if they introduce it to but then ((e)specially) remove it from Linux access:

      "Nvidia CULLS Cheap, Integrated x86 Chip "

      (cull:
      http://en.wikipedia.org/wiki/Culling
      )

      --
      Previously: "Linux... Toward the Sunrise..." Now: "Linux... Toward the-- No, now, part of Every Sunrise"
  4. Too many issues with assymetirc multicores by Slumdog · · Score: 1

    1. Microbenchmarking becomes too difficult when two or more cores of different types are used
    2. Inter-core communication takes a hit because you'll end up designing new flit routers (or even newer protocols) that efficiently route packets within cores that have different communication topology
    3. Failure of one core can render the chip useless, whereas in the case symmetric multicore design, failure of one core means other cores are still functional and the company can market them separately.
    4. Production issues involving 1,2, and 3 above.

    Eventually we'll end up with a dynamic multicore design which seems more promising than asymmetric designs. Some research has been done in this area (symmetric vs. asymmetric vs. dynamic via threading): http://www.cs.wisc.edu/multifacet/papers/tr1593_amdahl_multicore.pdf

  5. x86? by mangamuscle · · Score: 0

    Why botther at all? Better go straight to x64, I mean, even the lowliest of nvidia GPUs is already 64 bits, why bother with 32 bits technology?

    1. Re:x86? by timmarhy · · Score: 2
      it's still an x86 instruction set... duh.

      not only that but what exactly do you think your handheld/phone is going to do with more than 4 gig of ram per process?

      --
      If you mod me down, I will become more powerful than you can imagine....
    2. Re:x86? by pak9rabid · · Score: 2, Funny

      Why botther at all? Better go straight to x64, I mean, even the lowliest of nvidia GPUs is already 64 bits, why bother with 32 bits technology?

      They day an embedded system's CPU needs to address more than 4 gigs of memory (which is essentially why you would shift from a 32-bit to 64-bit CPU) is the day my shit turns purple and smells like rainbow sherbet.

    3. Re:x86? by Anonymous Coward · · Score: 5, Informative

      x64 is a Microsoft marketing term. Please stop using it. The architecture is x86-64.

    4. Re:x86? by Anonymous Coward · · Score: 0

      what exactly do you think your handheld/phone is going to do with more than 4 gig of ram per process?

      Same thing as your server. A phone and a rackmounted server in a datacenter, are the same thing.

    5. Re:x86? by Ninnle+Labs,+LLC · · Score: 1

      Since when have you ever seen a phone that even has 1 gig of memory in it let alone over 4?

    6. Re:x86? by Ninnle+Labs,+LLC · · Score: 1

      Okay, but the point still stands that 64bit address space isn't needed on a phone at any point in the future. That is probably one of only a handful that even have 1 gig.

    7. Re:x86? by rocketPack · · Score: 1

      ***WOOOOOOSHHHH***

      Wow, did Chuck Norris just go by, or did you miss a joke?

    8. Re:x86? by bruno.fatia · · Score: 4, Funny

      not only that but what exactly do you think your handheld/phone is going to do with more than 4 gig of ram per process?

      Nothing as 640k is enough for any phone.

    9. Re:x86? by nxtw · · Score: 1

      From what I can find, that device has 196 MB RAM and 1 GB of onboard storage (this is in addition to the 128 MB of flash for the OS and the microSD slot).

      This is different than having 1 GB of byte-addressable DRAM.

    10. Re:x86? by kkrajewski · · Score: 1

      We're already a quarter of the way there. It won't be long now.

      What was that quote about 640K? ;)

    11. Re:x86? by cjb658 · · Score: 1

      Why botther at all? Better go straight to x64, I mean, even the lowliest of nvidia GPUs is already 64 bits, why bother with 32 bits technology?

      They day an embedded system's CPU needs to address more than 4 gigs of memory (which is essentially why you would shift from a 32-bit to 64-bit CPU) is the day my shit turns purple and smells like rainbow sherbet.

      Is 640K enough for you still?

    12. Re:x86? by merreborn · · Score: 1

      Why botther at all? Better go straight to x64, I mean, even the lowliest of nvidia GPUs is already 64 bits, why bother with 32 bits technology?

      They day an embedded system's CPU needs to address more than 4 gigs of memory (which is essentially why you would shift from a 32-bit to 64-bit CPU) is the day my shit turns purple and smells like rainbow sherbet.

      The iPhone packs 128 meg, as does the BlackBerry Bold. A modern smartphone packs as much ram as the average desktop did a little under a decade ago. SODIMMs (laptop ram) look to be just over $10 per gig. But hey, 640k is all anyone really needs, right?

      You may notice some changes in the appearance and fragrance of your excrement in less than a decade.

    13. Re:x86? by DragonWriter · · Score: 1

      not only that but what exactly do you think your handheld/phone is going to do with more than 4 gig of ram per process?

      "640K should be enough for anybody", updated for 2009.

      Plus, TFS specifically mentions netbooks as part of where the chips would be used, which are more likely to make that particular feature likely than handhelds/phones, as the use cases for those are pretty much those for a general purpose laptop -- but with more focus on battery life (hence, power consumption), weight, and cost. I suspect the same issues that Nvidia sees that would make it make sense to "at some point" go from ARM to x86 for integrated chips would also at some point make it make sense to go to x86-64 as well, though it might be at a later point than going to x86.

    14. Re:x86? by frehe · · Score: 1

      the day my shit turns purple and smells like rainbow sherbet

      Anime styled shit sure sounds like a good way to earn a lot of money in Japan, by combining two of its most prominent fetishes into a product, that can be easily packaged and sold in vending machines.

    15. Re:x86? by Cajun+Hell · · Score: 1

      Since next year (or the year after or whenever) when 256 GB of DDR7 RAM costs $1.95. Take the long view, dude.

      --
      "Believe me!" -- Donald Trump
    16. Re:x86? by Anonymous Coward · · Score: 0

      They day an embedded system's CPU needs to address more than 4 gigs of memory [...] is the day my shit turns purple and smells like rainbow sherbet.

      Best make that appointment with the doctor now then. If you had a checkup in say... 5 years, that'd do you well because it's going to happen within a decade.

    17. Re:x86? by Spit · · Score: 2, Interesting

      The demarcation of storage and RAM is a legacy constraint forced by hardware limitations. Ubiquitous 64-bit and SSD will blur and eventually totally eliminate this separation.

      --
      POKE 36879,8
    18. Re:x86? by shutdown+-p+now · · Score: 2, Insightful

      x64 is a Microsoft marketing term. Please stop using it. The architecture is x86-64.

      Pray tell, why not amd64 then - the way it was originally marketed by the inventor when it was released?

      Last I checked, there's no definite established term for this, anyway, and x64 is the shortest while still being vendor-neutral. Even if Microsoft came up with it first (and are you sure they did, really?), so what? I don't understand how it is a "marketing term" for them, as they don't market it.

    19. Re:x86? by Pentium100 · · Score: 1

      Because flash based SSDs will be as fast as DRAM? In reading, writing and latency?

    20. Re:x86? by nog_lorp · · Score: 1

      Or, while everyone is nitpicking...

      Why not refer to it by "AMD's original designation for this processor architecture, 'x86-64'"?!

    21. Re:x86? by SEE · · Score: 3, Insightful

      Tell me, if they announced an intention to do a SPARC core, would you assume they meant a 32-bit version? How about POWER?

      x86 is just as 64-bit as they are.

    22. Re:x86? by Spit · · Score: 1

      Who said anything about flash-based SSD? I said SSD as in SOLID-STATE NON-VOLATILE STORAGE. Regardless, flash now is faster than CPU registers were not so long ago.

      --
      POKE 36879,8
    23. Re:x86? by Anonymous Coward · · Score: 0

      Yeah, we all know that. Like you're going to get x64 confused with a RISC system? the x86 part goes without saying. You know, like the aquaducts and such.

    24. Re:x86? by coxymla · · Score: 1

      x64 is a short, sweet, unambiguous term that is much less unwieldy than x86-64. Even if Microsoft was the first to use it (and AFAIK they certainly don't market it, I've only ever seen it in the filenames of MSDN ISOs) what about that makes it verboten for the rest of us?

    25. Re:x86? by nxtw · · Score: 1

      The demarcation of storage and RAM is a legacy constraint forced by hardware limitations. Ubiquitous 64-bit and SSD will blur and eventually totally eliminate this separation.

      Bullshit. The difference between flash storage and RAM is hardly a legacy constraint; the hardware limitations are very significant.

      Flash devices are many orders of magniture slower than DRAM. Flash devices have very limited write cycles, whereas DRAM does not. Flash devices operate on large (erase) block sizes - starting at 64KB. This is many orders of magnitude higher than RAM, which is addressed by the byte. The erase block size is also much larger than the 512 byte sectors used in hard drives. Note that most consumer flash-based devices present themselves as block devices with 512 byte sectors.

      On flash, data can be initially written in chunks much smaller than the erase block size, but once written, an entire erase block must be erased at the same time.

      It can be useful for data on secondary storage to be accessible as if it were in memory. Modern operating systems already provide this functionality - see mmap(2). However, the usefulness of exposing a large slow block device's entire address space is limited unless a high-performance application actually randomly uses all that data - and if that's the case the frequent page faults caused by the lack of DRAM for caching would result in lower performance than just using standard read/write operations.

    26. Re:x86? by Pentium100 · · Score: 1

      Sorry, my bad. I read SSD and immediately thought about flash. While flash is faster than CPU register were some time ago, it is slower than DRAM (even SDR) is now. In the future, flash may become faster than PC66 RAM, but it will probably never become as fast as the DRAM technology of the day.

      Also, if you addressed all storage using the same addresses as RAM, how would you handle removable media (especially the one that can have different sizes)?.

    27. Re:x86? by Spit · · Score: 1

      I never said that SSD would eliminate RAM either, which in turn will not eliminate on-die cache or registers in the forseeable future. When you've got a practically infinite address space you may as well use it.

      --
      POKE 36879,8
    28. Re:x86? by Spit · · Score: 1

      Sure is lack of imagination in here...

      --
      POKE 36879,8
    29. Re:x86? by moosesocks · · Score: 1

      x64 probably started as a verbal colloquialism. x64 rolls off the tongue much easier than x86-64.

      --
      -- If you try to fail and succeed, which have you done? - Uli's moose
    30. Re:x86? by Spit · · Score: 1

      I would be brave enough to say that in the not-too-distant future, 1GB storage will be about as common as 1KB RAM chips are now.

      --
      POKE 36879,8
    31. Re:x86? by ppanon · · Score: 1

      True, but Level 1, 2, and 3 CPU caches are all much faster than DRAM too, and yet they share the same address space. Theoretically, you could just make the SSD byte addressable and have your "main memory" DRAM act as a Level N+1 cache for the SSD. If you want a file system you run a RAM disk :-) That would make systems come up much faster from a power-off mode, but system resets would be more challenging to pull off.

      Alternatively, you could also think of it as the SSD being a big persistent swap partition for your main DRAM memory. That second approach might be easier to implement at first, since the first approach is more of a paradigm shift in how you organize your O/S. It might also make it easier to deal with flash mem's limits on repeated writes to the same location.

      --
      Laissez lire, et laissez danser; ces deux amusements ne feront jamais de mal au monde. - Voltaire
    32. Re:x86? by Spit · · Score: 2, Funny

      x86 is more than x64, so it's better right?

      --
      POKE 36879,8
    33. Re:x86? by Anonymous Coward · · Score: 0

      Storage hierarchies will always exists. The models we use on top of them will continue long after the current technologies are going.

    34. Re:x86? by Pentium100 · · Score: 1

      While I don't have much interest in making my PCs boot faster (I reboot them when I want to change some non-hot-plug device or something goes bad, in both cases the whole process takes way longer than it takes for my PC to boot afterward), I don't see how it would make systems boot faster than they do now.

      If you mean that on power-on the data is copied from the ssd/hdd to the RAM then we already have that function - it's called "hibernate". If the PC tried to use the ssd/hdd without copying the data first, it would be very slow until the data is cached to the RAM.

      Alternatively, you could also think of it as the SSD being a big persistent swap partition for your main DRAM memory.

      How does that work? Don't we create swap partitions on slower but bigger devices so that the PC can write data when it runs out of RAM?

      What would be the difference from what we have now? Now the OS handles swapping to disk, then some chip on the motherboard would handle it? Except that the chip would have to be like the OS and know which processes to swap out. How it would even know that the system is running out of RAM? AFAIK RAM does not have a FAT or some other file system so as to be able to tell how much free space is there.

    35. Re:x86? by Spit · · Score: 1

      You can by SSD now which consists purely of the same RAM sticks as on your motherboard. This is the idea that I'm getting at. So how do we handle it? Seems a bit wasteful to limit that massive bandwidth through legacy storage interfaces, so put it on the RAM bus. Also a bit redundant to double-handle it via antiquated filesystem IO, so map it directly.

      See where it's going...

      --
      POKE 36879,8
    36. Re:x86? by Pentium100 · · Score: 1

      SSD, that consists of RAM sticks, that is put on a RAM bus, that is accessed by the same address and has no file system. Wouldn't that just be a RAMdisk?

      And if you want it not to lose data while the PC is turned off - do not turn off the PC, just leave it on stand-by (with an internal battery).

    37. Re:x86? by c6gunner · · Score: 1

      Sure is lack of imagination in here...

      *sigh*

      You know, I get the same, or similar, response every time I talk to a proponent of any type of bullshit.

      "You don't see how Elvis could still alive? Gee, you sure are closed minded ..."

      Accusing people of being closed-minded or unimaginative seems to be the equivalent of saying "I have no evidence and no clue what I'm talking about, so I'm going to attack you just so you'll shut up".

    38. Re:x86? by toddestan · · Score: 1

      What about a NAS box? I'm considering building one using commodity PC parts, and when you can have a 4GB disk cache for $40, it's tempting. Though on the other hand, my desktops are kind of dated, and having a NAS box with twice or more ram of any computer it would be serving files to would be completely redicilious.

    39. Re:x86? by Spit · · Score: 1

      Back it up to floppy.

      --
      POKE 36879,8
    40. Re:x86? by Spit · · Score: 1

      Look man, extrapolating SSD into an argument about flash vs SDRAM just shows a lack of imagination. I'll see you in ten years.

      --
      POKE 36879,8
    41. Re:x86? by cryptoluddite · · Score: 1

      Well if you're talking about SPARC it would be the x64%4 architecture.

    42. Re:x86? by Anonymous Coward · · Score: 0

      Actually, it's Super Troopers styled shit.

    43. Re:x86? by setagllib · · Score: 1

      Easy - you already have a separation between volatile and non-volatile storage in all operating system kernels. It doesn't matter whether the underlying technology is the same - in fact you can deliberately blur the line by using part of your RAM as a virtual disk (tmpfs + file + losetup in Linux, memory-backed vnode in FreeBSD).

      --
      Sam ty sig.
    44. Re:x86? by setagllib · · Score: 1

      That's not quite true - the CPU's MMU handles some housekeeping on used RAM. However that's none of the motherboard's business, especially with memory controllers being integrated into the CPU these days. And even that information is far too limited to implement page replacement, which is still the responsibility of a sophisticated kernel.

      --
      Sam ty sig.
    45. Re:x86? by Pentium100 · · Score: 1

      So you say that the OS would still have to do swapping whether the hdd is mapped to RAM address or not. So what would be the point of mapping if the OS (and the CPU) still has to swap pages in and out of the hard disk?

    46. Re:x86? by setagllib · · Score: 1

      No, the number represents how far it is from perfection. Perfection is when there is nothing left to take away. The ultimate CPU will be x0. I'm going to trademark it ahead of time.

      --
      Sam ty sig.
    47. Re:x86? by dunkelfalke · · Score: 1

      These go to eleven.

      --
      "It's such a fine line between stupid and clever" -- David St. Hubbins, Spinal Tap
    48. Re:x86? by MrMr · · Score: 2, Funny

      No that was last time, when his shit turned its current color.
      Get back to him in a couple of years for something really weird.

    49. Re:x86? by smallfries · · Score: 1

      No, it shows that the poster that you are arguing with understands the different physical constraints between volatile and persistent storage. He also understands that we can make external storage look like RAM already, and the reason that we don't do so is that abstraction would kill performance for most applications that need to be aware of the distinction.

      You have nothing in response other than "blah blah imagination I'll be right in ten years". Yeah, course you will sunshine. As we progress down the fab sizes I'm sure that the distinction that volatile memory only needs to store a charge for a tiny amount of time (true looking back through DRAM all the way to mercury delay lines) where-as persistent storage needs more power to flip a state in some sort of field, ie magnetic.

      But of course, that's lack of imagination and physics will be drastically altered in the next ten years. I can't understand why nobody has seen you for the visionary that you are...

      --
      Slashdot: where don knuth is an idiot because he cant grasp the awesome power of php
    50. Re:x86? by Simetrical · · Score: 1

      The demarcation of storage and RAM is a legacy constraint forced by hardware limitations. Ubiquitous 64-bit and SSD will blur and eventually totally eliminate this separation.

      SSD is still orders of magnitude slower than RAM. The only way the distinction is going to go away is if someone comes up with persistent storage that's as fast as RAM but as cheap (per gigabyte) as disk. There's no reason to think such storage exists even in principle, unless you're living in a future where everything is made for free by solar-powered nanorobotic universal assemblers or something (and therefore don't have to worry about price).

      Fast, cheap, persistent: pick any two.

      --
      MediaWiki developer, Total War Center sysadmin
  6. Netbooks? by Hognoxious · · Score: 4, Funny

    You aren't allowed to call them netbooks, didn't you get the subpoena?

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    1. Re:Netbooks? by Anonymous Coward · · Score: 0

      I have always liked "subnote" better than "netbook." I think it describes these things better.

      (I'm using a Mini 9)

    2. Re:Netbooks? by syousef · · Score: 1

      I have always liked "subnote" better than "netbook." I think it describes these things better.

      Why? You're in the navy?

      --
      These posts express my own personal views, not those of my employer
  7. ah gamers... by emj · · Score: 5, Funny

    My Intel 855GM handles xterms very well, recently they have become very wobbly slimey when I drag them around in Gnome, other than that everything is fine with my integrated chip.

  8. Re:Linux is for steers and queers by Anonymous Coward · · Score: 0
  9. I don't see the point. by jd · · Score: 3, Interesting

    Surely a better design is to produce a series of very small, highly specialized, very fast cores on a single piece of silicon, and then have a layer on top of that which makes it appear to be an x86, ARM or whatever.

    One reason for having a bunch of specialist cores is that you don't have one core per task (GPU, CPU or whatever), but rather one core per operation type (which means you can eliminate redundancy).

    Another reason is that having a bunch of mini cores should make the hardware per mini core much simpler, which should improve reliability and speed.

    Finally, such an approach means that the base layers can be the same whether the top layer is x86, ARM, PPC, Sparc or a walrus. NVidia could be free to innovate the stuff that matters, without having to care what architecture was fashionable that week for the market NVidia happens to care about.

    This is not their approach, from everything I'm seeing. They seem to be wanting to build tightly integrated system-on-a-chip cores, rather than having a generic SoaC and an emulation layer. I would have thought this harder to architect, slower to develop and more costly to verify, but NVidia aren't idiots. They'll have looked at the options and chosen the one they're following for business and/or technical reasons they have carefully studied.

    If I was as bright as them, why is it that they have the big cash and I only get the 4 digit UID? Ergo, their reasoning is probably very sound and very rational, and if presented with my thoughts could very likely produce an excellent counter-argument to show why their option is logically superior and will produce better returns on their investments.

    The question then changes as follows: What reasoning could they have come up with to design a SoaC unit the way they are? If it's the "best" option, although demonstrably not the only option, then what makes it the best, and what is it the best at?

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    1. Re:I don't see the point. by MrNaz · · Score: 1

      "what architecture was fashionable that week"
      Yea, because CPU architectures come into and go out of fashion all the time.

      --
      I hate printers.
    2. Re:I don't see the point. by hawk · · Score: 4, Funny

      >Finally, such an approach means that the base layers can be the
      >same whether the top layer is x86, ARM, PPC, Sparc or a walrus.

      So much for running linux on it!


      BIOS ERROR.
      NO OPERATING SYSTEM FOUND.
      THE WALRUS HAS EATEN THE PENGUIN.

      hawk

    3. Re:I don't see the point. by SpazmodeusG · · Score: 1

      Surely a better design is to produce a series of very small, highly specialized, very fast cores on a single piece of silicon, and then have a layer on top of that which makes it appear to be an x86, ARM or whatever.

      Yes, they call that a modern x86 CPU.
      They don't create the x86 instruction set in hardware anymore. They just have a translation layer in hardware that takes the x86 code and runs it on another type of hardware (usually a RISC core).

      The internal execution core of this type of CPU [a modern x86] is actually a "machine within the machine", that functions internally as a RISC processor but externally like a CISC processor. The way this works is explained in more detail in other sections in this area, but in a nutshell, it does this by translating (on the fly, in hardware) the CISC instructions into one or more RISC instructions. It then processes these using multiple RISC execution units inside the processor core.

      http://www.tek-tips.com/faqs.cfm?fid=788

      Incidently CISC had a big advantage over RISC. Each instruction typically did more and so for a given program a CISC computer will typically use less code. Saving cache, memory and bandwidth. So modern x86 CPUs have the advantage of the dense code of the x86 instruction set and with their instruction decoders the advantage of an efficient RISC core.

    4. Re:I don't see the point. by Anonymous Coward · · Score: 0

      Since modern CPUs have to cache decoded instructions anyway, and the only concrete advantage of the x86 instruction set (not counting binary compatibility, which only matters for lazy vendors) is code density, surely we can devise an even more space-efficient instruction set. We're no longer limited to processing assembly code on vintage-1980 workstations, much less crafting object code by hand. Hell, we'd probably be better off with compressed Java or .NET bytecode.

    5. Re:I don't see the point. by Anonymous Coward · · Score: 0

      No the decoders don't run THAT far ahead. In fact they can only decode as many instructions ahead as the pipeline is long. Otherwise they'd run into problems when the code branches to somewhere completely different. So the cache really is benefitted by CISC code.

      As for a more space-efficient instruction set, yes you could create one. It wouldn't be Java or .NET bytecode that's the most efficienct though. You'd want to have a language that has opcodes of various length with the most common operations a short length and the least common a long bit length (this is most optimal as per Shannons information theory).
      If you created such an architecture it'd be very efficient in terms of memory.

      It wouldn't run all the x86 code out there though so you'd probably want to have a decoder on the CPU that takes x86 instructions and converts them to native code on the fly.
      Oh wait a minute...

    6. Re:I don't see the point. by setagllib · · Score: 1

      Modern CPUs perform branch prediction (partly guided by the binary itself) and will import a weighted portion of the possible code following a branch. There is still a cost to branching of course but it is far lower than it was in the old days - it's down to barely more than a static jump. Also, that's why Profile Guided Optimisation makes such a big difference even to an already "optimised" binary.

      --
      Sam ty sig.
    7. Re:I don't see the point. by jd · · Score: 1

      I've thought of that myself. Picture a cluster of programmable cores, such that each core's instruction set matches the interface for a Java class. Also picture having a stack of registers on that core, such that each instance of a class is equal to a given set of registers. Inheritance is simply taking an unrecognized opcode and forwarding it to another core.

      In principle, this would give you the ability to run a Java program as a physical machine, similar to the way the iWarp and Transputer worked, but using an object-oriented design rather than a functional design.

      The communication overheads in such a system are high, the complexity of the decoding is enormous, and you'd have to essentially rebuild the computer every time you reprogrammed it, but it should not be possible to run an object-oriented program any faster than such a machine could. (Using a mix of hardwired coding and microcode programming will give you massive performance gains over a general-purpose computer, as the individual cores need not be Turing-complete and can therefore be optimized for some specific subset.)

      Working on this design has, however, completely convinced me that there are huge benefits to being extremely lazy and just using general-purpose mass-produced components.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
  10. Can you just imagine?! by Phizzle · · Score: 4, Funny

    A Beowu.... aww fuck it.

    --
    I will not be pushed, filed, stamped, indexed, briefed, debriefed or numbered. My life is my own.
  11. They should just go with ARM by BikeHelmet · · Score: 4, Interesting

    They should just push ARM heavily. ARM is doing great right now. Companies like Texas Instruments are pushing the architecture heavily, and there's high demand.

    Linux ARM support is blasting ahead, thanks to projects like the Beagleboard.

    On top of that, a while ago Microsoft said they were developing an ARM version of Windows. Although we won't see it right away, in a couple years that'll open up even more options.

    If they push ARM hardware heavily enough, software will follow. Heck, the software is already coming along, so they just have to market the hardware properly.

    Most people won't know the difference between a linux MID and a windows MID. Both have "Email", "Instant Messenger", "Calendar", "Web Browser", etc., and if you need a new program you just download it... Nobody would even think of installing software off a CD, so most "Why won't this work?" scenarios won't even come up. It'll just look slightly different.

    And once a couple game devs follow - or heck, a program like Google Earth - it won't be long before oodles of software is being ported, and the ARM-x86 barrier breaks down.

    1. Re:They should just go with ARM by Darkness404 · · Score: 1

      This doesn't work for one main reason. ARM just isn't marketable. No one when looking at specs is going to go for the laptop with 1 gig of RAM and a 600 Mhz ARM CPU compared to one with a gig of RAM and a 1.6 Ghz Intel CPU. Sure, the megahertz myth is busted, but for the average consumer, the more Ghz, the more appealing the choice.

      --
      Taxation is legalized theft, no more, no less.
    2. Re:They should just go with ARM by Paradigm_Complex · · Score: 1

      If they push ARM hardware heavily enough, software will follow.

      (1) It doesn't matter how hard they push ARM, all the legacy x86 software won't magically work.

      (2) I don't think Nvidia has what it takes to push Microsoft hard enough to get a mainstream version of Windows or Office on ARM, and without Windows goes a huge number of people who refuse to try something different.

      (3) Nvidia's strength - the GPU - is best used in games. Without focus there, there is no reason to go with Nvidia's solution over Intel's or AMD's or Via's. Without Windows that just isn't going to happen.

      ARM just doesn't make sense for Nvidia. They don't have much choice but to stick with x86 - either work with something like the Nano or Atom, or roll their own.

      --
      "A witty saying proves nothing." - Voltaire
    3. Re:They should just go with ARM by Anonymous Coward · · Score: 0

      all three of your points are completely pointless in the market this stuff is for

    4. Re:They should just go with ARM by Locklin · · Score: 1

      Nvidia's GPU also has VDPAU which means that the GPU can do nearly all of the work decoding video, even HD x.264. So pair it with a weak little power-efficient cpu and you have an excellent video player. Intel can't do that.

      --
      "Knowledge is the only instrument of production that is not subject to diminishing returns" -Journal of Political Econom
    5. Re:They should just go with ARM by maxume · · Score: 1

      I would think, for 'PC' applications, that the 80% of the market that wants binary compatibility is a much bigger problem.

      If you show someone a $500 laptop that has great battery life, and you show them the laptop doing a good job doing the tasks they want it to do, some of them won't care that the $700 has a bigger number (and I think this is going to get more true, as computers are 'way fast enough' for a greater and greater percentage of tasks).

      --
      Nerd rage is the funniest rage.
    6. Re:They should just go with ARM by Erich · · Score: 4, Interesting
      Sigh.

      The reason to go with x86 is because ARM is just as shitty of an architecture.

      Seven supervisor modes now? Horrible page table format? Have you seen what they are planning for 64-bit addressing?

      Even more importantly than the CPU architecture, the ARM busses are typically very low performance. And if most of the time is dealt with memory movement, having a better bus dwarfs what's going on with the CPU.

      So, in the end, you have slow cores. Intel knows how to make x86 fast. And, as they are starting to show, they can make it low power also. ARM has yet to show a fast core. They don't use that much power, but if "netbooks" are low end laptops instead of high end cell phones, a few watts is fine.

      Oh, and did I mention that x86 cores are x86 compatible? That makes the software barrier to entry a lot lower.

      To compete with Intel, you have to be better. A lot better. For very low end, ARM is better, because all that matters is leakage power, and after that all that matters is power for very small processing. At a higher level of performance, ARM is different, but perhaps not better. Maybe the ARM architecture has some features which make it less complex to implement than x86. But at the end of the day if nobody is making ARM cores that spank x86 cores, x86 will win. Didn't you learn this from PowerPC? Don't you realize the same thing will probably happen to ARM except at the extremely low end? And even there, if Intel decides to start licensing 386 synthesizeable cores, how long do you think ARM7 and ARM9 will last?

      --

      -- Erich

      Slashdot reader since 1997

    7. Re:They should just go with ARM by Ninnle+Labs,+LLC · · Score: 1

      So no one buying a netbook is going to want to run x86 software? I call bullshit on that.

    8. Re:They should just go with ARM by BikeHelmet · · Score: 1

      Don't market mhz, then. Market capabilities.

      If the ARM laptop has "plays 1080p" slapped on the front, and the Atom laptop has "plays 720p" slapped on, which do you think the consumer will buy? What if the ARM laptop has a "16 hour battery life", and the Atom laptop has a "9 hour battery life"? What if the ARM laptop costs $50 less?

      I just hope the salespeople educate them a bit on the differences. :P Linux vs Windows needs to be explained... as Dell seems to have pointed out.

    9. Re:They should just go with ARM by Anonymous Coward · · Score: 2, Interesting

      On top of that, a while ago Microsoft said they were developing an ARM version of Windows.

      They already have one. It's called Windows CE.

      At my work we dev .net on win CE on arm. It works quite well believe it or not.

    10. Re:They should just go with ARM by BikeHelmet · · Score: 4, Interesting

      Yes, the ARM architecture is horrible and slow - but it also integrates really easily with other kinds of chips.

      How long have we had ARM SoCs with CPU, GPU, MMU, plus a dozen other chips all in a single chip? An ARM "CPU" (SoC) isn't just the CPU part. It also has dozens of other chips inside it for accelerating specific types of processing, and all with remarkably low power consumption.

      ARM is less complex than x86. Both ARM and x86 are moving towards integrating more and more stuff on a single die. Which do you think will work better - the simpler architecture (though not vastly simpler) with rapidly improving speeds, or x86? ARM has more experience in this area. They'll win.

      You say to compete with Intel "you have to be better", but your opinion on what makes a CPU better is flawed. Power6 stomped Intel for performance. Even today for FPU stuff it's still about 100% faster than Core i7(per ghz - and it scales up to +5ghz on air), and I don't see it dominating the market at all!

      ARM will win for these reasons:
      -Lower cost.
      -Lower power consumption.
      -Much smaller size. (smaller devices appeal to many people)
      -Similar/better performance for specific tasks(like video decoding/recording).
      -Efficient software base.
      -Appealing to device manufacturers.

      Yes, x86 is compatible with everything under the sun, but everything under the sun is incredibly inefficient, and designed to run on desktop dual/quad-core systems.

      You're arguing about what the consumers want, but you're thinking like a techy. If you put an x86 program next to a well-coded ARM program, they'll both run just as responsively, and at the end of the day, to end users, responsiveness is what determines "speed".

      x86 may "spank" arm, but consumers think Vista is "slow" because it takes 30 seconds to delete a file that took 0.5 seconds in XP, and it requires more RAM. They don't give a shit that the kernel may be 5% more efficient. :P They don't care that they have a 2.6ghz dual-core CPU rather than a 2.6ghz single-core CPU, if it feels slower than before. (because of flaws with software)

      All this puts the importance on software quality rather than the hardware. But software is easy, for ARM. ARM has no super-fast desktop line that would spur the growth of inefficient crapware.

      Don't you feel lucky that we are to have tons of open source developers making quality software that runs on ARM devices? And piles of device manufacturers ready to push linux/FOSS software on these devices?

      Too bad there's so few x86 device manufacturers pushing linux/FOSS. More support and demand would really spur growth of efficient software for netbooks and the like - but we do have Dell, I guess. :P

    11. Re:They should just go with ARM by dunkelfalke · · Score: 1

      only x86 has already been there more than a decade ago. remember cyrix media gx?

      --
      "It's such a fine line between stupid and clever" -- David St. Hubbins, Spinal Tap
    12. Re:They should just go with ARM by downix · · Score: 1

      Ah, so you're a MIPS fan!

      Or SPARC perhaps?

      --
      Karma Whoring for Fun and Profit.
    13. Re:They should just go with ARM by Anonymous Coward · · Score: 0

      >They should just push ARM heavily. ARM is doing great right now. Companies like Texas Instruments are pushing the architecture heavily, and there's high demand. when people push arm, i usually respond by kicking leg.

    14. Re:They should just go with ARM by Anonymous Coward · · Score: 0

      Umm... 30 seconds to delete versus 0.5 seconds is a more efficient kernel??? You must mean a 60 times less efficient one...

      (hint: the file is on disk, in a filesystem, which is a driver, part of the ... kernel! The kernel is the only software that can delete the file (well, except for trojans or rootkits with administrator rights that duplicate the functionality to mess around with files without anybody knowing about it...)).

    15. Re:They should just go with ARM by Erich · · Score: 1
      Look, I would love nothing more than ARM to win. Because if ARM wins, it opens up the door for innovation in architecture. And that's good for everyone.

      But they won't. Intel can make x86 chips that are low cost and low power consumption. And ARM is rapidly approaching implementation requirements that mean it's not as simple as you think it is. They overcrowded the opcode space, making decode hard. Thumb2 means serial decode problems, just like x86. And the whole anything-shifted-by-anything field on every instruction isn't so great for decent OoO pipelines. You end up having what amount to microcoded instructions with the move-multiples. So you end up doing basically the same things Intel would do -- breaking up instructions, speculative decode blocks, microcoded instructions, etc -- and Intel has been doing it longer and better.

      Two operating modes, seven supervisor modes, various page table formats, thousands of instructions (when you consider addressing modes and condexec and ARM/THUMB and Neon and VFP and...)... do you really think that ARM is *really* all that much more simple than x86?

      ARM ain't no Alpha. ARM ain't no MIPS.

      So maybe ARM has a niche in ARM7 and ARM9 class tiny, licensable, synthesizeable 32-bit microcontrollers that run at speeds of up to 200Mhz, but I'm afraid ARM won't be able to compete with Intel when it comes to gigahertz-level processors.

      Oh, and as for thinking like a "techy", in the end the only thing that matters is "Does it run my office suite" and "does it run my games". And the answer is likely "no" if you have an ARM. Because at the end of the day, nearly everyone runs Microsoft Office and nearly everyone ends up with some games compiled for x86.

      Like I said, I hope I'm wrong. It's much, much, much better for my career and the future of computing if ARM starts doing great. But I don't think I'm wrong. Too bad, too.

      --

      -- Erich

      Slashdot reader since 1997

    16. Re:They should just go with ARM by Anonymous Coward · · Score: 0

      There's something I never understood about ARM, and it seems nVidia could change this easily enough if they so desired: one of the special features commonly added to ARM chips is "Jazelle", which is intended to speed the performance of Java bytecode. Why not make an ARM chip that replaces Jazelle with something intended to speed up x86 emulation? x86 machine code is way more common than Java bytecode, after all.

    17. Re:They should just go with ARM by Anonymous Coward · · Score: 0

      Yeah, Apple went through a lot of trouble to bust that myth and now they use it for their own marketing. At what point does a myth become real?

    18. Re:They should just go with ARM by Darkness404 · · Score: 1

      Well, first there is the fact that the average consumer just isn't going to be playing any kind of Hi-Def videos. With wimpy SSDs, no Blu Ray (or CDs/DVDs for that matter), that would mean that the person would have to be downloading videos. Which, streaming through Netflix is an option if it is a Windows laptop, but if it is Linux, thats not even a possibility. With very few video downloading services that offer downloads in full 1080p for any reasonable price, we can assume these people are torrenting videos, and if they are torrenting it, they are obviously rather informed, if they are informed, then why do they need the sales guy in the first place?

      --
      Taxation is legalized theft, no more, no less.
    19. Re:They should just go with ARM by CAIMLAS · · Score: 1

      Well, except that CPUs are not frequently being marketed by clock cycles anymore. Yes, the Atom has several variants ranging from 1GHz to 1.9GHz (iirc). But there are 1GHz ARM chips, and many of them have multiple cores.

      Look at the desktop market of today to see where the portables will be tomorrow. There's little distinction between the various dual core CPUs, or the various quad core CPUs. ("a fraction of a GHz difference? that's hardly anything - why spend $30 on that when I could spend it on getting -four- cores at a similar clock?")

      From my rough guess, half the ARM CPUs out there are multicore and over 1GHz. The emerging technology is in the low-end: netbooks, and other similarly powered devices. Think of the SheevaPlug. ARM SoC platforms totally stomp the Atom platform (just without the comprehensive and annoying marketing) on every single attribute that matters (ie, on everything except 'x86 compatible').

      Like every other technology, geeks will get ahold ARM systems again due to their superior qualities, and it will catch on. Who doesn't want faster, smaller, cheaper, more power efficient devices? Green is in, baby. This will catch on, commercially, and it'll take off - likely throwing MS under the bus in the process, if they aren't able to get an OS and productivity products on the market by the time ARM starts gaining ground on the 'general computing' ground again.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    20. Re:They should just go with ARM by CAIMLAS · · Score: 1

      Except, there are dozens of ARM SoCs out there for the cost of just an Intel processor, with comparable clock speeds. These SoC have integrated cores with specialized processing, to allow for faster-than-Intel function on the vast majority of tasks which traditionally need a fast CPU in x86 land: audio, video, 3D, I/O, USB, and so on.

      Intel has always taken the "generic modularization" route, while ARM CPUs have taken the "lots of integrated specialization". For quite a long time, this made Intel more appealing. However, in the long run, ARM's approach is likely to win out: you can only make a processor so fast and generic before you hit a bottleneck, and have to start integrating anyway.

      Intel is faced with having to redesign now. Sure, they can probably do it, but it's going to be costly to change 'paradigms'. ARM CPUs, on the other hand, are already integrated, with each of the integrated components largely improving independently and at-pace with the amazing performance/clock increases seen in the ARM CPU. In my mind, ARM processors/SoC have the clear advantage - if only because they can benefit from each other's advancements and have true competition.

      Put another way, you can get a -developers- version of a 1GHz ARM SoC w/ 512M, ethernet, and USB2, half the size of a cell phone charger, using 1W, and costing $100. (The SheevaPlug.) How far is Intel from being able to offer something like this? Also note that the Tegra has been shown to consistently outperform the Atom.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    21. Re:They should just go with ARM by CAIMLAS · · Score: 1

      I do remember those, I think. They were a response to Intel's MMX, weren't they? MMX, and GX, and AMD Now! and so on, all required a substantial CPU redesign, if I recall correctly. The same has bee ntrue for all subsequent Intel and AMD chips: yes, they've offered improvmenets and changes in that area, but it's been a costly venture each time.

      Changes -improvements - like that are trivial on ARM.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    22. Re:They should just go with ARM by BikeHelmet · · Score: 1

      Vista seems to have a software glitch where sometimes the file deletion dialog sits there for ~30 seconds before it deletes the file.

      This is a software glitch. The dialog isn't doing anything. It's just sleeping for a half-minute before it deletes it. :/

      Extensive benchmarks show that a lot of software runs about 5% more efficiently on Vista. Games aren't part of that software - mostly just office programs and things that benefit from slightly better prefetching.

    23. Re:They should just go with ARM by BikeHelmet · · Score: 1

      No, ARM isn't MIPS - and yet it seems to be selling better than it.

      This isn't something two people can accurately predict. We'll just have to wait and see what the developers, device manufacturers, and consumers end up doing.

      My bet's on ARM. ;)

    24. Re:They should just go with ARM by Anonymous Coward · · Score: 0

      Memory systems count for much more in either case. Multi-processor multi-layer caching subsystems which are very non-trivial to do (having verified a L2 dual core hardware coherent cache - it has about 20k pipeline states to check). A small increase in miss rate will stall your CPU while doing Fetches (it is easy to get 90% stalls/NOPs in these cases).

      The ISA is rarely that important. Intel cleaned up thru its process technology - increasing frequency - not a great ISA.

      ARM is barely a processor. A modern RISC is what you really want. PowerPC or MIPS, etc.

      Other than that its what software is avail for 90% of users.

    25. Re:They should just go with ARM by dunkelfalke · · Score: 1

      nope, sorry. cyrix media gx was an x86 system on a chip and the reason why national semiconductors bought cyrix in first place.
      after a couple of years of mismanagement they threw away the rest to via, renamed media gx to geode and sold this part to amd.

      media gx was a very interesting and a tightly integrated cpu. it contained a 32 bit x86 cpu, a graphics processor and a soundprocessor. both graphics and sound were emulated to the system as a real vga and a real soundblaster pro.

      this system on a chip came out in 1997 and was pretty popular in set top boxes and subnotebooks.

      --
      "It's such a fine line between stupid and clever" -- David St. Hubbins, Spinal Tap
    26. Re:They should just go with ARM by dpilot · · Score: 1

      Actually, technical considerations may well have very little to do with it. It's more likely all in the licensing practices and considerations. ARM tends to be very liberally licensed and very well accepted on those terms. Intel tends to be very tight on the licensing, wanting much more to own the world than to work with it. It's possible that Intel will come up with licensable x86 cores, but not very likely, or at least not very likely on decent terms.

      The real battle will probably not be Intel vs ARM, but Intel vs ARM + ARM's partners. That's a bit of a different game.

      --
      The living have better things to do than to continue hating the dead.
    27. Re:They should just go with ARM by Anonymous Coward · · Score: 0

      But you are not considering the whole point from developers point of view. As Balmer said: "Developers, Developers, Developers !"

      Software development is not about efficiency anymore. It is about speed of development and distribution. That's what agile development and web apps are about. Sure responsiveness is important to consumers, but there are many other influencing factors.

      ARM will win for these reasons:
      -Lower cost.

      Lower costs, where ? I would think it's about the hardware. But the real factor is software development cost. Nobody puts an effort in handmade assembler algorithms anymore. It's all about python, java, ruby and the likes. For ARM really having an advantage here assembler code or at least compiled code would be the way to go. But this just won't happen.

      -Lower power consumption.

      Probably a plus. But as you stated in your post:

      An ARM "CPU" (SoC) isn't just the CPU part. It also has dozens of other chips inside it for accelerating specific types of processing, and all with remarkably low power consumption.

      So a special device for video decoding, audio decoding etc. at remarkable speed, low power consumption, but the next codec can not be supported. Just tell this a customer in desperate need to use the new VoIP app.

      -Much smaller size. (smaller devices appeal to many people)

      Yes a 400 Mhz ARM is smaller than a 2 Ghz x86. But look at the Power6 vs. Core i7 issue.
      power 6: 340 mm2 Die-Size, 750 Million Transistors
      coreI7: 263 mm2 731 Million Transistors
      I don't see the size issue here.

      -Similar/better performance for specific tasks(like video decoding/recording).

      Yes, but only with specialized components. Vendor lock, patent issues, new codecs, flexibility ...

      -Efficient software base.

      Sure, for calculators. But that just doesn't matter anymore

      -Appealing to device manufacturers.

      Yes, but not to software developers

  12. A Sure Path to Failure by Louis+Savain · · Score: 1

    So, instead of forging ahead with novel parallel processor technology, Nvidia thinks that the way to go is to copy last century's dinosaur CPU? It's enough to make a grown man cry. Whoever is in charge of research at Nvidia should be given the boot. What a waste of talented engineers! But it's not too late, Nvidia. Click on the link below and do the right thing. Otherwise, Otellini will tear you a new one and you know it.
    How to Solve the Parallel Programming Crisis

    On a different note, did not Nvidia recently say that the world is moving away form the CPU? I am beginning to think that Nvidia is either scared or bluffing. Otellini made a comment last week to the effect that Nvidia needs a CPU in order to build a GPGPU heterogeneous multicore processor and now there's all this talk about an Nvidia x86 coming out in a couple of years. Does Otellini call the shots at Nvidia? I am not so sure.

    Nvidia is right that the days of the CPU are numbered but so are the days of the GPU. The reason is simple. Neither CPU nor GPU provides a universal or homogeneous solution to the parallel programming crisis. The heterogeneous route is pure folly too, if only because it does nothing to solve the crisis. In fact, it makes it worse because it combines two incompatible parallel models on the same dye. A match made in hell.

    There is way to solve the crisis but it involves neither CPU nor GPU. Think pure MIMD vector processing. That's where Nvidia should invest its processor R&D resources, all of it. That is, if it wants to dominate the parallel computing industry for the next several decades. Intel would not know what hit it until it's too late. Big money is at stake. BIG.

    1. Re:A Sure Path to Failure by georgewilliamherbert · · Score: 1

      The Nvidia GPUs are large MIMD vector machines - look at the specs, and what they're doing with CUDA. That they're mostly actually used to draw texels of monsters and walls and bullets in flight doesn't mean that they're not a highly capable general purpose vector processor...

      Many people are (almost certainly correctly) stating that Nvidia wouldn't do that if they didn't think they had to, or didn't think that this would make them more money / market penetration than not doing it. Suggesting that sticking a small x86 on the corner of their big graphics chips is somehow an architectural black hole is silly - they're not dumb, they're chasing their market. The CPU won't slow anything else down.

    2. Re:A Sure Path to Failure by Parallax48 · · Score: 1

      Although I love the idea of a core designed specifically for parallel processing, it is another case where you are asking all programmers to switch to your model before you can make any money. Just like the x86->Arm switch, it is going to be very very very hard.

      I prefer the approach currently taken by Intel and AMD to process x86 instuctions out of order, with multiple instructions per clock and then reorder the results. Split this over a small enough number of cores to comprehend and throw some great tools at it and everything works fine.

      There are some awesome tricks being used to make serial x86 instructions parallel, and I imagine there is a lot more room to improve in that area before we need to reinvent the entire instruction set. Compilers are getting better and better at enabling this parallelism. Don't give up on x86 / x64 just yet!

    3. Re:A Sure Path to Failure by GameMaster · · Score: 1

      Sure, Nvidia would love to see the world move away from general purpose processors and focus more on vector processors like their GPUs, but they know that, for the short-term, general purpose processors are a market reality (as a side note, Nvidia executives are also known for making absurdly overstated/arrogent statemtents as well). This decision has nothing to do with parallel processing. In fact, it has nothing to do with advancing the state of the art for anything other than power consumption/cost per unit of calculation. They're aiming for a lucrative market. If you want to put a positive spin on it, the money they make by blowing Intel out of the water in the netbook market (assuming they do) can help fund more research in parallel processing on the high end.

      --

      Rules of Conduct:
      #1 - The DM is always right.
      #2 - If the DM is wrong, see rule #1
    4. Re:A Sure Path to Failure by Louis+Savain · · Score: 1

      The Nvidia GPUs are large MIMD vector machines - look at the specs, and what they're doing with CUDA. That they're mostly actually used to draw texels of monsters and walls and bullets in flight doesn't mean that they're not a highly capable general purpose vector processor... Many people are (almost certainly correctly) stating that Nvidia wouldn't do that if they didn't think they had to, or didn't think that this would make them more money / market penetration than not doing it. Suggesting that sticking a small x86 on the corner of their big graphics chips is somehow an architectural black hole is silly - they're not dumb, they're chasing their market. The CPU won't slow anything else down.

      Are you kidding me? If Nvidia's GPUs were pure general purpose MIMD vector processors, there would be no need to bundle them with traditional CPUs.

  13. This is good for competition by Anonymous Coward · · Score: 0

    This is good for competition

  14. Re:Linux is for steers and queers by Anonymous Coward · · Score: 0

    Wow, you mean Obama can walk on water, heal people with his hands and change water to wine too? That is amazing! Who knew that the president really is the most powerful man in the world.

  15. He makes some sense by Anonymous Coward · · Score: 0

    If you KNOW the x86 will be deployed with a good GPU, you can skip the MMX, SSE, and other recent ISA additions presumed to be patent-encumbered. The question is whether you can do without some of the other OS support features in the ISA which are too recent to be freely implemented.

    However, the hurdle here is that x86-compatible no longer means i386 to most people. Pre-compiled OS and application binaries may now unfortunately assume the presence of many newer ISA extensions and fail to work without them. Once you have to recompile, how much benefit is there to x86 versus ARM or anything else in the lightweight/embedded market?

  16. Well, that is what netbooks do by SmallFurryCreature · · Score: 0

    NOT all PCIe slots are created the same. The one in laptops is fairly small and there is no reason it can't be smaller still, after all, the connector standard is just there so all cards can be produced to fit in all slots. PCIe itself doesn't care what the slot is like or even if it is a slot at all, you could solder it on. Then it is integrated but still a real graphics card.

    What the above parent by the way is talking about has really nothing to do with integrated or not but just with crap implementations. Usually because a laptop maker takes shortcuts and uses fake busses or once that are hopelessly scaled down until you are left in a "modern" machine with less throughput then a telex machine.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

    1. Re:Well, that is what netbooks do by Jorophose · · Score: 4, Interesting

      Or external PCIe. I've been waiting for that. The PCIE standard has it specified, just nobody wants to make stuff for it. Think of it this way, you come home, you plug in a box (with its own PSU) into your laptop, and you can now game on your laptop with whatever cards you had put in that box. When you're done, unplug everything, switch your resolution/drivers if necessary, and go.

    2. Re:Well, that is what netbooks do by Anonymous Coward · · Score: 0

      ExpressCard is external PCIe.

      Asus showed off an external video card a couple years ago, but it seems to be vapourware. You could also get one of these if you have a lot of money to burn for such a thing.

    3. Re:Well, that is what netbooks do by zdzichu · · Score: 3, Informative

      Dude, external PCIe is available in laptop for years, it is called ExpressCard. And suprise, it's even used for external graphics: http://www.tomshardware.com/reviews/vidock-expresscard-graphics,1933.html

      --
      :wq
    4. Re:Well, that is what netbooks do by Anonymous Coward · · Score: 0

      Love to, 'xcept some manufacturer has decided to decree that PCI-E ports are verboten on a particular low-margin CPU.

    5. Re:Well, that is what netbooks do by sfraggle · · Score: 1

      From what I understand, most interest in external PCI Express has been related to server environments and virtualization. I worked on this product a couple of years ago but unfortunately it was canned. Not really something you can use with a laptop though anyway :-)

      --
      were you expecting to see a sig here? perhaps you'd rather see the inside of an ambulance!
    6. Re:Well, that is what netbooks do by mkaushik · · Score: 1

      Take a look at this: http://www.nvidia.com/page/quadroplex.html These things hold graphics cards externally, though they're only for desktops. There are models that hold as many as four external graphics cards. They're not cheap though.

    7. Re:Well, that is what netbooks do by default+luser · · Score: 1

      Yes, but at 1x PCIe 1.0, it's a mere shadow of what video demands today. The 1x lane on the ExpressCard slot (2Gbps after 8/10 encoding) was intended to be an inexpensive, nice upgrade over PCI (Cardbus), and nothing more. It makes me wish thay had planned-ahead, and pushed 2x into the slot for a little more cost.

      It has one other serious problem: due to bandwidth limitatations, you can't route the images from the video card expansion back to the laptop LCD, so this is not a "portable" solution. Even though the expansion box is very small, you must connect it to an external display, and that is NOT small.

      The good news: ExpressCard 2.0 will be released in 2010, and will feature USB 3.0 and PCIe 2.0, so the data rate will jump to 4.0 Gbps. That might actually be enough to make this concept work.

      --

      Man is the animal that laughs.
      And occasionally whores for Karma.

    8. Re:Well, that is what netbooks do by nedlohs · · Score: 1

      Yes, I want to have to plug an external PCIe device into my cell phone in order to see the caller ID number on the screen as it rings.

    9. Re:Well, that is what netbooks do by Anonymous Coward · · Score: 0

      2.5 Gbps? Pathetic.

  17. limits of 32 bits by hawk · · Score: 1

    I ran into a limit with 32 bits more than 10 years ago.

    My Fortran compiler was Cray derived (Lahey, iirc), and I had dynamically allocated a huge array. They were in some way bit-addressed, leading to a crash.

    I turns out that my adviser's machine had more memory (512Mb) than any of their own test machines.

    The workaround at the time was static allocation, which made the code faster, anyway.

    hawk

  18. Not to worry by Anonymous Coward · · Score: 0

    There is no need to worry that Nvidia will be making crappy crappy main processors (much like intels crappy crappy video processors). Intel didn't try to emulate anyones technology (we could tell that right away), however Nvidia is trying to emulate intels technology, for which they need a license. Now the big N pissed the big I off bigtime a few years ago, and the prospects of a license coming from the big I are far far less than 0. So no need to worry. It will never happen.

  19. nVidia releases ... by cybereal · · Score: 1

    This just in, nVidia announces world's first netbook to require not one but two separate AC adapters at all times. Other features include built-in vacuum cleaner noise generator, and thermal pubic hair remover.

    --
    I read the script, and I think it would help my character's motivation if he was on fire. -Bender
    1. Re:nVidia releases ... by cptnapalm · · Score: 1

      "thermal pubic hair remover"

      Dude! I've been looking for one of those!

  20. A little off topic but I want to know by erroneus · · Score: 1

    It seems that everything is moving in the direction of operational efficiency. More instructions per cycle, less power draw, faster and more efficient buses among processor, memory and peripheral devices are among important issues being focused on.

    But what ever happened to Moore's law? Are we already outside of its prediction? Has the chain been broken? I thought we would all have 5GHz machines running ice-cold by now but some of the latest and greatest stuff is a mere 1.6GHz atom processor based sub-notebook. Is power and speed out of vogue or is it just not as possible as it once was and so people are drawing attention in other directions hoping people have forgotten about Moore?

    1. Re:A little off topic but I want to know by Animats · · Score: 2, Interesting

      But what ever happened to Moore's law? Are we already outside of its prediction? Has the chain been broken?

      Effectively, yes. The problem is not cost per gate and wafer real estate per gate, which continue to decrease. It's heat dissipation per unit area. I've been to semiconductor talks where there are charts of increasing heat dissipation with lines marked "room temperature", "soldering iron", "nuclear reactor", and "surface of sun". The trend is clear and not encouraging.

      The effect is that computers of equivalent power continue to get cheaper (basically, a computer now costs $299 or less) but performance is leveling off.

      At the high end, a few years ago there was talk of a cyrogenic petaflop supercomputer, but the justification wasn't there. That thing would have dissipated 4KW at liquid helium temperatures, with very elaborate cooling. Just getting signals out of the liquid helium without letting heat in is tough; the I/O has to be optical.

      Density continues to improve for devices that don't use much power, like flash memory. But for CPUs, we're reaching the limits.

      Some fundamental limits, like the size of atoms, are not that far away, but those haven't been hit yet. There's about an order of magnitude to go.

      3D devices, with more layers, are promising in terms of density, but they're not cheaper, and the heat problem gets worse.

    2. Re:A little off topic but I want to know by V!NCENT · · Score: 0, Troll

      But what ever happened to Moore's law? Are we already outside of its prediction? Has the chain been broken?

      Effectively, yes.

      What the hell are you talking about? Moore's Law say that performance will double each year and it still does. Even if it doubles by packing more cores, then it still does.

      --
      Here be signatures
    3. Re:A little off topic but I want to know by Anonymous Coward · · Score: 0

      Moore's Law is about transistor density/number of transistors on a chip, it has nothing to do with gigahertz or power (although higher transistor density is the most efficient way to get mo(o)re power). Theoretically, you could get more transistors on a chip by enlarging the chip, but there's a ceiling on how big a chip can be because of things like heat, power and increased latency from one end of the chip to the other. That's why everyone gets excited about lower nanometer chips, because if the transistor is smaller you can fit more of them on a chip (meaning higher transistor density, yay!).

      But yes, incredibly, we're at a point where software has to catch up to hardware. There has been no "killer app" that have made people demand more computing power (unless you count virii+stupid people purchasing new computers when their old ones simply needed a re-install), so instead the computers are shrinking. Until someone invents something with huge requirements that everyone needs, we're going to see more Macbook Airs and Netbooks. Not that there's anything necessarily wrong with that - I'd be excited if someone combined projection keyboards technology+projectors to make a "projected touchscreen", so that the whole device could be the size of a small mobile but without the squinting and thumb cramping - they could even include a fold-able card as the projection surface that attaches to the projector via retractable/hinged arms for stability and easy focus .

    4. Re:A little off topic but I want to know by downix · · Score: 1

      Helps if you know Moores Law:

      Transistor count will double every two years.

      Nothing about Ghz/Mhz or that jazz. Yes, we have twice the transistor count we did two years ago, more cores per-chip, since we hit a wall in regards to frequency. If you can't go up, you go out.

      --
      Karma Whoring for Fun and Profit.
    5. Re:A little off topic but I want to know by Tycho · · Score: 1

      It may help to keep in mind that essentially every requirement and feature for a modern OS has not been significantly improved since 1980. No, not the 1980's, the year 1980. As the processing power at each grade of computing power has increased, that grade of computer has run an OS that has been improved gradually until it ran a modern OS. Since then, there has not been much advancement in what features to expect out of an OS. This may be why there is little difference in OS level features between Windows NT4, 2000, XP, Vista, and 7. Granted, OS stability and user security have improved from NT4 to XP. However, Windows Vista and Windows 7 seem to add very little to the mix in the end. Consider it a problem of diminishing returns.

      Adding cores is also is not the same as a speed up and an improvement in efficiency of the core you already have. Adding cores may help for certain problems, but there are still problems that are inherently single threaded and thus single core. Going up intelligently and going out intelligently both important.

      --
      Impersonating Tycho from Penny Arcade since before there was a PA.
  21. That's the interesting question... by Anonymous Coward · · Score: 0

    If you produce great GPU cores with all the SIMD goodness you need, does it really matter if your x86 core has SIMD extensions? Just run the basic x86 code and let the media driver software offload the rest of the processing to the GPU cores.

    The real question here is what kind of software is going to be hosted, and what ISA requirements does it really have (and which cannot be easily changed). It may still be easier to cross-compile existing x86 software to a slightly reduced ISA than to port legacy stuff to ARM? Only time will tell, I guess.

  22. They should open the drivers first by BESTouff · · Score: 2, Insightful

    Problem is that more and more netbooks are sold with linux, and NVIDIA drivers integration in any distro is less than stellar. Contrast that with Intel hardware where everything is well supported by all vendors.
    Unless they open their drivers, this platform will be Windows-only so even their lower-end models will be hampered by the Windows Tax.
    That won't go very far.

    1. Re:They should open the drivers first by Anonymous Coward · · Score: 0

      Problem is that since nvidia drivers won't work well, I won't use linux. I guess the zealots win... but it must be a hollow victory if nobody uses their "pure" operating system. Maybe the kernel devs should not specifically try to make closed source drivers break.

  23. I was just wondering... by sybreon · · Score: 1

    Would NVIDIA be able to do a Transmeta? Seeing that their GPUs are supposed to be more and more CPU-like, maybe they could translate the whole x86 instruction set in software?

    1. Re:I was just wondering... by Anonymous Coward · · Score: 0

      Maybe I'm not as educated on programming and cpu architectures as I would like to think I am, but...

      Seeing the several mentions of ARM and it's pros and cons made me think of something that may or may not be relevant here. Dynamic Recompilation recompiles part of a program in real time, with the obvious intention of speed optimization.

      I am thinking instead of licensing a patent to produce x86 clones; why not hire some highly skilled programmers to create an x86 dynarec engine for the Nvidia GPGPU or for the ARM RISC cpu instead?

      I don't have much experience with RISC in general, but it seems to me that dynarec would excel on that architecture.

  24. It probably will use an Intel CPU core by cheesybagel · · Score: 1

    Intel recently announced it was making the Atom CPU core available for SoCs made in TSMC. NVIDIA has dealings with TSMC, as they only do design and outsource manufacturing. So theoretically NVIDIA could just use an Atom core as a base and slap a GPU on it, much like they did with Tegra with an ARM core.

  25. The Palyar Commander's Brother-in-Law says... by Dogtanian · · Score: 1

    It's a black day indeed when Warcraft 3 can't run at full resolution on a laptop produced only a year ago.

    Yes it can! I have the screenshots to prove it!

    (Had to turn the detail down slightly though...)

    --
    "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
  26. Rather have this... by DaVince21 · · Score: 1

    I wish that some company would combine ARM and x86 into one chip already, so that a complete migration to a more efficient line of processors becomes possible.

    DISCLAIMER: I know nothing about the feasibility of this.

    --
    I am not devoid of humor.