Slashdot Mirror


AMD Quad-Core Opteron (Barcelona) Tech Report

crazyeyes writes "AMD has been very tardy with Barcelona. Countless AMD fans have eagerly awaited a new processor. As the day draws closer, TechARP takes a look at the upcoming quad-core AMD Opteron. Is there more to it than just its four processing cores? Will it be the Intel-killer that AMD promised long ago? From the article: 'AMD is in the same boat as ATI. Delays after delays of their long-awaited Barcelona core not only ensured the dominance of their rival, Intel, in the desktop processor market, it also ensured that Intel would be the only choice for those who want a quad-core processor. Although that wait will end in August, 2007 when the Barcelona is finally launched, it remains to be seen if AMD's new processor will be able to inflict serious damage to Intel's dominance.'"

201 comments

  1. AMD is in the same boat as ATI by Anonymous Coward · · Score: 0

    Actually, ATI is now in AMD's boat, which is literally the same boat.

    1. Re:AMD is in the same boat as ATI by Anonymous Coward · · Score: 0

      They're literally in a boat?

    2. Re:AMD is in the same boat as ATI by OrangeTide · · Score: 1

      What boat is this?

      --
      “Common sense is not so common.” — Voltaire
    3. Re:AMD is in the same boat as ATI by Wavicle · · Score: 1

      No, they're literally in the same figurative boat.

      Quite trying to be pedantic.

      --
      Education is a better safeguard of liberty than a standing army.
      Edward Everett (1794 - 1865)
    4. Re:AMD is in the same boat as ATI by MrNaz · · Score: 1

      Quite? I'm not sure what you're trying to say.

      --
      I hate printers.
    5. Re:AMD is in the same boat as ATI by guisar · · Score: 1

      As a former long time ATI/AMD fanboy (never owned Intel until last year, never owned nvidia yet) I can say I think the boat is the Titanic.

  2. Intel's sever / workstation chip sets suck by Joe+The+Dragon · · Score: 2, Insightful

    Intel's sever / workstation chip sets suck next to the ones for Opterons / AMD FX cpus.

    FB-DIMMS cost a lot and need alot more power to run then DDR ECC ram and the Intel chipsets have very few pci-e lanes. The nforce pro chipsets have the lanes for 2 full x16 slots with 2 x4 slots and pci-e lanes for on board sata / sas raid with x4 lanes left over that are some times used for pci-x slots.

    Also the amd chips have better cpu to cpu link.

    1. Re:Intel's sever / workstation chip sets suck by PDXNerd · · Score: 1, Insightful
      It depends on the solution you are looking for. Besides, when you say Intel's chipsets suck compared to AMD, you're comparing nforce pro chipsets, which is Nvidia, not AMD. Try looking at Nvidia's chipsets for Intel's CPUs and make the same comparison.

      On another note, this is considered news? There was, quite literally, nothing to see here. It was a couple of paragraphs with a flashy new slide in it. It lost all credibility when this line was written:

      Of course, Intel is also rushing out a similar solution, in the form of their V8 programme. So, it is a race to see which company will be the first to release an 8-core platform. AMD stands to take some wind out of Intel's sails if they are the first out with their 8-core platform.
      Intel has had an 8-core platform since last summer. Are they talking about "native" quad-core? Does a slight technical difference matter when one exists and one does not exist? How do we know "native" quad-core is better than dual-dual-core-on-a-single-chip?

      Let's discuss this again when AMD comes out with a platform that can be benchmarked.
    2. Re:Intel's sever / workstation chip sets suck by Joe+The+Dragon · · Score: 1

      The Nvidia's chipsets for Intel's CPUs are only for the desktop cpus not for the workstation / sever ones.

      Intel V8 for gaming is a joke FB-DIMMS no cross fire or sli.

    3. Re:Intel's sever / workstation chip sets suck by itzdandy · · Score: 2, Insightful

      No doubt that from a design perspective the barcelona is superior to an intel dual/dual core design. The problems is of course yields and bins. barcelona is a more expensive design because of lower yields from larger slabs of silicone. The only way to overcome that is to make much less complex, lower transistor count cores to up yields. otherwise, make a point-2-point bus working at much higher bandwidths and make seperate cores and glue them together(Intel). Intel will win this game because of better yields and higher profits per CPU because of both yields and higher bins. this is without considering smaller processes and no SOI problems.

    4. Re:Intel's sever / workstation chip sets suck by Maniac-X · · Score: 5, Insightful

      Intel has had an 8-core platform since last summer. Are they talking about "native" quad-core? Does a slight technical difference matter when one exists and one does not exist? How do we know "native" quad-core is better than dual-dual-core-on-a-single-chip?


      Actually it makes a lot more difference than you'd think. This is most evident in caches. Intel's quadcore has two shared L2 caches (one per two cores). AMD has a full L2 cache per core AND a shared 2mb L3 cache. Intel doesn't have an L3 cache on any of their stuff. Besides that, HTT is a lot faster than Intel's dated FSB. More bandwidth and faster aggregate links means that yes, the native quadcore will be a lot better.

      Aside from that, AMD also still has much better memory performance via the on-chip memory controller, and doubled-width op registers from the last gen AMD stuff.
      --
      (A)bort, (R)etry, (I)gnore?_
    5. Re:Intel's sever / workstation chip sets suck by InvalidError · · Score: 2, Interesting

      Native quad-core is better than dual-dual-core because more cores can exchange cache snoop data over CPU-speed internal buses instead of low-speed external buses. Cache snooping quickly kills performance scaling on shared FSB architectures like the P3, P4 and Core 1&2. Since the same FSB is also used for memory IO, cache snooping robs some more of the FSB-limited memory performance on P3/P4/Core-1&2 FSB-based SMP architectures.

      Shared FSB systems do not scale... even Intel knows that. However, dual-dual-core is more profitable short-term and easily more than enough to give AMD a run for its money for a good while longer. Things will get really interesting after Intel's Nehalem materializes in late 2008... perhaps we'll see AMD get one-up'd like they were when Core2 came out last year.

    6. Re:Intel's sever / workstation chip sets suck by gnasher719 · · Score: 1

      '' Actually it makes a lot more difference than you'd think. This is most evident in caches. Intel's quadcore has two shared L2 caches (one per two cores). AMD has a full L2 cache per core AND a shared 2mb L3 cache. Intel doesn't have an L3 cache on any of their stuff. ''

      Very interesting comparison. The way I see it: AMD has 0.5 MB L2 per core, and 2MB L3 shared between four cores. Intel has 4MB L2 shared between two cores, and 4MB L2 shared between the other two cores. Anything where 0.5MB is enough, AMD wins. After that, we have L3 vs. L2 cache where Intel should be slight winner. But once you need a total over 4MB cache, or more than 2MB in one process, Intel is the clear winner.

      Seriously, you blame Intel for not having any L3 cache when their L2 cache is twice the size of AMD's total?

    7. Re:Intel's sever / workstation chip sets suck by PopeRatzo · · Score: 2, Insightful

      It will be an easy decision for many of us. Whichever platform runs our applications the best will be the one we spend our hard-earned cash on. Personally, if the boost in productivity (music and video production) I got when I moved to a dual Xeon and a Core2Duo (2 boxes, of course) is any indication, I'm going to like this proliferation of cores.

      If I could only get my favorite applications (like Logic Pro or Sonar or Wavelab or Nexus or Kontakt or Premiere or After Effects or even Flash) was available in a native Linux version I could run on Ubuntu, I would be ecstatic.

      --
      You are welcome on my lawn.
    8. Re:Intel's sever / workstation chip sets suck by taniwha · · Score: 1

      "silicone"? what are you building exactly ....

    9. Re:Intel's sever / workstation chip sets suck by Anonymous Coward · · Score: 0

      The ultimate arbiter of what platform is "better" is the marketplace.
      AMD has been losing significant server share ever since Intel released a "quad-core" solution.
      You only need to look at AMD's financial results for the past 9 months - it's quite a disaster.

      You need to ask yourself why that is the case if AMD offers better value?

    10. Re:Intel's sever / workstation chip sets suck by itzdandy · · Score: 1

      silicon! so i can't spell!

    11. Re:Intel's sever / workstation chip sets suck by Anonymous Coward · · Score: 0

      You do realize the larger the cache, the slower it is, right? That's why having an L2 cache of .5mb per core is a smart idea.

      Having a large L2 cache is slow, but having each one send info to 2 cores instead of one is going to make the performance that much shittier. The way it's set up for the AMD quad-core, each core is going to be noticeably faster and more efficient for anything that requires up to a 2MB cache.

    12. Re:Intel's sever / workstation chip sets suck by arodland · · Score: 1

      Than. than. than. not then. than.

    13. Re:Intel's sever / workstation chip sets suck by bjackson1 · · Score: 1

      Intel doesn't have an L3 cache on any of their stuff.
      Actually, the Intel Xeon 7100 (Tulsa) series has 16 megabytes of shared L3 Cache. These are only dual core, however.
    14. Re:Intel's sever / workstation chip sets suck by ozmanjusri · · Score: 2, Funny
      The problems is of course yields and bins. barcelona is a more expensive design because of lower yields from larger slabs of silicone.

      So you're saying AMD is likely to go tits-up?

      --
      "I've got more toys than Teruhisa Kitahara."
    15. Re:Intel's sever / workstation chip sets suck by TheLink · · Score: 1

      "Native quad-core is better than dual-dual-core because more cores can exchange cache snoop data..."

      That's not really important at all. As long as something works better in practice, that's the one I'd buy/recommend.

      And from what I see, the Core 2 Duos are a LOT faster than the AMDs and in most cases the better choice.

      2 years ago I'd recommend AMDs over Intel's P4/Netburst crap. But now the Core 2's are stomping all over AMD, and with the recent Intel price cuts, AMD is in for a very bad time unless Barcelona is more than 90-100% faster per core than current X2s. AMD's top of the line is only competitive with Intel's mid range. So AMD has to slash prices of their expensive "rarer" stuff. It actually looks like Intel has spare head room and they're just waiting for AMD to release Barcelona before they respond.

      --
    16. Re:Intel's sever / workstation chip sets suck by cheater512 · · Score: 3, Insightful

      Its not the size that counts, its how you use it. ;)

      Per core cache is faster than shared cache.
      L3 is better as well because it means it can be used to transfer data between cores instead of main memory.

    17. Re:Intel's sever / workstation chip sets suck by itzdandy · · Score: 1

      I'd rather say that AMD likely wont produce the premier chips like they did when the hammers first came out. AMD had such dominant chips then and it really woke Intel up. a japanese commander said something to the effect of "I fear we have woken a sleeping giant" when they attacked pearl harbor, and i think that is exactly what AMD did with intel when they lead the market..

      i certainly hope AMD stays in the game but i doubt they will lead it with barcelona.

    18. Re:Intel's sever / workstation chip sets suck by Anonymous Coward · · Score: 1, Informative

      And from what I see, the Core 2 Duos are a LOT faster than the AMDs and in most cases the better choice.

      On a cost-basis in the low to middle range of the market (basically CPUs in the under $400 range), Intel and AMD are pretty much equivalent price for equivalent performance. As Intel drops prices, AMD drops prices to stay competitive (and vice-versa). There are a few applications where one is better then the other, but on the whole, the two of them are at rough parity.

      Personally, I prefer the NVIDIA + AMD motherboards. While Intel is back in the game with the Core 2 Duo, we're still buying Athlon64 X2s because the C2Ds are still too expensive.

    19. Re:Intel's sever / workstation chip sets suck by DrSkwid · · Score: 1

      > FB-DIMMS cost a lot and need alot more power to run then DDR ECC ram

      It's much cheaper if you just run one of them rather than both.

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    20. Re:Intel's sever / workstation chip sets suck by TheLink · · Score: 1

      They are NOT at parity at all. You're getting it the other way round.

      The C2Ds are definitely a lot faster, since the top X2 is still only as fast as a mid range C2D.

      BECAUSE of that, AMD has little choice but to slash prices, just to become equivalent in price/performance.

      Keep in mind: AMD's top chips are likely _cost_ much more to produce than Intel's mid range chips.

      The CPU/Mem industry is a bad industry to be in - producing capital intensive commodities. In contrast in other markets if you're Number 2 (e.g. "Pepsi") you don't end up losing hundreds of millions unless you do something extremely wrong (poison your customers).

      AMD is in big trouble, but they didn't really do anything wrong. Maybe they made a few suboptimal decisions, but in other industries they'd be making lots of money. The product is decent: reliable, cheap for what it does, and would be considered "top of the line" 2 years ago.

      Y'know, I wish I could get a good chair for the same price as an AMD CPU or even a 7200 RPM HDD. The furniture market is so uncompetitive in comparison :).

      --
    21. Re:Intel's sever / workstation chip sets suck by Doctor+Memory · · Score: 1

      Seriously, you blame Intel for not having any L3 cache when their L2 cache is twice the size of AMD's total? I wonder if bandwidth and contention will take a toll. Obviously, having more cache won't help if you can't access it efficiently. However, it will help with inter-core data sharing. That should help to partially mitigate AMD's L3 cache (since that's one of its main advantages). However, since a CPU can only share cache with one other processor, it won't be as flexible as AMD's approach. You also won't see consistent results, since (presumably) processor scheduling will be dynamic, and there's no guarantee that two cooperating threads will be executed by two cores that share the same cache every time. And the cache-sharing advantage only works with two threads; any more, and you'll be going out to main memory to share data. And that's a long walk, nowadays...
      --
      Just junk food for thought...
    22. Re:Intel's sever / workstation chip sets suck by Anonymous Coward · · Score: 0

      "Keep in mind: AMD's top chips are likely _cost_ much more to produce than Intel's mid range chips."

      Chip manufacturing works a bit differently than you think it does.

      The top and midrange products in AMD's lineup are one and the same from a manufacturing perspective; both come off the same line and are identical in cost.

      Variability in the process means that some chips can be clocked faster, some have less leakage current, and so forth. The testing process identifies the operating limits for each chip and they are sorted into frequency and/or power bins before sale.

      High frequency CPUs sell at a higher price because of the economics of scarcity, not because they cost more to make. Process variation results in a typical bell curve; top bin chips are relatively scarce and can therefore be sold for a higher price even though they cost exactly the same to make as any other speed.

      It does hurt AMD that their top bin chips can't be sold for premium prices due to Intel's price structure, but AMD still makes their best profit per unit in that segment. It's the price pressure on midrange and low-end CPUs which really hurts, because it moves AMD's average sale price much closer to (or below) their production/distribution/marketing costs.

    23. Re:Intel's sever / workstation chip sets suck by InvalidError · · Score: 1

      I was writing more about scalability than actual performance levels. A monolithic multi-core CPU has fewer interconnect bottlenecks than equivalent multi-die/chip implementations and will therefore allow better scaling with core count. Since multi-threaded processing throughput quickly degrades when CPUs start waiting to sync with each other, keeping all delays to the absolute minimum becomes critical as the total system core count increases.

      If we could make a direct comparison between a dual-dual and a native quad (we cannot given the numerous other tweaks that happen between core revisions), we would probably see the native quad lead by 1-20% depending on how much cache trashing and process synchronization the benchmark is generating. There are various ways to avoid costly thread/CPU synchronizations but they require HPC-style tricks few programmers are familiar with. With less costly synchronization, monolithic multi-core CPUs will take a much smaller performance hit from sub-optimal multi-threaded coding.

      Also, even though the Core2 CPUs may lead in raw performance, Athlon64/Opterons often take the lead in bandwidth-constrained situations where Core2/Xeons are simply choking on the shared (CPUs+IO+RAM) FSB... no amount of IPC+MHz domination can save Core2 in that situation.

      I do not care which one has the upper hand now as I plan to stretch my current PC+laptop until late 2008 unless they die before then... but given how messy AMD's business has become after the ATI acquisition, my next system is most likely going to be Intel-based.

  3. That's what you get... by Fyre2012 · · Score: 3, Insightful

    I recall Intel was up in a fuss when AMD released the 64 bit chips. The market 'ooh'd and 'aahd' in delight of the new architecture, supposing that it would herald in a new era of computing in a similar way that the jump from 16 to 32 did.

    The reality of the situation became that the great majority of Athlon64 users were running 32 bit apps, and continue to do so.

    There has yet to be a dire 'need' for 64 bit processing, much to the similar way that there isn't a dire need for more than 4 GB of ram in a desktop machine.

    At work, I'm the Sysadmin for a dedicated hosting company (Linux, mostly Gentoo), and even in that market I don't know of any of my users running 64bit. any performance advantages are outweighed by incompatibilities and plain old PITA to get things working.

    That said, the delay in developing these quad core procs shouldn't put that big a dent in the pocket / market share of AMD simply because it's a niche market that has yet to be widely adopted.

    --
    This is not the greatest .sig in the world, no. This is just a tribute.
    1. Re:That's what you get... by Inoshiro · · Score: 4, Insightful

      "There has yet to be a dire 'need' for 64 bit processing, much to the similar way that there isn't a dire need for more than 4 GB of ram in a desktop machine. "

      1987 called, they want to use more than 64k of RAM. How can they do that without going to 32-bit?

      2007 called back, just to let you know that 4gb of RAM was $150. That's right, $150. At that point, a lot of people are starting to wake up to the unpleasant smell of Intel's PAE (that's right, segmenting, but with 32-bits!). We're also living with the limitations of the 32-bit tlb and the paging methods used. I have a machine here with 4gb of RAM, and it's not unusual because of how cheap RAM is. Linux can run it as 4gb of RAM in 64-bit mode no problem, or I can run in 32-bit with 3.6gb of RAM because the PCI bus and other devices all map to that high region (just like everything above 640k was mapped to devices back in the 20-bit addressing days). Windows 32-bit does the same thing.

      Now, while Linux 64-bit is stable and mature (having been something I've used for 3 years, after which most of the userspace apps have been cleaned up to work), Windows 64-bit is still not all there. Naturally, the proprietary apps will always live in the land of 32-bit. Supreme Commander, a recent DX10 game, has a lot of 32-bit troubles -- running out of RAM and crashing. One of the things you have to do to play it well is add /3GB to your boot.ini, and patch the EXE to enable larger address spaces for userland applications.

      Now, 10 years ago, or even 5 years ago, that would not have been even on the radar screen. Now that you can buy 4gb of RAM for less than $200 (CAD or USD), and now that we have games and applications that need it (beyond the VFS cache; go look at some series SQL applications or scalable web applications), I think you're way off base, and you sound like someone talking about how 64k of RAM (the 16-bit addressing limit) is more than enough for anyone.

      If all you're doing is sysadmining mom-and-pop's micro website that runs fine with 1 or 2gb of RAM, you'll never know this. If you're sysadmining a company that relies on this stuff, and has a cluster of machines that need to be up and running with gobs of RAM to buffer slower disks and backplanes, you'll know better. When normal users can get 4gb of RAM for next to nothing, the server machines better have at least 32gb of RAM.

      --
      --
      Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
    2. Re:That's what you get... by joib · · Score: 2, Interesting


      That said, the delay in developing these quad core procs shouldn't put that big a dent in the pocket / market share of AMD simply because it's a niche market that has yet to be widely adopted.


      From what I've heard, the Intel quad cores are selling like hot cakes for running virtual machines.

      And it's not only quad core, Barcelona also brings a bunch of core improvements, sorely needed to keep AMD competetive with Core2.

    3. Re:That's what you get... by chubs730 · · Score: 1

      4gb of ram for 150 dollars? link me.

    4. Re:That's what you get... by Anonymous Coward · · Score: 0

      1987 called, they want to use more than 64k of RAM. How can they do that without going to 32-bit?

      By going to 16 bit (theoretical limit: 4 MB).

    5. Re:That's what you get... by twistedcubic · · Score: 1

      I got two 1GB sticks (Kingston ValueRam DDR2 667) from Newegg for $33 each, a few months ago. Now the price for the same sticks is $43 each. I should have bought 4GB at the time, which would have cost just $132 + shipping and tax, which is just over $150. I'm sure they have some other memory for a cheap price.

    6. Re:That's what you get... by Anonymous Coward · · Score: 0

      Corsair 1GB stick for $34.99

      Four of those run you $139.96.

      With shipping it comes to $147.88.

    7. Re:That's what you get... by NockPoint · · Score: 1
      I work with CAD problems that often require 64 bits. That being said, as 32 bit software runs faster, fits in less memory, anytime I think that there is a chance a job will run in 32 bits I start there. 64 bit software takes more memory (pointers and such are twice as large), the more memory used fills up cache faster which slows down the job, and takes more expensive machines that there are fewer of and harder to get.

      Multicore CAD isn't there, and is years away from being meaninfully speeded up. So multicores are mostly not of interest. But every application is different, and software to utilize multiple cores is something that people are thinking about and working on now.

      --

      This is not a sig.

    8. Re:That's what you get... by OrangeTide · · Score: 1

      There are advantages beyond >4GB of ram for the AMD 64-bit architecture that you apparently do not realize. 64-bit works smooth as silk on Linux, and you can have 32 and 64 mixed together on those systems and it still holds up. The incompatibility problems you see on Linux are with desktop configurations. Where you need certain closed source firefox plug-ins (and you foolishly installed the 64-bit firefox instead of the 32-bit firefox), or closed source 32-bit drivers for your video card, sound card, etc. In a server environment, 64-bit Linux has advantages over 32-bit and almost no disadvantages.

      The hot thing right now in the market is virtualization, and we've quickly learned that more cores == more virtualization. And the virtualization market is only going to continue to grow. Sysadmins like yourself will quickly find themselves managing fewer large machines that are getting >80% utilization, rather than many smaller machines with 5% to 20% utilization. You will want quad and octo cores to build those big machines for the cost, management, power and performance advantages they offer.

      --
      “Common sense is not so common.” — Voltaire
    9. Re:That's what you get... by fm6 · · Score: 3, Interesting

      There has yet to be a dire 'need' for 64 bit processing...
      As usual, slashdotters are critiquing the computer marketplace as if it were all about them. It's not.

      Of course nobody's running 64-bit applications at home on at the office. Because the dominant player there is Microsoft — whose 64-bit support on the desktop is either lame (try to find even basic drivers for XP-64) or a nightmare (try to run Vista-64 at all!). Can't really run 64-bit apps without a 64-bit OS, can you?

      On the other hand, there's a huge demand for 64-bit apps that run on high end workstations and servers. How do think AMD managed to grab so much market share so quickly? By finding a way to meet that demand ahead of Intel, that's how.

      If it weren't for this demands I wouldn't have a job — documenting x64 servers for Sun. Yes, Sun. Its a big profit center for them these days.

      At work, I'm the Sysadmin for a dedicated hosting company (Linux, mostly Gentoo), and even in that market I don't know of any of my users running 64bit. any performance advantages are outweighed by incompatibilities and plain old PITA to get things working.

      All that tells us is that Gentoo 64-bit support sucks and that you're not supporting any high-end applications. What have you got, some low volume commerce and web presence sites? If you were doing millions of transactions a day, you'd be needing to squeeze all the performance out of your servers you could manage. Which is why the big boys run serious 64-bit OSs: RHEL, SLES, Solaris, Windows 2003.
    10. Re:That's what you get... by RoundSparrow · · Score: 1

      How about 4GB for less than $100? Rebates... but I've gotten for less than $150 without rebates, just wait for sales at Fry's (online or store).

      http://forums.anandtech.com/messageview.aspx?catid =40&threadid=2054141&enterthread=y

      Back to original topic... Intel motherboards really are held back. Why can't I put in 16GB for about 2.5x the price of 8GB?

    11. Re:That's what you get... by Windowser · · Score: 1, Troll

      Which is why the big boys run serious 64-bit OSs: RHEL, SLES, Solaris, Windows 2003.

      You lost all credibility when you included Windows 2003 in that phrase.
      --
      Avoid the MS tax, always buy I.B.M. PC's (I Built-it Myself)
    12. Re:That's what you get... by wall0159 · · Score: 1

      If you're running open-source software, then upgrading to 64-bit is trivial.

    13. Re:That's what you get... by jrminter · · Score: 1

      >> Now, while Linux 64-bit is stable and mature (having been something I've used for 3 years,
      >> after which most of the userspace apps have been cleaned up to work),

      I have been using Mandriva x86_64 for several months now (2006, 2007, and 2007Spring) and basically agree. I still don't have java web start running and some custom apps don't build well, requiring major surgery but it is coming. I understand why so many stayed with 32 bit. I deal with big data sets and have 4GB of RAM so I have been willing to walk (or often crawl) up the learning curve

    14. Re:That's what you get... by Anonymous Coward · · Score: 0

      Supreme Commander is DX9, not DX10. It was supposed to get a DX10 patch later, but that was canceled.

    15. Re:That's what you get... by SEE · · Score: 2, Interesting

      The market 'ooh'd and 'aahd' in delight of the new architecture, supposing that it would herald in a new era of computing in a similar way that the jump from 16 to 32 did.

      The 80386 was introduced in 1985, but the transition to 32 bits in software was really only done in 1995. Windows 3.1, released seven years after the 386, still ran on the 286. Word 6.0 for DOS, released in 1993, still could run on an original 8086.

      The first 64-bit x86 processors were introduced in 2003. If they "herald in a new era of computing in a similar way that the jump from 16 to 32 did", then there won't be a full transition until 2013. Maybe Microsoft will bother shipping a 32-bit OS then, but since any 32-bit machines will be six years old by then, I doubt it. And I'd expect more than four gigs on a desktop to be pretty standard by then, so there'll even be a demand.

    16. Re:That's what you get... by DrSkwid · · Score: 1

      Presumably it's not ECC?

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    17. Re:That's what you get... by Fyre2012 · · Score: 1

      Of course nobody's running 64-bit applications at home on at the office. Because the dominant player there is Microsoft
      Agreed. The single quotes were meant to emphasize the difference between a 'need' and a 'want'. All 64 bit apps have a 32 bit counterpart, however not all 32 bit apps have a 16 bit counterpart.

      All that tells us is that Gentoo 64-bit support sucks and that you're not supporting any high-end applications.
      I can't say the issue was a problem with Gentoo's 64bit support, as I'm certain the issues were most certainly user related. Hence the 'PITA' comment. No, we're not supporting 'high-end' applications, just basic web presence with a few thousand hits per client per day.

      What have you got, some low volume commerce and web presence sites?
      Yes, we don't run anything crazy. Not everyone runs websites that generate millions of hits a day. I'm sure a large market percentage is in the medium, with only a few in need of more than 1 server to run a web infrastructure.

      Which is why the big boys run serious 64-bit OSs
      Not everyone is a big boy, nor has the need to compete with them. They may guide and shape the marketplace, but they arn't the market itself. I thikn you under estimate the little guys and how many there are.

      In my post i did forget about virtualization. We run a number of VDS servers, and the dual cores definitely help keep the costs down, and allow us to maximize the revenue to server ratio.

      My is simply that not everyone needs a quad core, so not being first to market isn't that big a deal. When Intel finally came to market with their 64bit compatibility, it didn't matter that they were later than AMD, because their products were simply better than the competitor.
      --
      This is not the greatest .sig in the world, no. This is just a tribute.
    18. Re:That's what you get... by ACMENEWSLLC · · Score: 2, Interesting

      The problem isn't that we don't need/want 64bit, it's that with Microsoft it is so damned hard to get to 64bit. My AS/400's been running 64 bit for something line 8 years now. The conversion was transparent. With Microsoft, I can no longer use my 32Bit antivirus. I can no longer use my 32bit device drivers and many don't offer 64 bit versions. WTF? Who thought that was a good idea? It doesn't have to be that way. But that's the hold up. I want 64bit so I can run more than 4GB of RAM. But I don't want to replace all my hardware to get there. My system's upgradeable for a few more years now. Once it's time to build a new system, then I'll go 64 bit. BTW - at work, we have VMWare running with 8GB of RAM. I believe this ESX server is 64 bit. We portion it out to serve up 32bit Windows hosts. Yea.

    19. Re:That's what you get... by fm6 · · Score: 1

      Not everyone is a big boy, nor has the need to compete with them.
      No, but they do buy a lot of hardware. Enough so that you shouldn't generalize without considering them. And for them, those extra 32 bits we definitely a "need", not a "want".

    20. Re:That's what you get... by hamster_nz · · Score: 1

      Bzzt: Wrong.

      The 8x86 in 16 bit 'real' mode had a 20 bit address space, allowing access to 1MB. The 24 bit address was the contents of a 16 bit segment register shifted left four bits plus the memory address.

      With a 16 bit address space you can only address 64K of memory, without using page switching or some other form of banked memory. Most 8 bit micros (Z80, 6502...) had a 64 bit address space.

    21. Re:That's what you get... by urbanriot · · Score: 1

      Presumably it's not ECC? Presumably. Most home users and enthusiasts aren't using ECC RAM.
    22. Re:That's what you get... by langelgjm · · Score: 2, Interesting

      Of course nobody's running 64-bit applications at home on at the office. Because the dominant player there is Microsoft -- whose 64-bit support on the desktop is either lame (try to find even basic drivers for XP-64) or a nightmare (try to run Vista-64 at all!). Can't really run 64-bit apps without a 64-bit OS, can you?

      Amen to that. I've run both XP 32- and 64-bit on this machine, and now I'm giving Vista x64 a go. XP 64-bit is a total joke - driver support is almost totally lacking, and now with Vista, I doubt that manufacturers have much incentive to develop for XP 64-bit.

      As for Vista x64, it has been a nightmare. Between crappy/non-existent drivers and all the programs that are either totally incompatible with Vista, or just won't run on the 64-bit version (no Cisco VPN client? WTF??), I'm left thinking I should go back to XP. Either that, or a long waiting game for Service Pack 1.

      I now have a computer that has 1 GB more RAM than it did when running XP (grandparent is wrong on that count, XP 32-bit can't see all 4 GB of RAM because of PCI devices, etc.), but no Bluetooth, suspend-to-RAM that is completely broken, and virtualization that breaks the network driver after a reboot.

      --
      "Anyone who [rips a CD] is probably engaging in copyright infringement." - David O. Carson
    23. Re:That's what you get... by Thorrablot · · Score: 2, Interesting

      Only a fraction of the 64-bit capable desktops and workstations are running 64-bit applications. What's more, there are very few mainstream 64-bit applications out there, despite the fact that for gaming, audio processing, image processing/photoshop apps, and video there would still be performance advantages (memory bandwidth and operation throughput), even if you don't yet have > 4GB of RAM.

      As a veteran of the 16->32 bit transition (for that matter, the 8->16 bit as well), I've been wondering about this, as I would like to start to benefit, both as a programmer and user, of the benefits of 64-bit AMD and Intel CPUs. The comparison is admittedly a bit forced, as developers of 32-bit apps aren't being forced into programming using a segmented architecture as they were in 16-bit days.

      Warning: Readers of the following will have to cope with the fact that the installed OS on virtually all PCs is Windows XP, 32-bit. (Please assume crash positions.)

      This means that MS effectively has these machines "locked in" to 32-bit mode, until the user upgrades their OS to XP-64 (little motive) or Vista 64-bit (or one of the server 64-bit flavors) - wait, this sounds familiar...

      "Sherman set the wayback machine to the early 90's, and the great 16->32 bit transition" You might recollect the introduction of the mighty 386 processor, extended memory modes, the Win32s API, but probably most importantly, killer apps like DOOM loading up their own 32-bit memory managers to sidestep the OS, which really wasn't ready to provide good 32-bit native support. Apps that did this completely took over the system, putting the host OS in stasis until the app was exited.

      Sounds much like the same situation - the majority of users are running an OS that can't tap the full potential their CPU has to offer. So - why aren't we seeing similar application tricks, like those that enabled 32-bit protected mode now? The proposition of writing an application which would sidestep Windows XP 32-bit and set up a mini 64-bit host environment (not really a full OS) is not that radically different, right?

      IIRC, one of the reasons that the 32-bit app could be launched this way was that there was a way to allow it to converse with the 16-bit drivers already installed for disk I/O, audio, video, etc. (I honestly don't know if this is possible to provide a bridge from 64-bit to the 32-bit drivers in the same fashion or not.) This made it feasible to write apps in 32-bit protected mode without having to write 32-bit drivers for every possible piece of hardware in the system.

      I am also certain that XP, and most users, would not be nearly as tolerant of an application taking over the entire OS unless it had the same "quantum leap of experience" that a game like DOOM brought to the PC in it's day.

      All that aside - I do wonder how often Vista 64-bit is being pre-installed on new platforms vs. the 32-bit edition. If users are not strongly encouraged to upgrade now, this will continue to be a barrier to introducing 64-bit applications to the mass market. (At least Vista licensing and distribution is such that an upgrade from 32-bit to 64-bit is free - although I'm not sure how painless it would be.)

      --
      Any sufficiently advanced technology is indistinguishable from a rigged demo. -- James Klass
    24. Re:That's what you get... by drsquare · · Score: 1

      Of course nobody's running 64-bit applications at home on at the office. Because the dominant player there is Microsoft -- whose 64-bit support on the desktop is either lame (try to find even basic drivers for XP-64) or a nightmare (try to run Vista-64 at all!). Can't really run 64-bit apps without a 64-bit OS, can you?
      Linux's 64-bit support isn't up to much either. Whatever OS you use, experimenting with 64-bit is a trail of tears, and of no use to most users.
    25. Re:That's what you get... by jedimark · · Score: 1

      24bit addressing was brought in with "protected mode" on the 286 series and up (and as far as I can vaguely remember, partly on the 80186 too, or am I thinking of the LOADALL instruction?)

      Z80's, despite being the coolest CPU ever relied on external bank-switching hardware, and could only address 16 bits.

      6502's was even more 8 bit -> it didn't have any external 16 bit registers. It did have 16bit immediate addressing, a 16bit mode with an index, and indirect 16 bit addressing mode (using memory contents as a register).

      The 6510 had a little bit of banking smarts built in in the first coupla bytes of IO/memory, which could bank roms, ram expension, etc, but it certainly wasn't linear addressing.

    26. Re:That's what you get... by davetv · · Score: 1

      64K bytes even ... or 2 ^16 = 65536 bytes

    27. Re:That's what you get... by cheater512 · · Score: 1

      Wait...You use Gentoo on 64bit boxes but compile as 32bit?

      No such thing as incompatibilities if your compiling it.

      (I run two 64bit Gentoo servers fyi)

    28. Re:That's what you get... by matthewcraig · · Score: 2, Informative

      Linux's 64-bit support isn't up to much either. Whatever OS you use, experimenting with 64-bit is a trail of tears, and of no use to most users.

      This is very much untrue, as I can attest. I have been running a 64-bit OS since 2003, and it runs like a dream. I can't address all the technical reasons why, but I can say that I have no 32-bit libraries and I'm up and running. No tears here.
    29. Re:That's what you get... by WuphonsReach · · Score: 2, Informative

      2007 called back, just to let you know that 4gb of RAM was $150

      If you'd watch the market more regularly, you'd know that RAM has priced out at anything between $30 per gigabyte and $125 per gigabyte in the past 12 months. Last summer it was around $60-$75 per GB, rising to the $125/GB figure in the fourth quarter of 2006. Right now it's bouncing around in the $30-$50/GB range.

      All depends on what week you buy it and what week your retailer bought their stock.

      I'm hoping that inexpensive ($30 or less) 1GB sticks means that the price is about to start dropping on the 2GB sticks.

      --
      Wolde you bothe eate your cake, and have your cake?
    30. Re:That's what you get... by TheThiefMaster · · Score: 1

      Drivers have to be 64-bit for a 64-bit OS because they have to be able to talk to the devices through physical ram, without any translation. There's no easy way around this, especially for high bandwidth devices like graphics cards.

      32-bit software works because it was ALREADY USING virtual memory, so mapping the app's 32-bit virtual memory to 64-bit physical addresses isn't a whole lot different to mapping to 32-bit physical addresses.

      As for antivirus, I think that one was a difficult choice. Antivirus programs use hooks into the lowest levels of the windows kernel to be able to scan files as other programs request them, so as the kernel was 64-bit it makes sense that everything that hooks into it should be 64-bit as well. It's theoretically possible to hook a 32-bit program into a 64-bit one, but would have been quite difficult to do.

    31. Re:That's what you get... by evilbessie · · Score: 1

      Sorry that's just plain wrong, there is a dire need for 64bits in certain fields, but then if your only concerned with desktop office work then I can see your point, but to any serious number cruncher 64bit has been a long time coming and we can only hope it comes along faster and compatibility gets better.

    32. Re:That's what you get... by Hal_Porter · · Score: 2, Interesting

      Only a fraction of the 64-bit capable desktops and workstations are running 64-bit applications. What's more, there are very few mainstream 64-bit applications out there, despite the fact that for gaming, audio processing, image processing/photoshop apps, and video there would still be performance advantages (memory bandwidth and operation throughput), even if you don't yet have > 4GB of RAM.

      It's not really compelling - plus or minus a few percent. And you need to test two binaries which is expensive. So unless you're absolutely forced to use more than 4GB per process, I think people won't bother.

      "Sherman set the wayback machine to the early 90's, and the great 16-32 bit transition" You might recollect the introduction of the mighty 386 processor, extended memory modes, the Win32s API, but probably most importantly, killer apps like DOOM loading up their own 32-bit memory managers to sidestep the OS, which really wasn't ready to provide good 32-bit native support. Apps that did this completely took over the system, putting the host OS in stasis until the app was exited.

      Sounds much like the same situation - the majority of users are running an OS that can't tap the full potential their CPU has to offer. So - why aren't we seeing similar application tricks, like those that enabled 32-bit protected mode now? The proposition of writing an application which would sidestep Windows XP 32-bit and set up a mini 64-bit host environment (not really a full OS) is not that radically different, right?


      If you really want 64 bit, I don't see why you can't use Windows x64. Sure you'll need to be careful that you have hardware which has x64 drivers, but that's life.

      32 bit Windows already has PAE which is the moral equivalent of a Dos extender. I think Outlook and MS SQL server can use it. So there isn't really a hole for a 64 bit Windows extender.

      I've often wondered what would happen if you could make bootable games - e.g. Linux+ATI and NVidia drivers+a game binary on a LiveCD. But to make it work you'd need to be able to offer much better graphics performance than regular Windows, just like Doom's extended Dos had better performance than regular Dos.

      And given the amount of effort NVidia and ATI spend on Linux drivers compared to Windows ones, I'm not sure that's the case. DirectX is thinner layer over the driver than OpenGL too.

      You'd also need to make a LiveCD which could boot on all PC hardware without any fiddling around with config files, which is probably non trivial given that new PC hardware is lauched all the time and OSs needed to be patched to support it.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    33. Re:That's what you get... by DrSkwid · · Score: 1

      Their ignorance is annoying. Why even mention non ECC ram in reply to :

      "If you're sysadmining a company that relies on this stuff, and has a cluster of machines that need to be up and running with gobs of RAM to buffer slower disks and backplanes, you'll know better."

      Using non-ECC RAM in a 24/7 machine is stupid.

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    34. Re:That's what you get... by CoonAss56 · · Score: 1

      --All that tells us is that Gentoo 64-bit support sucks.

      Sorry, but Gentoo is one of the few Linux distros that 64 bit actually works and works well even for desktop computing. Win2003 can't even use more than 8G while Linux can use 64G or more. Next time before you hit that "enter" key know what what your'e yacking about. Sheesh!

      --
      Won't Bow.....Don't Know How
    35. Re:That's what you get... by DrSkwid · · Score: 1

      Have you done it ?

      Because I discovered that pleny of OS apps wouldn't compile. libdv is one iirc. Kino is another, not the most important apps in the universe but enough to make me waver.

      That said, some fine people have stepped up and done some of the dirty work and done a 64bit multi-media distro : http://64studio.com/

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    36. Re:That's what you get... by CarpetShark · · Score: 1

      Of course nobody's running 64-bit applications at home on at the office. Because the dominant player there is Microsoft


      Dominant? Yes. Total control? No. Plenty of us run 64bit apps, just not on Windows.
    37. Re:That's what you get... by WuphonsReach · · Score: 1

      Linux's 64-bit support isn't up to much either. Whatever OS you use, experimenting with 64-bit is a trail of tears, and of no use to most users.

      If you say "end users", I'd tend to agree with you (although the situation is improving at a good pace).

      But for server users, Linux 64bit has been here for at least 2 years now. The early adopters probably started 3-4 years ago. Things were still slightly shaky 2 years ago, but are definitely pretty solid today.

      --
      Wolde you bothe eate your cake, and have your cake?
    38. Re:That's what you get... by Anonymous Coward · · Score: 0

      The reality of the situation became that the great majority of Athlon64 users were running 32 bit apps, and continue to do so.

      There has yet to be a dire 'need' for 64 bit processing, much to the similar way that there isn't a dire need for more than 4 GB of ram in a desktop machine.

      -------
      You don't understand the benefits... even though the apps are 32 bit, "under the hood" the memory and pci subsystems are 64 bit and benefits from memory/system bandwidth that's an order of magnitude faster. The OS doesn't even see this stuff. It's abstracted. This has huge benefits for professional audio, database, and other io bound applications.

      Put into real-world perspective... I do audio engineering as a hobby. When I got my single CPU AMD 64, and put together a platform based around this, I could handle 139+ audio streams. At that point I ran into CPU speed limitations. The box cost me $800 to build. My buddy that got a Xeon based dual cpu system could handle 34 streams for nearly $3000. His CPUs never hit more than 10%.

      Any more tracks than that that he'd get buffer underruns which manifest themselves as an extremely irritating and loud "crackle". This equates to about 12 tracks in an audio editing program if you are running them through FX or the track is a soft synth. We spent weeks on the phone with software support, hardware support and tuning, and could not get any more than 34 streams going.

      I tried to tell him before he spent the money and he wouldn't listen.

      While you are correct in saying that 32 bit apps don't benefit from 64 bit precision, the plumbing in the opteron and amd 64 systems has benefits for any OS, for moving extremely large amounts of data to and from PCI,PCI E etc cards, the memory, and disk. The OS doesn't even see or care about this plumbing. All it does is address the memory, where the memory controller takes over, or the device registers. At that level the OS doesn't care how the data gets form point a to point b, the system board takes care of those tasks.

      What good is a dual xeon if you can't feed the processors enough data to keep it busy? It's like putting a ferrari engine into yugo. It's only going so fast before you twist off the axles or slide off the road because the rest of the car isn't up to the task.

      I'd much rather have my bottleneck be the cpu for what I'm doing... at least I get to use the cpu I paid for ROFL. AMD systems are and always will be about the balance of the entire system. Intel sells GHz, damn the torpedoes on the system bandwidth. GHz sells and Intel knows that most of the market only cares about that number.

      For DB and professional audio, the opteron always has been and is still superior to Intel for these jobs. It's just too bad people are idiots and don't pick the right hardware for their applications...

      -AC

    39. Re:That's what you get... by Anonymous Coward · · Score: 0

      gentoo has no problems in this space if you'll put in some tinker time, which you'd do anyhow around this with ubuntu.

    40. Re:That's what you get... by Gr8Apes · · Score: 1

      Which is why the big boys run serious 64-bit OSs: RHEL, SLES, Solaris, Windows 2003.


      You lost all credibility when you included Windows 2003 in that phrase. he even lost some by including RHEL and SLES. Solaris, OS400, and other big iron OSes are really the only serious 64 bit apps at the moment.

      The consumer space is about to get its first full 64 bit OS though: OSX Leopard. If you don't think you need 64bit, you haven't done movie editing yet.
      --
      The cesspool just got a check and balance.
    41. Re:That's what you get... by Fulcrum+of+Evil · · Score: 1

      he market 'ooh'd and 'aahd' in delight of the new architecture, supposing that it would herald in a new era of computing in a similar way that the jump from 16 to 32 did.

      It will - the 386 showed up in 1987. It was 5 years before we had a good mass market OS that was 32 bit, and another 7 or 8 to get win2k/XP (the last good version), and this was with a demand for stable, fast 32 bit windows. Right now, we _do_ have 64b OSes, but it's only needed for massive memory apps, which generally run unix anyway. Unless you've got lightwave or pshop, you probably don't need 64b yet.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    42. Re:That's what you get... by PitaBred · · Score: 1

      I'll stick up for Ubuntu here. I've got the 7.04 64bit version, and it works flawlessly on my laptop. Not even a desktop system, a laptop. Linux has been 64bit on the desktop for a while.

    43. Re:That's what you get... by fm6 · · Score: 1

      Actually, you're kind of lucky. You can always go back to the 32-bit XP world, where everything you need is support. Perhaps you'll feel a little silly have paid extra for an x64 when you can't even run 64-bit apps. But if you don't say, "I wish I hadn't bought that" now and then, you're not a true technonerd!

      On the other hand, I'm sort of screwed by the whole Vista debacle. You see, I went out and bought a Motion Computing tablet. Which I love, except those idiots at MS decided not to make the handwriting recognition trainable. When they finally realized that was why nobody was buying tablets, they added handwriting trainability — to Vista! So I can put up with horrible handwriting recognition, or I can confront the nightmare that is a Vista upgrade.

    44. Re:That's what you get... by fm6 · · Score: 1

      You define "plenty" as "everybody I know". I define "plenty" as "a significant fraction of the marketplace".

    45. Re:That's what you get... by Allador · · Score: 1

      try to find even basic drivers for XP-64 For what its worth, this isnt a problem if you're buying new equipment. The big vendors all will support XPx64 or Vista-64 on their workstation class equipment. I know folks that have been running XP x64 for years, with very little in the way of challenges. The key seems to just buy machines that are certified for x64 windows, and there are plenty of these in the tier1 manufacturers.
    46. Re:That's what you get... by Allador · · Score: 1

      Between crappy/non-existent drivers and all the programs that are either totally incompatible with Vista, or just won't run on the 64-bit version (no Cisco VPN client? WTF??), I'm left thinking I should go back to XP. Either that, or a long waiting game for Service Pack 1. What makes you think that Vista SP1 will fix lacking drivers, poorly written 3rd party userspace apps, or Cisco VPN client? Your problem here isnt with MS and Vista, its with your software vendors.

      And who sold you the hardware? What do they say when you call their support and tell them the drivers they ship with the machine doesnt work? Did you get a refund?

      I now have a computer that has 1 GB more RAM than it did when running XP (grandparent is wrong on that count, XP 32-bit can't see all 4 GB of RAM because of PCI devices, etc.), but no Bluetooth, suspend-to-RAM that is completely broken, ... As I asked above, what does your hardware vendor say when you call them and say that their stuff doesnt work because they didnt include the right drivers? I'd send the machine back if they cant solve it.
    47. Re:That's what you get... by toddestan · · Score: 1

      The 80386 was introduced in 1985, but the transition to 32 bits in software was really only done in 1995. Windows 3.1, released seven years after the 386, still ran on the 286. Word 6.0 for DOS, released in 1993, still could run on an original 8086.

      Windows 3.1 had protected mode, which only ran on the 386DX and later processors. This allowed Windows 3.1 to do things like address more than 16MB of memory, and took advantage of other features of the 386. While it's true that Windows 3.1 also ran on the 286, it's much the same how how Vista also has a 32bit version to support older processors. You would be more correct to say that in 1995, Microsoft had finally phased out support for the older stuff with Windows 95.

    48. Re:That's what you get... by wall0159 · · Score: 1

      I'm running Ubuntu, AMD64-bit version. Thus, I haven't recompiled any apps, but have just used the pre-compiled ones.

      I've installed Linux32, which includes 32-bit libraries -- thus I can run 32-bit apps in parallel with 64-bit ones.

      I'm running 64-bit firefox, and have used the wrapper for flash - lets me run 32-bit flash inside 64-bit firefox with no instability - nice!

      I think the other nice thing is that, because only recent CPUs support 64-bit, the apps are compiled to use all the nice features of new apps, so I reckon compiling your own loses some of the advantage..

    49. Re:That's what you get... by langelgjm · · Score: 1

      What makes you think that Vista SP1 will fix lacking drivers, poorly written 3rd party userspace apps, or Cisco VPN client? Your problem here isnt with MS and Vista, its with your software vendors. And who sold you the hardware? What do they say when you call their support and tell them the drivers they ship with the machine doesnt work? Did you get a refund?

      Sorry, I didn't make it clear. This is a 2-year old home-built machine I've upgraded to Vista, but all the components are mainstream. Sure, driver support isn't Microsoft's fault, but what about the suspend-to-RAM (which worked under XP)? Or the virtualization (through Microsoft Virtual PC 2007, which worked under XP)? Or the fact that Windows Mobile Device Center has been fairly horrific so far (ActiveSync used to work just fine, thank you)? And then there's the fact that even if Bluetooth worked, it's less functional than in XP with Microsoft's stack. My god, they even managed to ruin Sound Recorder - it no longer will record WAV files, only 96 kpbs WMA - no other option.

      There's plenty of blame to go around, but I hope that by the time SP 1 comes out, some of these vendors will have gotten their act together, and that there will be improvements to Vista as a whole.

      --
      "Anyone who [rips a CD] is probably engaging in copyright infringement." - David O. Carson
    50. Re:That's what you get... by CarpetShark · · Score: 1

      You seem to like defining my definitions ;)

    51. Re:That's what you get... by DrSkwid · · Score: 1

      You're talking rubbish.

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  4. Intel was never the choice for Quad Cores, since.. by Brane2 · · Score: 2, Interesting

    ... it NEVER MADE _true_ QC CPU...

    All existing Q6xx0 solutions are dual-dual core ie two dualcores sharing same FSB - and that is _NOT_ the same as true QC as Barcelona is claimed to be.

    That difference is enough to make Barcelona the main choice for many core servers even if it were made with old K8 and not the new K10 cores.

    Intel should have true QC chips in a year or so...

  5. So... um... by TheRealMindChild · · Score: 1

    Someone want to buy me one? The only thing I have to trade for it is nothing... but I got a whole lot of it.

    --

    "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
  6. Benchmarks, Price, Release date by nukem996 · · Score: 1

    My gf is going to school in late September and will need a new machine. Shes currently looking at the Intel Core 2 Quad since it just had a great price drop (its $300 at newegg) and may be doing some vmware stuff. I'd love to tell her to wait for AMD bench marks but none are out, there is no release date and even if we had all of that she doesn't want to spend that much on her system so knowing the price would be nice(it would suck to wait till September only for Barcelona to be $800).

    1. Re:Benchmarks, Price, Release date by Dogers · · Score: 1

      The chip being previewed here is the server edition. You'll be wanting to look at the Phenoms, which are apparently being previewed tomorrow on Tech ARP

      --
      I am a viral sig. Please copy me and help me spread. Thank you.
    2. Re:Benchmarks, Price, Release date by nukem996 · · Score: 1

      Well I'll look for it tomorrow at work. I'm not to worried about the chip being a server editor or desktop edition. What ever is the cheapest/best performance is what we want to go for. Hell one of my "desktop" machines uses an IBM Cell Processor.

    3. Re:Benchmarks, Price, Release date by Dogers · · Score: 1

      Well, the server version uses Socket F, the desktops will use AM2/AM2+

      But since you have a Cell system, I guess you're not too worried about upgrade paths ;)

      --
      I am a viral sig. Please copy me and help me spread. Thank you.
  7. Re:Intel was never the choice for Quad Cores, sinc by Joe+The+Dragon · · Score: 2, Informative

    Intel needs more then just true quad core. They also need memory controllers build in the cpus and a cpu to cpu link that does need to use the NB to talk the other cpu and also have so you can have more then one NB like chip like you can on a amd system. With a 2 way amd system you can have 2 chip set links and up to 2 HTX slots.

  8. Better quad-core how? by Kjella · · Score: 4, Insightful

    Intel basicly took a big hammer to any AMD claims of "more affordable quad-core" with their cut today from $530 to $266 for the cheapest quad core, which I doubt AMD can do much better than. I also don't expect them to top the QX6850 for performance right off the bat, since they clearly fail to do so in dual core. AMD is bleeding a lot of money right now and Intel knows to push when it hurts. Right now AMD is staying competitive but with the massive cuts to margins it can't be good for neither profits nor R&D. Intel is not going off on a huge strategic blunder like the PIV or Itanium again, this time they're on the ball and overclocking results suggest they have a lot of headroom.

    The latest batch of ATI cards have failed to compete with the 8800GTX and instead compete against lower clocked cards, presumably again with cut margins. Right now AMD and ATI to me look like two second place companies, and if they try to integrate closer they'll drag each other down. I'm certainly not inclined to buy those two as a package...

    --
    Live today, because you never know what tomorrow brings
    1. Re:Better quad-core how? by bluSCALE4 · · Score: 5, Interesting

      That's because you're not aware of the power of using the GPU in coordination with the CPU. Folding certainly shows GPU as a force not to neglect. You also fail to realize into your comment that quad cores are two dual cores. AMD and Motorola would do this sort of thing to claim next tier technology when in reality they were today's tech on steroids (They often fix GHz speeds with two CPU sets). Now, for some reason, AMD has opted not to do that and we'll see the true worthyness of this strategy with the release of the true quad core.

    2. Re:Better quad-core how? by Jeff+DeMaagd · · Score: 1

      Last I heard, AMD is still a process generation behind. Intel can stuff two dual core dies in a package and still not exceed the TDP of AMD's FX series. I think it may be that AMD just couldn't stuff two dual cores in a package because of the power consumption.

      Motorola is no longer a player in the desktop CPU market, have not been for several years now, I'm curious why you bring them up. Their products were not put into a new notebook computer for over a year and a half now.

    3. Re:Better quad-core how? by Kjella · · Score: 2, Interesting

      You also fail to realize into your comment that quad cores are two dual cores.

      I know, and I also don't give a shit. I got a single-socket mobo and four cores running, you don't. I don't need a special and expensive dual-socket mobo, eATX case or whatnot. That's 99% of the advantage there already. The notion that "real" quad-core makes a big difference is at best disputed, maybe if you have a lot of core-core communication but well... I don't see how that could be a very big bottleneck for normal quad-core use. The Core 2 Quad is certainly not FSB starved, the advantage of 1333MHz over 1066MHz FSB was minimal. The cache tricks you can pull by reassigning the cache of all four processors is also minimal (we've seen this with single-core processors using varying cache sizes). There's just no big compelling reason for such tight intergration unless you're trying to build a cluster with lots of cores working on the same data.

      --
      Live today, because you never know what tomorrow brings
    4. Re:Better quad-core how? by bluSCALE4 · · Score: 1

      Because I was giving examples of pre-GHz companies and how they reached such speeds.

    5. Re:Better quad-core how? by rw63phi · · Score: 1

      I'm curious at to whether any of the more one-sided posters in this thread are defending the value of the stocks they hold.

    6. Re:Better quad-core how? by dpilot · · Score: 2, Informative

      And if it continues to go this well, Intel will push AMD entirely out of the competitive CPU marketplace. Next they'll go after VIA in the low-end, low-power markets and drive them out, and they'll reinvigorate their efforts on IA64, attempting to go after the high-profit Sun and IBM sockets.

      In essence, the desktop will slow and rot, perhaps giving us another boneheaded move like NetBurst.

      You can take all of that with a grain of salt, but remember this... It's been hammered here many times before that a company is in the business of returning value to the stockholders.

      If there is not significant "commodity CPU" competition, it's not worth Intel putting much money into advancing it. Far better to just keep the lines running, keep enough pressure to keep AMD on the ropes, and simply milk it for all its worth. Why bother with unprofitable changes. Process maturation, migration, etc will supply the speed improvements.

      Put the develpment budget where the competition is.

      So if AMD really is on the ropes and quits challenging Intel, forget about the significant improvements you've been seeing.

      --
      The living have better things to do than to continue hating the dead.
    7. Re:Better quad-core how? by LuSiDe · · Score: 1, Troll

      Intel can stuff two dual core dies in a package and still not exceed the TDP of AMD's FX series.
      1) However, AMD's FX series have a far lower idle W (9 versus 35 on Intel, or something).
      2) If you use AMD's X2/EE versions your TDP gets far lower (whereas cost of CPU increases by merely a couple of bucks). If you use X2/EE/SFF you get a TDP of 35W.
      3) Price/performance wise, AMD is still a clear winner, hands down.
      --
      WE DON'T NEED NO BLOG CONTROL.
    8. Re:Better quad-core how? by bluSCALE4 · · Score: 1

      That's why I see as their merger with ATI as so vital to the future of their company and computing as a whole. GPU are an untouched resource. I think that OS's like Vista are going to have to start using GPU's in order to recover ground lost in terms of speed and efficiency. Maybe it's wishful thinking but a lot of people are going to realize that their PC's are garbage when it comes to gaming and that's thanks to Intel's chipsets. If AMD figures out a way to ship a cheap CPU and GPU bundle, things will forever change.

    9. Re:Better quad-core how? by kestasjk · · Score: 2, Informative

      Intel is not going off on a huge strategic blunder like the PIV or Itanium again, this time they're on the ball and overclocking results suggest they have a lot of headroom. Really? I'm not so sure.

      Sooner or later they're going to have to go for something similar to an Itanium processor. Once pushing clock speed runs out, pushing cores runs out, pushing micro-op improvements runs out, they're going to start looking at the instruction set.
      You can bet that if they could change the instruction set at a whim they would have done a long time ago, and the processor would perform much better.

      I think it's inevitable that in the next 10 years things will start to look towards Itanium (or an equivalent), because changing the instruction set will provide a lot of untapped processing power.
      --
      // MD_Update(&m,buf,j);
    10. Re:Better quad-core how? by tknd · · Score: 2, Insightful

      Right now AMD and ATI to me look like two second place companies, and if they try to integrate closer they'll drag each other down.

      I look at it this way: there are only three players, AMD, Intel, and nVidia. Beyond that you're not going to find a chipset, cpu, or gpu worth anything. The only company that (now) has sufficient expertise in all three areas is AMD. Intel has done a good job with centrino, but clearly has no interests and lacks knowledge in the GPU arena (they've only done the bare minimum with their integrated graphics). AMD now has the potential to succeed in providing an all-AMD platform, not just for desktops, but also for laptops. This opens up a new market segment to them that they've had trouble entering IF they can integrate the technologies between AMD and ATI fast enough. The big bonus is if they are successful in the laptop market segment, they no longer need to have be the performance king for CPUs or GPUs. Instead they can focus on being the efficiency king as nobody has bothered to fully tap that requirement. Intel has a pretty good start, but laptops are still only lasting hours on battery. I think they can still do better.

      This will be a good move for AMD if they can manage to pull it off while Intel and nVidia lead in CPUs and GPUs. Let's hope they get through it somehow otherwise we'll be left with nVidia and Intel monopolies.

    11. Re:Better quad-core how? by drinkypoo · · Score: 1

      I think it's inevitable that in the next 10 years things will start to look towards Itanium (or an equivalent), because changing the instruction set will provide a lot of untapped processing power.

      We've been hearing things like this for a lot longer than ten years. I'm not an expert in this area (or any other, I'm more of a jackoff of all trades) but I do have a few observations to make.

      Itanium was supposed to be inherently faster than x86. It hasn't proven to be so. They did load it up with fancy FP hardware and, lo and behold, it was fast. It's still far cheaper to use a group of AMD processors if you want fast FP. And now they're going quad... That's mostly irrelevant though, the point is that even intel has only managed to get modest benefits out of going to VLIW and even then it's not beneficial in all types of computing.

      x86 was supposed to be a limiting factor long before now, and we were supposed to all be joining hands and skipping gaily across the meadow towards the rainbow of RISC. Remember that starry-eyed shit? Today, x86 is by far where the price/performance ratio is for all types of computing except for the very largest clusters (where you save substantial power by using POWER, ironically enough) although pretty much every x86 processor since the Pentium and the Am586 is internally RISCy. But that has not come to pass; the goofy variable-length instruction set with all the different lengths of data and whatnot ends up functioning much like instruction set compression and there are actually substantial benefits, while the [several] deficiencies of x86 and its externally, apparently CISC design have largely been solved through various heroic efforts in the area of register renaming, caching, and superscalar processing. Also, x86_64 largely eliminates the objections to x86, while maintaining backwards compatibility. This is pretty damned magical to me (not literally, but I have almost the same sense of wonder that it works at all, and then that it works so well.)

      I think that if there is a substantial change to be made that it must be more fundamental than what instruction set is used. A shift to asynchronous computing, for example, would make much larger changes in terms of efficiency than we've seen from any individual change so far. But it also requires not just new development tools, but a whole new way of thinking... which is probably why we haven't seen it happen yet (although people have certainly talked about it.)

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    12. Re:Better quad-core how? by Chris+Burke · · Score: 1

      You can bet that if they could change the instruction set at a whim they would have done a long time ago, and the processor would perform much better.

      No. No it wouldn't. It might perform marginally better, as in maybe 1-2%, if you could get rid of all x86 cruft. That number is mostly a WAG, but I've done performance modelling studies to back it up (or more specifically, I've modelled x86 cores without x86 cruft because it's easier, and adding in the cruft for accuracy costs a percent or two on average).

      People thought instruction set was the key to performance back in the early RISC days. x86 was too complex, it could never keep up with the new out-of-order processors RISC ISAs allowed. But then those clever folks at Intel came up with decoding x86 instructions into "micro-ops" that look just like RISC instructions and ever since then x86 has been competitive with RISC. That RISC never took over the market because there was no compelling reason for it to do so when all your apps were already written for x86 architectures that were just as fast.

      So x86 is here to stay. Am I sad because a crufty ugly ISA is what we're going to be stuck supporting forever? You bet. Am I sad because we're dropping some hypothetical performance on the ground by keeping x86? No, not a bit.

      The only way in which you get extra performance out of changing the instruction set is by exposing hardware features not otherwise available. For example, vector processing units, which were added nicely to x86 by the SSE extensions to x86. Or like EPIC tried to do, exposing basically everything from the basic scheduler bundles to the branch predictor, which I think is an example of how trying to put to much emphasis on the ISA can hurt you not help. A lot of computer architecture is done to make a computer run the code that compilers generate quickly, and then the compiler can try to optimize their code for that architecture, forming a feedback loop. Requiring the compiler to generate the code that will make your architecture run fast as a one-way optimization is a bad idea.

      But that's not why Intel came up with EPIC. It isn't why they'd drop x86 like a flaming badger if they could. They came up with EPIC because AMD does not have a cross-licensing deal with Intel for anything non-x86. Whatever ISA they come up with is immaterial next to them being the only game in town producing that ISA. That was the point of EPIC -- locking out all competitors -- but it failed. They are probably not eager to try again soon, especially since most of the Itanium people have been run out of town.

      --

      The enemies of Democracy are
    13. Re:Better quad-core how? by ppanon · · Score: 1

      If there is not significant "commodity CPU" competition, it's not worth Intel putting much money into advancing it.
      Well, if they do that, what's going to happen is that almost nobody is going to buy upgrades. Seriously, remember how after the big upgrade push for Y2K, companies didn't upgrade for 4-5 years and 2004 was a really painful year for computer manufacturers? Multiply that by 4 as companies and end-users only bother upgrading when their old systems fail. Microsoft isn't the only company that can wind up having to compete with it's old products. I don't think Intel really wants to see the market shrink to 1/2 or 1/3 of what it is today, but that's what will happen if they sit on monopoly laurels for too long.

      --
      Laissez lire, et laissez danser; ces deux amusements ne feront jamais de mal au monde. - Voltaire
    14. Re:Better quad-core how? by marnues · · Score: 1

      All those "heroic" efforts to make CISC relevant have mostly been related to transforming the CISC ISA of the x86 into (mostly) RISC instructions though true RISC just doesn't cut it, all current processors have the RISC ideal at heart

    15. Re:Better quad-core how? by marnues · · Score: 1

      The performance gained by removing the cruft of x86 is not really from the more streamlined architecture, but from all the room that's been cleaned up. You could have larger caches or the on-die memory controller that Intel desparately needs.

    16. Re:Better quad-core how? by Chris+Burke · · Score: 1

      The area hit of x86 is not really that severe. It certainly would not allow significantly larger caches, especially since there's diminishing returns on cache size and the L2s on Intel parts are fairly large, anything less than a 50% increase would be irrelevent. Similarly, the area of an on-chip northbridge would be larger than what you could save by removing the x86 decoders. And in either case, it isn't die size that is stopping Intel from putting the northbridge on-chip (AMD already has, and they are much more constrained by die size than Intel who has fab capacity to spare), it's their investment in their current system topology. They'll make the switch eventually (2009 I hear), and it won't have anything to do with making room on the die.

      --

      The enemies of Democracy are
    17. Re:Better quad-core how? by Chris+Burke · · Score: 1

      Well yeah, which means that the ultimate historical answer to the question of "Who won: RISC or CISC?" is "Both!" :)

      --

      The enemies of Democracy are
    18. Re:Better quad-core how? by dpilot · · Score: 1

      I didn't say advancement would stop, nor did I say they would put no money into it. They just wouldn't need to put too much emphasis on it. For instance, instead of leapfrog development groups, they could just have one. Beyond that, there's some amount of performance benefit to be had simply from process learning and shrinks - and that's applicable for both commodity CPU and for whatever the new target markets are.

      The ideal level of "improvement" would match Microsoft's bloat/release schedules, so that as a new OS was ready with heavier requirements, a new CPU would be just-in-time. There would be advancement, just none of this faster-than-curve stuff that we've been getting for quite a few years, now. That kind of timeframe also tends to match corporate replacement cycles, too.

      Then there's the growth in the new target markets...

      --
      The living have better things to do than to continue hating the dead.
    19. Re:Better quad-core how? by kestasjk · · Score: 1

      I thought getting RISC going was better because it allowed the compiler to make all the decisions about instruction ordering and so on. At the moment the processor needs to do a lot of work to line everything up so that things can execute in the most efficient order, because the compiler doesn't have that kind of control. If the compiler did have such control it would be able to make better decisions than the processor about instruction ordering and branch prediction.

      At least, that's what I thought.

      --
      // MD_Update(&m,buf,j);
    20. Re:Better quad-core how? by Chris+Burke · · Score: 1

      You're thinking of EPIC, Intel's ISA for the Itanium line. The instruction bundles generated by the compiler had explicit scheduling information in them. The compiler was basically responsible for everything, and as was discovered, that puts an onerous burden on the compiler that it is not easy for it to meet. Plus exposing micro-architecture in the ISA is a bad idea because when you change the underlying architecture suddenly your program's scheduling and such is all messed up. The decisions the compiler makes for one Itanium chip may not be optimal for another, but it's all hard-coded.

      The idea behind RISC was to actually enable processors that could make the kind of complicated scheduling decisions you're talking about. Out-of-order superscalar processors were considered too hard to do with a CISC ISA. There's still a lot the compiler can do, and compilers started to adapt to the RISC way of doing things. But at any given cycle, it's the processor itself that knows best what resources are available on the processor and what operations can be executed in parallel. RISC is not about exposing the microarchitecture to the compiler.

      x86 processors do the same thing now, breaking the CISC ops into RISC-like micro ops. Also, x86 compilers have generally started to use a RISC-like subset of x86, using the complicated instructions at a bare minimum and mostly using the load/store/op model of RISC. Only with some x86 sugar, like combining a memory operation and an arithmetic operation into one instruction.

      --

      The enemies of Democracy are
    21. Re:Better quad-core how? by drinkypoo · · Score: 1

      all current processors have the RISC ideal at heart

      Right, but what I'm trying to express here is that they ARE internally RISC, and the x86 instruction set functions as a sort of compression of operations, and in the end a highly-optimized x86 processor often ends up being just as efficient as the competition, and sometimes moreso. The ISA is simply NOT as much of a limiting factor as many people believe it to be - and that's the message here. The processor is internally RISC (every AMD processor since the Am586 has been RISC, for example) so you have the benefits of both.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  9. Finally by eneville · · Score: 0, Flamebait

    Finally I can run four things at once on Windows without a block.

    1. Re:Finally by the0 · · Score: 0

      1. Antivirus Scanner
      2. Windows Defragger
      3. Solitaire
      4. ?

      God, so much processing power, so little to do!

    2. Re:Finally by g0dsp33d · · Score: 1

      I can't wait for the 5 core CPUs then so I can run:
      5. Profit!!!

      --
      lol: You see no door there!
    3. Re:Finally by theendlessnow · · Score: 1

      Finally I can run four things at once on Windows without a block.
      Perhaps... if only 4 processors could allow one to get rid of the plethora of worthless modal dialogs... sigh.
    4. Re:Finally by dbIII · · Score: 1

      Finally I can run four things at once on Windows without a block.

      Until you put a CD in the drive. Locks up multiprocessor machines fairly effectively until it works out what to do with it.

    5. Re:Finally by Anonymous Coward · · Score: 0

      Not quite... that is the Operating System causing that problem. Here's a quarter (flip)..... get yourself a real OS.

    6. Re:Finally by drinkypoo · · Score: 1

      Until you put a CD in the drive. Locks up multiprocessor machines fairly effectively until it works out what to do with it.

      yeah, what the hell is that all about? happens with linux too - especially when there are errors.

      windows NT finally (in windows 2000) figured out how to read a floppy without killing the whole fucking OS. and then we got USB and ATAPI floppies and the problem went away. but cdroms are already ATAPI (or SATA, or SCSI) and it seems like any OS still shits itself when it comes across a read error.

      Do I need to put another computer in my computer, connect it with gigE and do scsi-over-ethernet so that I can still do sector reads (for dvd ripping, naturally) but not have a bad CD kill my whole damned PC?

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    7. Re:Finally by Fulcrum+of+Evil · · Score: 1

      yeah, what the hell is that all about? happens with linux too - especially when there are errors.

      Craptastic interrupt handling. I recall the best part of OS2 was that you could format a floppy with zero system impact.

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

      Until you put a CD in the drive. Locks up multiprocessor machines fairly effectively until it works out what to do with it.

      yeah, what the hell is that all about? happens with linux too - especially when there are errors.

      Maybe I've got a very reliable collection of CDs or linux 2.6 handles it fine.
    9. Re:Finally by drinkypoo · · Score: 1

      I am currently using a system whose uname -a is "Linux sec2lpt7-linux 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux", and I still have the problem. It's Ubuntu Feisty, but frankly, I've found it to be a problem with all versions of linux -- and I have run all major and minor versions (if not tiny) in a timely fashion since 1.1[.47].

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  10. Close to press BS by Anonymous Coward · · Score: 0

    This is close to press BS as you have to put this into perspective.
    - Intel is the 800-pound gorilla, and AMD (compared to Intel) is just a mosquito.
    - Three years ago AMD use to have the best top-of-the-line processor for, and kept the performance crown for over a year, that did not changed the roles Intel and AMD have.
    - Getting an alternative to Intel is good thing per se, and the press should not push a development to crush and burn even before it is out to the market.

  11. Why worry? by ynososiduts · · Score: 1

    We have yet to really harness the power of two cores, so why all the fuss over four? How many multi-threaded programs are there anyway?

    --
    622677120
    1. Re:Why worry? by Nibbler999 · · Score: 3, Insightful

      It's not all about multi-threaded programs - being able to run multiple single threaded programs concurrently is also important.

    2. Re:Why worry? by Anonymous Coward · · Score: 0

      Think server

    3. Re:Why worry? by DeadChobi · · Score: 1

      Like clockwork, there's always someone that asks this question. Every CPU article, every time.

      --
      SRSLY.
    4. Re:Why worry? by smallfries · · Score: 1

      Multithreaded H.264

      Real-time encoding...

      --
      Slashdot: where don knuth is an idiot because he cant grasp the awesome power of php
    5. Re:Why worry? by melstav · · Score: 1

      How many multi-threaded programs are there anyway?


      A LOT.

      Most of them just aren't application that someone who only uses their computer to surf the web and play games would walk into Best Buy, Circuit City, or Wal-Mart to buy.

      Ray-tracers, webservers, database servers, and compute-farms are just a very small sampling of areas that will directly benefit from having four cores.
    6. Re:Why worry? by Anonymous Coward · · Score: 0

      "We have yet to really harness the power of two cores, so why all the fuss over four? How many multi-threaded programs are there anyway?" - by ynososiduts (1064782) on Sunday July 22, @04:59PM (#19948485)

      Well, ok, your results will vary from mine, but I can provide that data to you easily enough in Windows NT-based OS (since 2000 onwards) via taskmgr.exe, using its VIEW menu, SELECT COLUMNS submenu, & that's done once you are in its PROCESSES tab...

      E.G.-> Of 34 total processes I keep running here typically? 28 ARE MULTI-THREAD DESIGN (bearing 2-N threads & most are over 2 threads per program in that lot here)...

      You can check yours the same way I did... & they (generally) WILL benefit by the presence of additional CPU cores, as will single-threaded processes also (since the threads from other processes can be sent to the least saturated CPU cores present IF/WHEN needed, by the OS kernel component, known as the task scheduler).

      APK

      P.S.=> Today, AND FOR YEARS NOW, nearing a decade in fact? Many, if NOT MOST, programs today bear @ least 2 threads of execution (threads = the smallest atomic unit of execution in Windows NT-based OS' afaik - yes, there are "fibers", too)... apk

    7. Re:Why worry? by BlueParrot · · Score: 1

      It's so the gentoo users can run a computer game with their media player running in the background as they wait for the compilation to finish. ; )

    8. Re:Why worry? by Poromenos1 · · Score: 1

      Well, I don't know about that... I can't think of four programs that will use 100% of the cpu and need to run concurrently, all I can think of is movie encoding, and I won't be running four (or three) simultaneously...

      --
      Send email from the afterlife! Write your e-will at Dead Man's Switch.
    9. Re:Why worry? by pookemon · · Score: 1

      Presumably you are not a developer? Or if you are you haven't considered using something like VMWare (or even the Windows Mobile Emulator) for development/testing. Multiple cores make using these products soooo much nicer. You can have virtual servers and workstations running on a single machine. For implementation testing you can use "Snapshots" to revert back to a "clean" state (in a matter of minutes) so you can test your implementation over and over again.

      Having multiple cores makes your virtual machines run "100%" faster (Eg. You go from your emulator/VM and your development environment/debugger sharing a processor to them running on their own core). Quad core will mean that you can run a VM network at near to full speed.

      Once you've tried it, using a single core machine (even with that "HT" rubbish Intel pawned for so long) is painful.

      --
      dnuof eruc rof aixelsid
    10. Re:Why worry? by glitch23 · · Score: 0

      Even if individual applications do not take advantage of 4 cores your system as a whole will benefit due to your process scheduler scheduling threads across all 4 cores making your system more responsive.

      --
      this nation, under God, shall have a new birth of freedom. -- Lincoln, Gettysburg Address
    11. Re:Why worry? by Tenebrarum · · Score: 1

      That's what I thought when I bought the first Intel quad core.

      Alas, now I don't get much sleep at all.

      I don't know whether I should be happy or sad ...

    12. Re:Why worry? by Anonymous Coward · · Score: 0

      I can easily think of 4:

      1: DVD-Burning (Nero can fail burns if you don't give it enough CPU + Disk I/O)
      2: Recording TV (MPEG-2 or H.264 encoding, HDTV is even worse)
      3a: Filesharing (Most popular filesharing apps--Azureus, eMule, Limewire, Newsleecher--are CPU hogs)
      3b: Gaming + Teamspeak (easily 100% of one core)
      4: Browsing, reading PDFs, coding, typing, etc. (Both Fx and Adobe PDF can be hogs)

      I do all that on 2 cores now, but I need to be careful not to run all of it while burning DVDs. Gaming while burning DVDs is impossible. Gaming while recording TV is not ideal and has lag.

      (some of it requires multiple disks to handle concurrent disk I/O as well.)

    13. Re:Why worry? by WuphonsReach · · Score: 1

      Well, I don't know about that... I can't think of four programs that will use 100% of the cpu and need to run concurrently, all I can think of is movie encoding, and I won't be running four (or three) simultaneously...

      Moving encoding typically is multi-threaded, so it will use as many cores as it can lay hands on. So you'd only be encoding one movie at a time.

      For the rest of us, having 2 or 4 cores is more about being able to handle spikes in CPU usage without slowing down interactivity. With a single-core machine, when a process needs a lot of CPU time, I'm at the mercy of the (not so good) scheduler in Windows XP to keep the machine usable. On my 5 year old laptop, this often tests my patience as there are numerous tasks that spike the CPU and cause the screen to become unresponsive. Which means I have to interrupt my thought process while I wait on the machine to respond. Those spikes can last as little as 1 second, and still intrude upon my workflow. (Things like e-mail programs checking for e-mail in the background, etc.)

      One a dual-core machine, this happens a lot less often. CPU spikes are handled in the background on the other core while the first core keeps responding to my input. With a quad core system (especially if it's for the same price, roughly, as a dual-core), the operating system gains even more flexibility about scheduling tasks. Which should make the system even more responsive, even in cases where I have multiple tasks all clamoring for CPU attention.

      Now, it should be noted that I am very much a multi-tasker. I always have at least 6 applications open, with another 6 applets running in the system tray. I prefer to start up things like e-mail clients and web browsers and then minimize them to the background. Having 4 browser windows with 4-8 tabs in each window is not unusual. Along with 6-12 SSH sessions, a few documents, e-mails, and file folders open. My poor single-core laptop from 5 years ago regularly groans under the strain.

      --
      Wolde you bothe eate your cake, and have your cake?
  12. Re:Intel was never the choice for Quad Cores, sinc by ciroknight · · Score: 3, Insightful

    Guess what? The market doesn't give a shit, they just want multiples of 4 in one socket, period. Even AMD admits it was a mistake not to go MCM; Intel got the drop on them, and has deepened their lead quite substantially, leaving AMD sitting on their hands with no competitor for far, far too long (and their upcoming competition will quite frankly devastate them in the short run, however in the long run...).

    Intel had the option to rest on its laurels; they don't like to work any harder than necessary to remain on top, and the Core marchitecture gave them a huge.. well I'll say it.. "Leap Ahead" of the competition. Unfortunately, Intel's more of a bunny; hop a few times then get tired and sit around, whereas AMD is more of the turtle (slow to market, but rather constant). Well all know who wins the race.

    --
    "Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
  13. Re:Intel was never the choice for Quad Cores, sinc by qbwiz · · Score: 4, Insightful

    "True" QC, "fake" QC, what does it really matter? The only things that really matter in the end are performance and price (and possibly power dissipation). From the standpoint of a consumer, the internal technology has no importance at all.

    Now, if you said that "true" quad core was going to make the chips be twice as fast as Intel's, at half the price, then that would be interesting. Of course, you could say that the chips would twice as fast at half the price, and that would be just as interesting - the technology has nothing to do with it.

    --
    Ewige Blumenkraft.
  14. Doesn't matter by Sycraft-fu · · Score: 3, Insightful

    Geeks love to work themselves in to a lather over technical difference but to the end user, quad core is just 4 processors in a single socket, doesn't matter how it is delivered. Now if the Intel solutions performs poorly because of the 2x2 design then it could be a problem. However, thus far, it doesn't seem to. On the kind of apps that can use the power (like a 3D renderer for example) they just shine.

    In the end it doesn't matter how it is delivered, it matters who can deliver the good performance per $$$. Intel's quad core chips go a long way to doing that in the markets that can use them. The reason is it gets expensive to add physical processors to a board. A single socket board might be $100, but the same thing in a dual socket variety can be $400-600 and you don't even want to see the prices on quad sockets. Thus being able to drop 4 cores in to a standard desktop board, even if they aren't a monolithic 4 core package, is a good deal for many.

    Technical arguments and contrived benchmarks mean nothing. The only things that matters is how fast it runs the things you actually, really do, and how much it costs.

    1. Re:Doesn't matter by Brane2 · · Score: 1

      But on those "real life benchmarks" even old 4 socket Xeon would performe "just great" since there is minimal need for intercore communication with these tasks.

      They could be executed just as efficiently with multiple machines, connected through network.

      On any really intensive multicore problem existing Intel's dual-dual core solutions suck...

      Testing multicore solutions on optimized Photoshop tests, video encoding and raytracing is just like buying drag-racing truck for as daily commuting vehicle...

    2. Re:Doesn't matter by Sycraft-fu · · Score: 1

      Regardless of if you don't like them, they are in fact very real world and the kind of thing people want to do with quad cores. A network of computers is more expensive and uses more power. For that matter even if you are going for a network, better to pro in multi core processors, have each system do more. I'm not saying a real unified set of cores isn't better from a technical standpoint, I'm saying from a practical standpoint most people don't care, especially if you can deliver the "2x2" chips cheap and fast.

  15. Re:Intel was never the choice for Quad Cores, sinc by Joe+The+Dragon · · Score: 1

    If amd where to go MCM there better cpu to cpu and cpu to chip link the hypertransport bus will make things a lot better they the way intel does it.

  16. Re:Intel was never the choice for Quad Cores, sinc by Anonymous Coward · · Score: 0

    Never the choice?

    Intel has sold 1 million quad-cores (4 cores in a socket) already.
    AMD has sold approximately 0 quad-cores to date :)
    I guess nobody told those people that they should have waited...

  17. Re:Intel was never the choice for Quad Cores, sinc by suv4x4 · · Score: 1

    ... it NEVER MADE _true_ QC CPU...

    All existing Q6xx0 solutions are dual-dual core ie two dualcores sharing same FSB - and that is _NOT_ the same as true QC as Barcelona is claimed to be.

    That difference is enough to make Barcelona the main choice for many core servers even if it were made with old K8 and not the new K10 cores.

    Intel should have true QC chips in a year or so...


    You're very convinced the difference will be drastic, that's very funny thing to be when you never saw a single benchmark.

    According to Intel's engineers there's no identifiable bottleneckeck in a design that uses two 2-core dies on a single chip. And after all, if two dies was so terribly horrible, people would use multi-processor systems long before we saw multi-core systems.

    Intel is moving to single die 4-core processors, sure, but their technology, design and process is better in all other respects, which COULD easily be enough to leave AMD in the dust.

    People won't buy a 4-core processor to make an art statement, they'll get it to do work, so they can't care less if it's a "true" 4-core cpu or just.. well.. is a cpu that has 4-cores.

  18. Re:Intel was never the choice for Quad Cores, sinc by Brane2 · · Score: 1

    1. it all depends on task at hand. With tasks with intensive intercore communications true Barcelona could be say 10x faster than anything Q6xx0 on Intel's side even without superior core.

    2. If your general understanding of the problem is poor than any explanation that could be "interesting" to you is likely to be marketing bull**it, optimized for technical morons.

    You can't make universally valid "X-times faster/slower than" comparisons between these kind of machines.

    Results tend to be program-and-load specific...

  19. Re:Intel was never the choice for Quad Cores, sinc by Brane2 · · Score: 1

    Not true.

    If AMD wanted to, they could have hads Intel's style "quad core" long ago.

    Hell, even two "x2 4800" dies on one substrate, connected through HT link would be an equivalent, and they could do it in a few weeks even if they would decide to go for it _today_. There is not much to it.

    Opteron/AMD64 was _made_ so it could be connected it LEGO-like fashion...

  20. Re:Intel was never the choice for Quad Cores, sinc by Brane2 · · Score: 1

    I am very "convinced that performance difference will be drastic" since:

    1. This is mainly what currently holds Opterons over Xeons on servers, despite superior C2D core and heap of cache.

    2. I have exchanged dual Opteron boards for single socket DC 6000+.
    Despite HT link and dual RAM bank of existing Opterons being superior for most uses to Intel's shared FSB, there is tangible speedup just due to having really fast intercore communication path.

    3. AMD has onboard memory controller even now with K8 and K10 will bring further optimisations there.

    4. There are further optimisations for VT, which will bring ie. speeds of WinXP, running under VmWare on my Gentoo Linux (64 bit) much closer to native speeds...

    5 ...

  21. Re:Intel was never the choice for Quad Cores, sinc by Anonymous Coward · · Score: 0

    "According to Intel's engineers"

    Hahahahahah, please don't try to kill me, like you just did with your credibility.

  22. AMD: first to 8-core CPUs ? by this+great+guy · · Score: 1

    AMD have indicated they may do MCM in the future (Multi-Chip Module), like Intel. But since they are releasing a true quad-core CPU before Intel, it is going to give them an advantage: to make an 8-core CPU, they will just need 2 quad-core chips, whereas Intel will need 4 dual-core chips.

    I wonder how significant this technical advantage really is on various levels: performance, power consumption, reliability, yield, simpler to manufacture, cost, etc. Could this also mean AMD will be first to market with 8-core CPUs ?

  23. On AMD boards fully populate your CPU sockets by symbolset · · Score: 1

    Or you can't use all your memory sockets because the memory controller for half of them is in the second potentially non-extant CPU.

    Balancing the amount of memory on each side is a good idea too.

    --
    Help stamp out iliturcy.
  24. Neither one is a bad choice by symbolset · · Score: 1

    She's unlikely to tax either one.

    She'll need a lot of RAM for VMWare to work well. That will have a huge impact on your cost calculations. Use RAID for performance, she'll need that too.

    Processors are important but they're not the whole answer in the performance equation. At this time the bottlenecks tend to be more in the RAM and HD I/O.

    --
    Help stamp out iliturcy.
    1. Re:Neither one is a bad choice by nukem996 · · Score: 1

      Well the system will be used for many different things(from gaming to vmware to multi threaded programming things I want to try out) and we're hoping to future proof it so we won't feel the need to upgrade for awhile. The big thing concerning me is out the Intel Core 2 chips have so many bugs in them.

  25. Re:Benchmarks, Price, Release date-I SINCERELY DOU by Nom+du+Keyboard · · Score: 1
    My gf is going to school in late September and will need a new machine. Shes currently looking at the Intel Core 2 Quad since it just had a great price drop (its $300 at newegg) and may be doing some vmware stuff.

    I sincerely doubt that anyone still in school - any school - is going to overtax the current Core 2 Duo/AMD-64 X2 offerings available today. Short of running simulations of the Universe in real-time, or high resolution Maya renderings (remember when Photoshop was once the app that justified the most powerful machines, and AutoCad before that?) before class is over, that Quad Core is going to be performance, and wallet, overkill.

    She may want it. She may actually get it. But I truly doubt she really needs it. Feel free to point out what heavy duty computing she is getting into to justify this. And VMware isn't the answer. It actually runs quite well on current dual processor rigs with enough memory.

    --
    "It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
  26. Re:Intel was never the choice for Quad Cores, sinc by Brane2 · · Score: 1

    Actually, intel has sold 0.000 QUad cores (= 4 cores on a die in a single unit)...

    And if you count Q6xx0 as quad core system, then by that standard qualifies every dual socket dual core AMD system sold, since architecturally they are about equivalent, if not better ( 2x memory channels, HT links)...

  27. Re:Aburrídoooo. by Anonymous Coward · · Score: 0

    You have reason!.

    1. Windows x64 is useless. This OS runs slower in AMD64 or EM64T than Windows XP.
    2. Windows Vista is slower and buggy than Windows XP.
    3. AMD64 64-bit mode only is used to run OSes Linux, FreeBSD, NetBSD and OpenBSD.
    4. The 64-bit and 32-bit applications run faster in Linux or FreeBSD than in Windows XP.
    5. The Linux and FreeBSD community can develop applications for different targets of CPU.

    Dear President of AMD's CEO,

    Can you read my proposal?
    1. Today, is more important to follow the x86 compatibility of your AMD's CPU for the Linux/*BSD people?
    1.a) Why don't release a new CPU of 64-bit with less archaic instructions and more new 64-bit instructions of complex modes of addressability?
    1.b) Why don't use 8 KiB pages instead 4 KiB?
    1.c) Why don't remove x86 32-bit instructions? It eliminates ugly problems of 3264 bits system calls.
    1.d) Why don't double the pins to double bandwidth?
    1.e) Why don't double the number of DDR modules to 8 instead 4 to permit 8x1 GiB or 8x2 GiB?
    1.f) Why don't follow the K.I.S.S. principle to don't lose time making complex tasks!!!

    2. It's not important to improve the performance of the poor Instructions System Architecture (ISA) of AMD64. It's more important to release new ISA to improve gainly its performance maintaing the same principles of the previous design.

    3. You must to change the timelines. The time is precious in this hard race that Intel is winning.
      Change the plan in this time to don't lose the lost market and to re-born a new era of CPU 64-bit race.

  28. Re:Benchmarks, Price, Release date-I SINCERELY DOU by nukem996 · · Score: 1

    I'm currently doing research with MRI imaging on multi-core systems and she may be joining in. Plus we're Gentoo users ;)

  29. Re:Intel was never the choice for Quad Cores, sinc by Anonymous Coward · · Score: 0

    The reality of the market is that Intel killed the 4 socket market by making a 2-socket system behave like a cheap 4 socket system. This trend will continue.

    AMD lost the opportunity to grow the 4 socket market by failing to drop prices sufficiently. That is where their greatest advantage is (system architecture - HT, etc...).

    Now Barcelona is late and underperforming (2GHz at launch with scaling to 2.4 by Q1 2008)
    This is not enough to fight off Intel's 45nm offerings, especially the newer server platforms on deck such as caneland and tigerton.

    By the time AMD finally scales Barcelona to a respectable frequency, they will have to deal with Nehalem which IS a native quad core with on die memory controller and direct-connect links (CSI). Furthermore, Nehalem will have 8 cores AND SMT.

    The future is looking pretty grim for AMD in server-land.
    They do however appear to be making headway in the low-end of the laptop space which is a fast growing market. But...they need the high end to pay the bills. Gaining marketshare at the expense of profits is a recipe for disaster.

    AMD could get 99% marketshare if they priced all of their processors at $0 for example.

  30. Re:Intel was never the choice for Quad Cores, sinc by Wavicle · · Score: 3, Insightful

    If AMD wanted to, they could have hads Intel's style "quad core" long ago.

    And yet they don't, and they just posted a $600 MILLION loss in one quarter. The difference between what AMD lost and Intel made last quarter is almost 2 billion dollars. Maybe you should take your market genius over there and help them turn it around.

    --
    Education is a better safeguard of liberty than a standing army.
    Edward Everett (1794 - 1865)
  31. Re:Intel was never the choice for Quad Cores, sinc by Anonymous Coward · · Score: 0

    Umm...a 2 socket Q6xx0 system is 8 cores.
    A 2 socket AMD Opteron system is 4 cores.

    Intel killed the 4 socket market for AMD. This used to be a huge cash cow.

    Why would you pay for 4 sockets and get 8 cores, when you can get a MUCH cheaper 2 socket systems.
    The 2 socket (8 core total) systems are more dense and give you greater throughput per dollar - even with an FSB - thank Intel for their gigantic caches which help to reduce FSB traffic more than an opeteron might.

  32. There is no "real 4 core" performance leap. by guidryp · · Score: 1

    "Barcelona could be say 10x faster than anything Q6xx0 on Intel's"

    BS: At what tasks?

    Because Intel has already demonstrated near 4x performance with it's "untrue" quad core. You are not going to get more than 4x single core performance. There is only a tiny margin of efficiency of multi-cores that AMD could improve upon.

    AMDs only real Barcelona hope is if it increases basic core performance significantly, there is no magical "real 4 core" performance leap to be had certainly not a 10X performance increases. That is impossible.

  33. No major loss by Anonymous Coward · · Score: 0

    It used to be that ATI had better hardware, and Nvidia had better backroom deals.

    Things have changed. The only thing ATI/AMD offers open source is the middle finger. AMD/ATI has done virtually nothing except add user-hostile features and low-level DRM on the framebuffer level.

    I won't be buying from them anytime soon. They need to get on the ball and lead, not just throw slipshod proeducts out just to try to keep up. AMD needs to take a charge off the quarterly earnings, and do some R&D in order to survive.

    IMHO, even VIA is starting to outshine AMD/ATI.

  34. Re:Aburrídoooo. by Anonymous Coward · · Score: 1, Interesting

    1) What Linux/BSD people need is irrelevant, the market share is too low. (I run WinXP, Debian and FreeBSD, for the record)
    1.a) Complex addressing modes are only good for people writing software in assembler - few are needed by C-compilers, and those are provided already anyways. They're also more silicon space that could be better used for wider ALUs/FPUs or more cache.
    1.b) 4kB/4MB pages are already available. 8kB, while marginally nice, isn't really necessary.
    1.c) 32-bit instructions are just being translated to micro-ops, just like 64-bit instructions during instruction fetch, the benefit would be marginal, while losing 32-bit compatibility.
    1.d) Doubling pins means more layers in motherboards, skyrocketing the manufacturing costs. It's possible if you're ready to pay 300-500$ per motherboard, to produce those 10 layer monsters. It would also mean another new socket type.
    1.e) Because the memory controller is on the CPU (on the die), this would also mean more traces on the PCB -> radically higher costs.
    1.f) AMD-64 keeps things simple, at least compared to some unnamed competitor. *cough* Itanic *cough*.
    2. New ISA is often a suicide. Ever heard about Itanium?
    3. Biggest blunder AMD has done recently is dropping Socket-939 prematurely.

  35. What EPIC technology about? by Anonymous Coward · · Score: 0

    What know you about the EPIC technology after the unsucessful VLIW and sucessful multi-core speculative-superscalar?

    * The problems of VLIW were the excesive NOPs and its stalls. So, the VLIW technology is not the solution of today.
    * We're 7 years later of the start of 3rd Millenium, it's a poor race of an American. Because of the stupidity of mea culpa.

    Perdón por mis pecados, tenía que haberle dicho a AMD que tendría que haber hecho una nueva CPU de 64 bit diferente claro que puede reinventarla! de tal forma que puede llevar 8 IPs (Instruction Pointers) integrados en el scheduler x N cores para multithreading and/or multiprocessing en vez de complicados y lentos 8xN cores x1 IP para multiprocessing.

    Las ventajas son el permitir la ejecución paralela del mayor número de unidades enteras y de coma flotante aprovechables por cualesquiera de las IPs que necesiten. Y además permitir la cooperación de información entre los registros de las IPs integrada en el complejo scheduler.

    Los sistemas multicores tienen el problema de la consistencia de memoria y coherencia de las caches. MOESI? Dragon?
    Pero también tienen otro problema, no están aptos para sistemas multithreading porque sus IPs no están en la misma caché sino en diferentes cachés, y las hebras comparten el mismo espacio de memoria y por lo tanto de la caché.

  36. Race? by AnimeDTA · · Score: 1

    Current Opteron users can also upgrade to eight-cores just by replacing their current dual-core Opterons with two quad-core Opterons.

    Of course, Intel is also rushing out a similar solution, in the form of their V8 programme. So, it is a race to see which company will be the first to release an 8-core platform. They talk of putting two quad cores on existing dual core systems to get 8 core platform. This was done over a year ago on Intel quad cpus. That race was over long before the article.
  37. Re:Benchmarks, Price, Release date-I SINCERELY DOU by Joe+The+Dragon · · Score: 0, Flamebait

    running VISTA + anti virus + background apps with rendering / cad or video work can tax a system even more so with some of carp that some schools make you run on your system can tax it.

    Games are a other thing that can push systems also it not just the cpu that gets taxed in is also the ram, IO , hard disks , network, video and so on.

  38. All chips have bugs by symbolset · · Score: 1

    They're called errata. The most recent bunch are more plentiful than usual but it's not unheard of. Get your microcode updates, whichever vendor you get your chip from. AMD calls them BIOS updates which partly makes sense since you usually patch the BIOS at the same time. You get them from the OEM of your motherboard or system usually but as you see from those links operating system vendors can put them out too. The errata that have been in the press lately are unlikely to affect chips you buy right now because new chips and systems will almost certainly have their BIOS and microcode updated from those issues before they ship.

    No computer is future proof. You can get some extra months on one by buying above average, but the best desktop you can get today will still look sad in three years. Pay extra for bleeding edge if you want to but the best value is middle of the road and frequent upgrades.

    --
    Help stamp out iliturcy.
    1. Re:All chips have bugs by nukem996 · · Score: 1

      I know no system is future proof but if you buy right a system can last you years. I still use my IBM Thinkpad T40(1.5ghz pentium-m) as my laptop because it works so well for what I need. My currently desktop is an AMD X2 4400+ and I am very happy with it and usually don't use 100% CPU. Since we can wait till late September to get the system I'd rather be 100% sure on what we want then to buy now and wish we went with something else.

    2. Re:All chips have bugs by WuphonsReach · · Score: 2, Interesting

      No computer is future proof. You can get some extra months on one by buying above average, but the best desktop you can get today will still look sad in three years. Pay extra for bleeding edge if you want to but the best value is middle of the road and frequent upgrades.

      If you had written that statement in the late 90s or even as late as 2002, I'd agree with you. But system performance stopped doubling every 18-24 months a long time ago. Now it's closer to 36-60 months (although dual-core and quad-core upsets the calculation) before performance doubles.

      What I've seen over the past decade is that responsiveness determines how sad a system looks and feels. A single-core/single-CPU system can easily be bottlenecked by a runaway process or by an operating system that gives too much time to a greedy process and not enough to being responsive to the user. But once you start adding CPUs or cores, apparent responsiveness goes up quite a bit.

      I have good reason to believe (I've used multi-CPU systems for 3+ years now) that the lifespan of a multi-core or multi-CPU machine is going to be quite a bit higher then you give it credit for. My 3-year old box still feels pretty quick because the interface (except where Windows is poorly designed) rarely blocks input. The new dual-core machines that I'm building today will probably remain useful for 8+ years because of having multiple cores.

      And as always, having enough RAM is essential (2GB for a dual-core box is a useful mininum).

      --
      Wolde you bothe eate your cake, and have your cake?
  39. Ahh more FUD by Sycraft-fu · · Score: 3, Insightful

    Vista 64-bit and Xp 64-bit work just fine, thanks. I'm running Vista-64 right now. We make a fair bit of use of both at work, for precisely the reason that we have apps that run out of 4GB of RAM.

    As for your drivers comment, well let's see here: Intel has 64-bit XP and Vista drivers for their motherboards (and by extension graphics) and NICs as far back as their 865 series (anything older doesn't support 64-bit CPUs). Vista-64 has native support for older nVidia chips (GeForce 2 is the oldest I've tried) and nVidia provides downloadable drivers for their 5 (FX) series and newer. ATi likewise has support in the OS for some older chips, and downloadable drivers for the 9500 and newer for XP-64 and Vista-64. Broadcom has XP-64/Vista-64 drivers out for all their NICs (both 44XX and 57XX series). LSI has 64-bit drivers for, well, all their products that I can see for XP and Vista (and Linux and Solaris). Colorvision has 64-bit drivers and is Vista compatible. Logitech, Microsoft, and Saitek all have 64-bit drivers and support apps out for their input devices.

    I could go on but basically any modern hardware seems to have no problems at all with 64-bit drivers. In fact, on all the 64-bit Windows systems I've set up, I've never encountered a component we didn't have a driver for. I'm not saying there aren't some oddballs out there, I'm saying that the vast majority of stuff DOES have a driver and thus it is a non-issue.

    When you are countering some FUD, please don't spread your own. You may to like MS OSes, that's fine, but it is a lie to say that finding drivers for 64-bit Windows systems is hard. The vast majority of devices, including specialty devices (I've got 64-bit Vista drivers for my colorimeter and StudioCanvas for example) have 64-bit drivers. It is just a non-issue. Far more rare is 64-bit software, but thankfully 32-bit software runs without problems on the 64-bit OS.

    1. Re:Ahh more FUD by fm6 · · Score: 1

      Your post exemplifies why I hate the term "FUD". People tend to use it with little or no evidence. In this case, you're full of shit. My comments on XP 64 were based on personal experience. As for Vista 64 working "just fine", I can only ask: Dude, what planet do you live on?

    2. Re:Ahh more FUD by Sycraft-fu · · Score: 1
      Well your personal experience isn't valid. The main reason is simply that personal experience doesnt make empirical evidence. A person's experience can deviate quite far from the norm. Also in your case it seems particularly likely since you seem quite hostile towards Windows, and thus are not likely to think clearly and use proper problem solving, and more likely to write it off as "just crap" or whatever.

      I presented you with valid evidence to the contrary. I showed wide availability of drivers from manufacturers that account for a large part of the market, in all different kinds of devices. That is proof right there that the statement that there aren't many drivers for 64-bit is false. I'm sure you can find devices that don't have drivers, but that is always the case. However if the vast majority of devices do (and it is easy to demonstrate that fact) then the statement is false.

      As for Vista-64, I live on planet Earth, specifically I live in a part where we try not to get all zealous and hateful, and actually evaluate new products. I do not have any empirical studies on Vista 64, however in the cases that I have installed it, which are several, it does its job without problem. One is my desktop at home. It has been running 64-bit Vista for a couple months now. If it isn't working "just fine", then I guess I misunderstand the definition of that phrase. It runs all my apps and games, it doesn't crash, it seems to do its job well. What precisely is it failing to do? Same with the installations at work. They work on the hardware on which they are installed and run the apps they are asked to run. That seems to me what they ought to do.

      So yes, what you are doing is attempting to spread FUD: Fear, uncertainty and doubt. You are attempting to put out misinformation about something as such to make it look bad and make people not want to try it. That's FUD. Saying "In my experience I've not been able to get 64-bit XP working," is one thing, saying "MS's 64-bit offerings suck and don't work," is FUD because the facts don't back that up.

      If you have problems, perhaps you should ask why that is the case, rather than just blaming MS for sucking. Just because you can't make something work doesn't mean it is broken, it might just mean you didn't read the directions.

    3. Re:Ahh more FUD by Allador · · Score: 1

      He's really not full of shit.

      Go into any engineering shops, and unless they're poorly organized, they've been using x64 windows xp for years for their design & engineering work. It works just fine.

      And wrt Vista-64, I think you'll find that in a competent IT shop, you will have no problems with vista once you get past the learning phase, and know what you're dealing with. Then its all pretty straightforward.

      The only problem you're going to have with either XP or Vista-64 is drivers. So just buy your equipment from manufacturers who certify their equipment on x64 windows. Consider Dell, HP, and IBM all do this, you shouldnt have a problem finding equipment that works.

    4. Re:Ahh more FUD by fm6 · · Score: 1

      You would be making sense if people always bought all their hardware from the same manufacturer. Remember, drivers aren't just for internal stuff. If I were to move to XP 64, I'd have to discard my scanner, my printer, my PDA... OK, no biggie, I was tired of them anyway. But now I can only buy gadgets that have XP64 drivers. Which drastically limits my choices.

    5. Re:Ahh more FUD by fm6 · · Score: 1

      So your postivie experience is proof that everything's hunky-dory, but my negative experience is just anecdotal? You're really good at cherry-picking your evidence. Have you thought of going to work for the White House?

    6. Re:Ahh more FUD by Sycraft-fu · · Score: 1

      Now you are flying off with straw man and ad-hominem attacks and simply talking nonsense. My personal experience is NOT proof that it does work in all cases, I noted that. However it does counter what you claim. You said "try to run Vista-64 at all!", implying it was a nearly impossible task. Well the fact that I am doing so, right now, does disprove that. Doesn't mean it'll work in all cases, but it does mean it isn't this impossible task you pretend. In fact in my case it was extremely easy. Install OS, install some drivers, install apps (thus far all have worked), done.

      Also this still doesn't address the real proof of widespread driver support for 64-bit MS OSes, which you claimed there was not. That is clear and evident bullshit. When the major chipset, NIC, graphics, sound, input, and storage companies all have 64-bit drivers, it is real hard to claim they are scarce. From this I can only conclude that:

      1) You have an oddball device you couldn't find drivers for, and thus have come to the conclusion that almost nothing has drivers, with no further evidence. Or...

      2) The drivers weren't on the CD and you didn't know or care to go to the manufacturer's page to get them. Or...

      3) You are basing this on very old information (big surprise: there aren't many drivers when an OS comes out, but they just keep coming). Or...

      4) You know this to be false are are simply lying to further an agenda.

    7. Re:Ahh more FUD by fm6 · · Score: 1

      My personal experience is NOT proof that it does work in all cases, I noted that.
      You also noted it as evidence that I was FUDing.

      You're good at throwing out nasty words like "FUD" and "straw man" and "ad hominem". Next time such a word occurs to you, try looking in a mirror.
    8. Re:Ahh more FUD by Sycraft-fu · · Score: 1

      No I know pretty well what I'm talking about. A straw man is an argument constructed and attacked rather than attacking the real argument. In your case the straw man was claiming that I'd said my experience was proof that everything was hunky dory. I never made such a claim and thus you are attacking a straw man argument. An ad hominem attack is one directed at the person, rather than the argument. In your case it was the "Have you thought of going to work for the White House?" You couldn't formulate a response to what I said, and so instead decided to imply that my opinions are worthless/contradictory/etc.

      The one who should be doing some self reflection, or looking in a mirror if you prefer, is you. When you start coming back with nothing but one line attacks and ignoring everything, it clearly means that you've got no response but simply aren't willing to back down. If you dislike the terms I've used, then stop doing them.

  40. Re:Intel was never the choice for Quad Cores, sinc by AbRASiON · · Score: 1

    Oh god these AMD guys just won't drop this.

    WE KNOW ALREADY. the intel quad core still performs very well in benchmarks - faster than the dual core in multi-threaded apps, one can only conclude it damn well works.

    As for AMD's 'true quad' performing better, no one knows for sure, there's no real benchmarks yet at this point.
    AMD could release it and say 'wow, our system is 25% faster than the Q6600" and intel could say 'err so what' and release the Q6600 clocked 25% faster because there's so much damn headroom on their chips at the moment.

    I'm a fanboy of neither company but right now AMD fanboys claiming "K10 will rule all!" and "Barcelona 'rapes'!' etc are totally foolish, NO ONE KNOWS YET.

    Finally there's the efficiency of each core itself.
    Look at the Intel C2D @ 2ghz vs the X2 3800+ at 2ghz - both dual core but one of them is substantially faster than the other - efficiency on each cpu will make a difference.

  41. Engaging x86-64 long mode from XP-32? by Thorrablot · · Score: 1

    A couple clarifications: I was referring to the DOS extender technology, and the x86-64 article does indeed refer to it being "possible" to enter x86-64 "long mode" using such a technique.

    Is anyone actually doing this for a non-turnkey application?

    --
    Any sufficiently advanced technology is indistinguishable from a rigged demo. -- James Klass
  42. I'm upgrading next month and I'd love to buy AMD.. by funkdancer · · Score: 1

    ... but alas it's the Q6600 for me as a) Intel just drop kicked its price, and 2) AMD are still nowhere near releasing quad cores for the consumer market. "Later this year" just doesn't cut it, so here's yet another person switching from AMD (Newcastle 3200) in their desktop to Intel. :P

    --
    ISO certified == THX certified
  43. Barcelona by infonography · · Score: 1

    The Doctor: Rose Tyler, I was gonna take you to so many places. Barcelona. Not the city Barcelona, the planet Barcelona. You'll love it, fantastic place, they've got dogs with no noses!
    [laughs]
    The Doctor: Imagine how many times a day you end up telling that joke, and it's still funny!

    Well, that aside but because it had to be done. But to business. I remember when 64bit cpus came out Sun and a few others had them (12 years ago) the programming took forever to catch up. They are still selling 32bit processors as new. I think I will leave that hanging in the air.

    --
    Sorry about the writing. Robot fingers, you know? Cliff Steele in DOOM PATROL #23
  44. Re:Intel was never the choice for Quad Cores, sinc by woosoki · · Score: 1

    A fable is only a fable, and what's worse, this race is supposed to run forever. Surely AMD can show their persistence and diligence despite their past ill judgments and mistakes, Intel for now has the upper edge.

    --

    Slashdot me with L$s!

  45. I game on Windows XP x64 and Ubuntu x86-64 by TheThiefMaster · · Score: 1

    I have an AMD X2 3800+ (s939), 2GB of ram and an nVidia GeForce 8800GTS all in an nForce 4 motherboard, and drivers for all of it are available for both Windows XP x64 and Ubuntu x86-64.

    My 250GB Windows disk is overflowing with major games, and all run wonderfully. Except for the occasional one I have to crack, either because it's too old and tries to load a 32-bit driver (understandable) or the company went for a shit copy-protection system that tries to load a 32-bit driver (eg Overlord). That's not such a big problem as I crack most games anyway.

    My Linux install is reasonably new (Ubuntu 7), and already has launchers for 8 commercial games on the desktop. Admittedly a couple are running in Wine, but they still run well. Neverwinter Nights and UT2004 are examples of native linux games, EVE online and steam are running in Wine.

    So far I haven't found anything that doesn't work well on a 64-bit OS. Well, except copy-protection.

  46. I see the Intel fanboys have shit on your post by Anonymous Coward · · Score: 0

    Go here:

    http://www.fftw.org/

    Download and compile it (and get your free compiler here, because Sun Studio 12 is 5% or more faster than GCC even on Linux...). Do so on both AMD and Intel chips.

    Now, benchmark both architectures.

    FWIW, my 2.4GHz Opteron runs FFTW about 30 to 40% faster than my 3.2GHz Xeons. Even when the Opteron is running the 32-bit binaries compiled for the Xeon.

    PS - when you compile FFTW, make damn sure you disable ALL inlining...

  47. Re:Intel was never the choice for Quad Cores, sinc by evilviper · · Score: 1

    Unfortunately, Intel's more of a bunny; hop a few times then get tired and sit around, whereas AMD is more of the turtle (slow to market, but rather constant). Well all know who wins the race.

    I think it's important to remember that Intel inadvertently delivered the high-end server market into AMD's lap.

    Intel had done so much heavy marketing, pushing claims that the Itanium was going to blow away all the proprietary CPU architectures, that damn near EVERYONE EOL'd their Unix servers... Alpha, MIPS, PA-RISC, etc., etc. Intel and Itanium made them announce the end was coming, and then when Itanium turned out to be the biggest flop in history, companies around the world had nowhere to go, but perhaps POWER and SPARC.

    Then, into this vacuum, appeared AMD's x86-64, which had great performance, and everything needed for the high-end server market. AMD ate everyone's lunch (and got a bit more comfortable than they should have).

    And also interestingly... You can't run your old proprietary Unix OS on AMD64 hardware, so what do you do? You switch to Linux. So it got a boost out of Intel's stupid marketing blunder as well.

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  48. I sort of agree with you... by symbolset · · Score: 1

    but think your information is a little dated. For many years what I said was true. Then for about 18 months it wasn't. I believe the race is back on now.

    Today's quad core, vm supporting 64bit machine will be quite useful in 8+ years, especially if you get the ULV processor. But compared to what's on the shelves at WalMart on that day it will still look dated.

    What I wonder is what sort of hideous application would require the type of computing horsepower that should be available 8 years hence. By then what's that process supposed to be? 21nm? 24? I trust the rocket scientists at the chip companies will continue to come up with technology to astound us.

    --
    Help stamp out iliturcy.
    1. Re:I sort of agree with you... by WuphonsReach · · Score: 1

      I still doubt that we're going to see single-core performance increases like we did in the mid/late-90s. Current CPU cores, even with the smaller processes, seem to be limited in how much they can ramp up.

      While I'm a fan of multi-core (dual-core is a minimum recommendation from me for the past year, ever since the Athlon64 X2s broke the $150 barrier), I do question the idea of more then around 4-8 cores on a consumer / light-business desktop. For the power users, yeah, they'll be building systems with 4 CPUs each with 8-16 cores. But I suspect it will be massive overkill (and too expensive) for others. Now, if the CPU makers manage to fit 16 cores into a single CPU and price it under $150...

      I've been poking around with an old PowerMac G4 from 1999 this past week. It's a 450Mhz, single-CPU unit. But with enough RAM (I put in 1280MB), it's surprising how snappy OS X 10.4 is on it. Definitely quick enough for all but CPU-heavy tasks. If it was one of the dual-CPU systems, it would definitely still be usable as the primary machine for a light office user. As is, it's fast enough to drive a 1680x1050 screen, play a DVD, and browse the web.

      --
      Wolde you bothe eate your cake, and have your cake?
    2. Re:I sort of agree with you... by symbolset · · Score: 1

      I agree. Where we are right now is that the pace of improvement will not stop even though the baseline product is far more capable than 90% of the people need. I don't expect this to change any time soon. The person who can make efficient use of a top of the line pc will only become more rare.

      The baseline will continue to improve at remarkable rates as each innovation on the bleeding edge drives prior art downmarket.

      Peripherals are a different story. I expect more innovation in human-machine interface than we've seen thus far.

      --
      Help stamp out iliturcy.
  49. Re:Benchmarks, Price, Release date-I SINCERELY DOU by WuphonsReach · · Score: 1

    $300 is not an unreasonable amount for someone to spend on the CPU in a system that they think will need horsepower. It's when you go beyond the $250-$320 price range that prices escalate rapidly compared to the performance increase. I would dissuade most users from spending $600 on a CPU, but wouldn't be as negative towards someone in the $250-$300 range.

    Of course, for the budget users, I'd be pointing them at the lowest cost dual-core CPU. Or possibly a few steps up from the bottom. There are some pretty decent dual-core CPUs in the $100-$120 range.

    --
    Wolde you bothe eate your cake, and have your cake?
  50. Re:Intel was never the choice for Quad Cores, sinc by ErikZ · · Score: 1

    I've always been a fan of AMD, but I agree with your point.

    It doesn't matter if it's two dual cores in one package. It doesn't matter if it's 4 single cores with a highly trained monkey dividing up the instructions between the cores. It's the end results that matter.

    However, right now you can't get the 300$ quad core from Newegg, it's sold out. You *can* get a 61$ dual core from AMD though. And unless you require a lot of processing power, it's more than enough for most people. Especially college students on a budget.

    I'd go as far to say that if you're on a budget, it's a no-brainer. Even if you could use the processing power the Quad core chip brings you, a 239$ difference is huge.

    --
    Democrats or Republicans. They are both taking us to the same place and they are not afraid of us anymore.
  51. True Quad-core ppft. Intel is going true 9 core by BlackSnake112 · · Score: 1

    Intel will make a 9 core chip. 8 cores for the OS to use and the last one for the memory controller.

    **Intel if your reading this, and do this I want a percentage.
    **** laugh, it makes you feel better

  52. 8 core platforms? by Gr8Apes · · Score: 1

    AMD has had an 8-core platform since the 8x Opterons came out. They had a 16-core platform with the introduction of dual core CPUs a couple of years ago, and they'll have a 32-core system when Barcelona comes out.

    But why not say Intel was "first"? They were the first in the x86 space to slap 4 cores into a single socket package. Let's wait and see how AMD's solution actually performs when it comes out. Either way, it's going to be interesting and prices should drop, so we should all like both Intel and AMD for their continuing competition.

    I still think AMD has the better server side solution by far, but for the consumer side Intel is the better bang for the buck since C2D came out.

    --
    The cesspool just got a check and balance.
  53. Ripping out some decode stages would help... by Anonymous Coward · · Score: 0
    Most of the x86 instruction decoding cost is in the design effort required to support it. Which is not a performance hit per se. It would be if you assumed equal implementation effort, but that's not the reality of the marketplace.

    The big x86 problems are:

    • Inadequate register set. Mostly addressed by AMD. This has required more L1 cache ports and fancier stack hardware, but okay, not too big a performance penalty.
    • Complex instruction decoding. This is the biggie that I could see a redesigned instruction set solving. You could rip a couple of pipeline stages out of the front end, which would reduce branch misprediction penalties and improve cold-cache performance.
    It's the decoding latency that I see as the major remaining x86 liability. The entire P4 trace cache mess was a (failed) attempt to reduce the branch misprediction penalty, but it sucked as soon as you escaped the L1 cache.

    It's probably not worth it, but even without major VLIW rearchitecting, there are ways to improve on the x86.

    1. Re:Ripping out some decode stages would help... by Chris+Burke · · Score: 1

      You're right, in that it's the decode latency that is the big x86 penalty. It ends up not being that much, like I said, a percent or two on average.

      The P4 trace cache was actually a quite successful way to reduce the decode latency and decouple decode from the critical path. The reason it didn't really help branch mispredict latency is because getting rid of 3-4 cycles isn't that big a deal when there's at least 15 more cycles after that. :P

      --

      The enemies of Democracy are
  54. Horsefeathers! by Anonymous Coward · · Score: 0

    Linux's 64-bit support isn't up to much either.
    Linux's 64-bit support is just peachy. All the drivers work, and 32-bit apps work fine, too. I'm even being brave and running a mostly 64-bit userland, but that's optional.

    What sort of problems are you encountering? I'm not having any.

  55. Enabling 64-bit from XP-32? (was Re:...) by Thorrablot · · Score: 1

    Only a fraction of the 64-bit capable desktops and workstations are running 64-bit applications. What's more, there are very few mainstream 64-bit applications out there, despite the fact that for gaming, audio processing, image processing/photoshop apps, and video there would still be performance advantages (memory bandwidth and operation throughput), even if you don't yet have > 4GB of RAM.

    It's not really compelling - plus or minus a few percent. And you need to test two binaries which is expensive. So unless you're absolutely forced to use more than 4GB per process, I think people won't bother.

    Looks pretty compelling from here! Take a look at the 32-bit vs. 64-bit benchmarks shown here for instance! If I was a game developer, I'd gladly take 40FPS over 30FPS if it only meant a recompile targeting a 64-bit platform! You only need to test two binaries if you also choose to support 32-bit as well - a suitably advanced app/game could just make a 64-bit capable AMD/Intel chip a prerequisite these days (DOOM required a 386 or better during a similiar 16/32-bit transition period)

    "Sherman set the wayback machine to the early 90's, and the great 16-32 bit transition" You might recollect the introduction of the mighty 386 processor, extended memory modes, the Win32s API, but probably most importantly, killer apps like DOOM loading up their own 32-bit memory managers to sidestep the OS, which really wasn't ready to provide good 32-bit native support. Apps that did this completely took over the system, putting the host OS in stasis until the app was exited.

    Sounds much like the same situation - the majority of users are running an OS that can't tap the full potential their CPU has to offer. So - why aren't we seeing similar application tricks, like those that enabled 32-bit protected mode now? The proposition of writing an application which would sidestep Windows XP 32-bit and set up a mini 64-bit host environment (not really a full OS) is not that radically different, right?


    If you really want 64 bit, I don't see why you can't use Windows x64. Sure you'll need to be careful that you have hardware which has x64 drivers, but that's life.

    *I* can (and regularly use XP-64, W2K3 64-bit, and even Vista 64-bit these days) - but if I'm writing a high-end app/game for a reasonably wide audience, you have to realize there's a lot of Windows XP 32-bit boxes out there running on CPUs capable of running in 64-bit "long" mode. It would be mighty sweet to tap into that power for high-end gaming, audio/video processing/transcoding, ray-tracing, etc.

    32 bit Windows already has PAE which is the moral equivalent of a Dos extender. I think Outlook and MS SQL server can use it. So there isn't really a hole for a 64 bit Windows extender.

    PAE only gives you access to more memory, it doesn't enable the CPU 64-bit processing, so it's not interesting to me. What's more - programming to these "bank switching" style memory extensions really is quite cumbersome.

    I've often wondered what would happen if you could make bootable games - e.g. Linux+ATI and NVidia drivers+a game binary on a LiveCD. But to make it work you'd need to be able to offer much better graphics performance than regular Windows, just like Doom's extended Dos had better performance than regular Dos.

    And given the amount of effort NVidia and ATI spend on Linux drivers compared to Windows ones, I'm not sure that's the case. DirectX is thinner layer over the driver than OpenGL too.

    Yes - using a stripped down Unix core could achieve the same goal, I suppose. Again the DOS4GW dos extender did some mojo regarding drivers such that it leveraged the existing 16-bit DOS drivers for a number of s

    --
    Any sufficiently advanced technology is indistinguishable from a rigged demo. -- James Klass
    1. Re:Enabling 64-bit from XP-32? (was Re:...) by Thorrablot · · Score: 1

      Obsession being the mother of invention, I did some further digging, and discovered the comp.arch folks were discussing this two years ago. From what I've gleaned from a few postings and white papers, and thinking about how WOW64 works, this really seems like it ought to be possible - the fact that it isn't here already must mean the effort is extremely high (unlike 16->32, it appears MS didn't give any "extender hooks" to make this easy to do.)

      --
      Any sufficiently advanced technology is indistinguishable from a rigged demo. -- James Klass
    2. Re:Enabling 64-bit from XP-32? (was Re:...) by Hal_Porter · · Score: 1

      Looks pretty compelling from here! Take a look at the 32-bit vs. 64-bit benchmarks shown here for instance! If I was a game developer, I'd gladly take 40FPS over 30FPS if it only meant a recompile targeting a 64-bit platform!

      That's nowhere near representative

      E.g.

      http://forums.nvidia.com/index.php?showtopic=29278 &mode=threaded
      I get unstable results in Vista x64 the range from as low as 4800 to as high as 5200, this is a massive instability when you consider that ins Vista x32 I get 5270 +/- 20 and on XP (both x86 and x64) I get 5300 +/- 15. If anyone would like the compare URLs I can post them, just ask

      x64 seems to have a graphics driver issue.

      or

      http://news.softpedia.com/news/Windows-versus-Wind ows-or-32-bit-versus-64bit-1349.shtml

      x64 and x32 perform identically. This is what I'd expect actually.

      You only need to test two binaries if you also choose to support 32-bit as well - a suitably advanced app/game could just make a 64-bit capable AMD/Intel chip a prerequisite these days (DOOM required a 386 or better during a similiar 16/32-bit transition period)

      Yeah but back then every gamer had a 386. Now everyone has an x64 compatible CPU but most of them are running 32 bit Windows.

      PAE only gives you access to more memory, it doesn't enable the CPU 64-bit processing

      x64 gives more registers, and you can use things like CMOV since you know all x64 CPUs support them.

      Having more registers won't help that much I suspect - most games are limited by GPU or memory subsystem performance, not by CPU registers.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;