Intel Begins Shipping 64-bit Prescotts 411
Rucas writes "With a minimum of fanfare, Intel has begun shipping a version of the Pentium 4 with 64-bit instruction set extensions. The news came to light not via an Intel press release, but rather through the spec sheet for a new server from IBM. In the midst of the new IBM eServer xSeries servers based on the recently released 64-bit Xeon is a blade server powered by the 64-bit Prescott. This marks the first product appearance of the new CPU."
And tought that before was the oposite (Score:4, Insightful)
Figures (Score:5, Insightful)
Bang for the buck means AMD wins hands down.
Re:Figures (Score:2, Interesting)
Wintel (Score:3, Interesting)
Intel have already lost out on providing XBox2 with a CPU.
Re:Figures (Score:5, Insightful)
Re:Figures (Score:5, Insightful)
However, the central insight is exactly correct; overcoming the brand takes much more time than overcoming the product.
Re:Figures (Score:3, Insightful)
OTOH, that inertia bites both ways. Once the brand has been overcome, it's a bitch to get past the "has-been" reputation.
Witness the progression from "you can never going wrong buying IBM", to quite a few years of criticising IBM engineering/marketing decisions (Big Iron! MCA bus!), and now they're slowly creeping back as purveyors of open standard equipment.
Re:Figures (Score:5, Insightful)
As with microsoft, a lot of it has to do with politics, arm-twisting and inertia.
Also, people like to pay more to get the same (or inferior) thing because, of course, in the corporate mind paying more = better product.
Re:Figures (Score:4, Insightful)
Re:Figures (Score:3, Insightful)
I was reading in No Logo (Naomi Klein) that a lot of products that have a consumer and corporate version are basically the same thing but the latter has a higher price-tag just so the corporate world doesn't think it's buying cheap consumer grade stuff. Hell, I even think slashdot had a story about that not so long ago.
Uh... CEO Reality check... (Score:5, Interesting)
Then I started noticing that EVERYTHING was IBM. The servers, the workstations, even the CABLING. I saw this at every bank we did work for (at least 8 different organizations).
So if it wasn't for the quality, expense, and/or speed, what was it? I later learned that this was a common theme in many larger organizations and it had a lot to do with how much IT stock was owned by the execs.
A friend of mine - a CIO - relayed to me that when a large organization buys a ton of equipment from IBM, the resulting sales figures usually give a bounce to the stock. Better still, if you coordinate your efforts with other execs in other companies, you can often make yourself a tidy profit.
During my time consulting for these banks, management did not want to hear about any other solution that wasn't IBM. I suspect that most Fortune 500 companies play a similar game with Dell product - and that would certainly help explain Intel's entrenchment.
Re:Figures (Score:3, Interesting)
ostiguy
Re:Figures (Score:5, Insightful)
Intel has been publishing some phenemonal research on new processor architectures recently. For example, "Continual Flow Pipelines" appearing in ASPLOS of this year [toronto.edu] shows some awesome potential. It is a novel new technique for a superscaler out-of-order processor that does not use things like reorder buffers which don't scale well with instruction window size. Surely Intel has patented this technique before publishing in an academic conference.
Intel will catch up rather quickly.
Re:Figures (Score:5, Insightful)
Normally Intel would have sand-bagged on their R&D and be able to respond quickly, but because of the catastrophe that is the Itanium they're stuck. Intel poured so much money and R&D brainpower into the Itanium that when it bombed they didn't have anything else to show.
Intel basically tried to pull a PS/2 with the Itanium. They wanted an architecture that they had exclusive control over and that they could charge up the ass for. Such schemes can be successful at times, but when they fail the consequences are devastating, which is exactly what we're seeing right now.
Add to that the recent string of catastrophes in the P4 arena that has actually led Intel to drop a core revision in favor of a modified P-III that was originally desiged for laptops, and you've got a recipe for a total cluster-fuck.
Intel is not out of the game yet, but they're hurting bad and it is going to take a LOT more than a bunch of journal articles to get them out of the hole.
Lee
Re:Figures (Score:4, Insightful)
Funny how that works. McDonald's may not make the best burger, but they sure sell the most!
Re:Figures (Score:2)
Re:Figures (Score:3, Informative)
At least with AMD we can say they moved to 64 bit, Intel hasnt really done anything.
Re:Figures (Score:2)
Re:Figures (Score:2)
Re:Figures (Score:2, Interesting)
Re:Figures (Score:2)
Re:Figures (Score:2)
Re:Fan Boy Alert (Score:2)
Re:Fan Boy Alert (Score:2)
Re:Fan Boy Alert (Score:5, Interesting)
And while you're at it...what's this about USB being broken and never fixed? I haven't noticed it on any of my AMD machines.
For the record, I have many, many Intel boxes, and many (though not quite *as* many) AMD ones as well. If cost is no object, and insano speed and/or 64bit isn't necessary, I'll choose Intel. If I'm paying for it, it will be an Athlon. If I want the fastest thing I can lay hands on, I'll get an opteron.
There is no point in bickering over vi vs. emacs. Or NVidia vs. 3dfx.
Re:Fan Boy Alert (Score:2, Informative)
The USB 2 didn't work and they had to bundle a sepearte card and turn off all the onboard USB.
That sucked
Re:Fan Boy Alert (Score:2)
Anyway, Intel may have a better track record with chipset reliabilility. I'm not real sure. But when I buy a chip and motherboard, I do enough research that if there's a bad chipset out there, I'm not getting it. These days that means that when I build an Athlon box I'm using nforce2. I'll admit, the AMD choice has changed
Re:Figures (Score:2, Interesting)
Re:Figures (Score:2)
Re:Figures (Score:3, Insightful)
I'm not sure if I understand you grammatically, but if you say that the USB of the AMD 760MPX doesn't work, then you're wrong. I have a MPX board (Tyan S2466N-4M) and I use the onboard USB on a daily basis. It works without problems. The AMD 760MPX is a very fine chipset for dual Athlons (much better than the AMD 760MP).
OK, USB didn't work with the old MP chipset. I'm not sure when they fixed the problem
Re:Figures (Score:2, Redundant)
Re:Figures (Score:2)
Re:Figures (Score:5, Interesting)
It shows in the excellent IPC scores of the hammer series, and the incredible scaling for SMP systems that Opterons enjoy.
So alpha technology lives on in a small way in the AMD hammers.
Re:Figures (Score:5, Interesting)
I'll take a chipset that work (never had a problem with my NForce2) over one that doesn't work with a major new technology (PCIe) any day.
Re:Figures (Score:2)
I wonder where I got "tumwater"?
(quick Google) Oh, Tumwater will come after Lindenhurst and adds other things on (like 16x PCIe, as opposed to Lidenhurst's 8x).
Well, I wasn't TOO far off.
Re:Figures (Score:5, Informative)
Re:Figures (Score:3, Informative)
It's not an old bug, I have an Nforce2-based motherboard and have that zzzzzzzzz always present in my speakers, and it even varies the pitch depending on CPU load.. imagine the annoyance. I can't beleive things like that still shows up in modern systems, but they do, in fact, I'm not really mad since the board didn't cost me 500$. Of course
Re:Figures (Score:5, Interesting)
Re:Figures (Score:3, Informative)
I'm using the Asus A7N8X, not the deluxe, and have no sound problems. The on board is better than my old SB16. The white box store that I deal with had serious trouble with the SB live Audigy in the deluxe version of the same Mobo. It was Creatives drivers and never did work right. The on board, through a 2 year old set of Klipch 5.1s sounded better than the Audigy did in any box with the same speakers. I don't really think sound cards are worth it any more.
Re:Figures (Score:4, Informative)
IT'S NOT A PROBLEM ANYMORE, NVIDIA AND SIS BOTH HAVE QUALITY CHIPSETS FOR AMD AND VIA HAS CLEANED UP IT'S ACT.
I'm sorry for shouting but damn, this hasn't been a valid argument for years and intel zealots are still spouting off about it.
plagiarism (Score:2, Informative)
Original Article (Score:5, Informative)
http://arstechnica.com/news/posts/20040804-4070.h
Re: (Score:2)
Comment removed (Score:5, Insightful)
Re:Infomation wants to be free. (Score:3, Insightful)
Disabled 64 bit extensions on first chips shipped? (Score:5, Interesting)
Does this mean that we will have disabled and enabled versions? Like the old 486SX and DX (SX I understood was a disabled/failed math co-processor). I suppose like all their other chip lines, each will be labled distinctly with some marketing nomenclature.
Re:Disabled 64 bit extensions on first chips shipp (Score:2, Interesting)
486SX - a 486DX with its FPU disabled.
486DX - 486SX with a working FPU.
487 - 486DX with a slightly different pinout for use in 486SX systems and sold as a "math-coprocessor;" actually, it would disable the 486SX and be used exclusively!
Source [ic.ac.uk].
Re:Disabled 64 bit extensions on first chips shipp (Score:3, Informative)
My guess is that it would work, but they've been fine-tuning it the whole tim
Re:Disabled 64 bit extensions on first chips shipp (Score:3, Interesting)
Later SXs may have omitted the FPU completely but given that the SX was what amounted to a "loss leader" for Intel, intended to hold back AMD & Cyrix from the gates, they never spent a whole lot of time engineering the thing.
The real fun was when Intel sold a "FPU upgrade" for some 486SX systems. The "FPU Upgrade" was nothing more than a rebadged 486DX chip that mounted in a socket close to the
Subdued Release (Score:5, Funny)
Re:Subdued Release (Score:2)
The Knights of NIH...
The last thread on Xeons... (Score:2)
Supposedly Intel released the chips in June too.
Re:The last thread on Xeons... (Score:2, Offtopic)
Re:The last thread on Xeons... (Score:3, Informative)
But rumor has it that Intel's 64-bit performance is no faster than its 32-bit performance, and slower than AMD's 64-bit performance.
Amazing (Score:5, Interesting)
Think about how big a jump it was from the i286 to i386 (16-bit to 32-bit.) That release was a major deal for Intel.
Re:Amazing (Score:2)
IIRC, nobody cared about 32 bit until Windows 95 came around, and even that was a hack. I don't rememer intel hawking 32 bit for 386s so much.
For a company whose main business is to businesses and retail, who in turn primarily use an OS with no x86-64 compatible variant, it is pointless. Thus why this is being promoted to the workstation and server market.
AMD's rare Athlon 64 ads seem to pay lip service to this missing OS issue. Giv
Two reasons why it's not hyped. (Score:5, Insightful)
2) The 64-bit instructions are reportedly emulated and are not as fast as the AMD equivalent. Therefore they will make x86_64-specific optimizations seem slow. They'd rather you use it for the 40-bit pointers, but to keep the word sizes 32-bit and not to use those extended registers.
It's a half-hearted effort to get the compatilibity where it matters (OS, database) while exploiting the fact that most of the code is still x86_32 with a sprinkle of performance-critical SSE* and that runs fine on Nocona.
Re:Amazing (Score:2)
Re:Amazing (Score:3, Informative)
Son, what are you talking about? Zillions of 16-bit apps use numbers bigger tha
Xeon-Nocona no faster on 64-bit code? (Score:5, Informative)
Though Xeon-Nocona has been available for more than a month [intel.com] it seems there there are no substantial reports on 64-bit performance of Nocona. Is there anyone here who can report anything about the 64-bit performance of Nocona?
Re:Xeon-Nocona no faster on 64-bit code? (Score:3, Interesting)
The processor is not in-fact a Prescott. IBM Blades infact use Prestonias today. Prestonia are 400/533MHz FSB Xeon processors. These processors have in reality been shipping for over two years. These are also dual CPU blades (can we expect to see EM64T enabled 4-way Foster CPUs?).
This is much more interesting than Noconas and Prescotts having EM64T technology, as it shows that the technology is being retrofitted into older curr
Re:Xeon-Nocona no faster on 64-bit code? (Score:5, Insightful)
On the otherhand, Intel seems to be marketing these chips as a way to get more memory on your motherboard (aka the way Apple did at first, "Now you can have EIGHT gigs of ram instead of FOUR!!!"). They're hoping this will be enough for most people, considering where these chips will be marketed (low-medium range server).
Besides, Intel's said it plenty of times: Netburst is dying. It was a foolish hack in the first place, but at least it gave them enough time to breed the Pentium M into what it is today.
Re:Xeon-Nocona no faster on 64-bit code? (Score:2)
I don't think they wanted to implement the whole command set, but since they had to, they did so as crudely as they could. I doubt they spent very much time trying to make this part of their chip fast; the same way they didn't try to make Itanium x86 emulation fast. The greater scheme of it all; they can say that this code is simply "flawed". Better than saying it, they can let people opinionate it ("hey, Intel's usually on top of the benchmark
Where are the 64 bit apps? (Score:5, Insightful)
At what point are people actually going to start making 64 bit applications? I'm not talking 64 bit linux or anything like that, I'm talking consumer level apps and games.
I see a lot of people upgrading to 64 bit chips, but what good does it do if there's nothing to utilize them? Is it just for bragging rights or what?
I'm a programmer and I have yet to see a need to get a 64 bit chip.
Re:Where are the 64 bit apps? (Score:5, Informative)
Among other things, it should let the OS map more than a few gigabytes of memory into the address space at one time. A 32-bit application will only be able to see 4 gigabytes (or 2, or whatever the limit ends up being after tag bits and OS space are reserved), but the total amount in use can be more, without an application rewrite needed. This is already done to some extent (my understanding is that the 32-bit processors have 36 bits of address space in total, with a 32-bit per process maximum), but moving to 64 bits gives a lot more headroom.
I see a lot of people upgrading to 64 bit chips, but what good does it do if there's nothing to utilize them? Is it just for bragging rights or what?
I'm a programmer and I have yet to see a need to get a 64 bit chip.
It's handy to have native handling of things like 64-bit integers, but addressable memory space is the most pressing reason right now. You'll be able to mmap() a file larger than 2 gigabytes on x86-64 machines (where up to now you had to use a non-x86 platform). You'll be able to hold more than 2 gigabytes of working data in RAM, which is significant if you're doing video editing (or heavy rendering or really heavy image processing).
Consumer apps and games will move into this niche in a few years (there are algorithms that let you trade off memory footprint and speed, and memory is cheap). But there are several places where the ability to address more memory is important _now_, even for user workstations.
Re:Where are the 64 bit apps? (Score:2)
and to answer your question, GCC handles them OK.
Intel is not the leading processor developer - they are the leading CONSUMER grade processor manufacturer. There are other bottom feaders below them too, eg. VIA.
Intel with a 64-Prescott (Score:2, Insightful)
That write up looks familar ... (Score:4, Informative)
Quick! (Score:3, Insightful)
Anyway
I'm still unconvinced about 64-bit computing for the present. I think most businesses will wait a long while before making upgrades based on this. One obvious reason is that software is compiled for 32-bit processors, but how much faster is say Gentoo compiled for a 64-bit AMD processor?
A lot of people's arguments defending 64-bit computing is that no software is designed for it. I'm sure I'm completely ignorant on this, but how well does gcc take advantage of it if I were to compile programs to make use of it?
Re:Quick! (Score:4, Informative)
There are also the "intangibles". For example right now software can only use about 3 gigs of memory without hacks (PAE and such). This is because there is only 4 gigs of address space and the OS and libraries must be in there somewhere, so most OSes give the OS 1 or 2 gigs of that address space. And you must map a library into each program's view of the address space, possibly into different areas. With a 64-bit address space, you could give a full 4 gigs to tons of programs, all while having lots of libraries loaded and have a simple linear addressing space for everyone. This simplifies things quite a bit. And when you need to use more than 4 gigs of data, you'll be able to without any performance hit.
The biggest difference you'll see are the registers. While it won't help you type faster into a word processor, it could very well help a game out.
Re:Quick! (Score:2)
Yup. Here's 3 reasons to get an AMD64 chip.
1. On-Die memory controller.
2. HyperTransport.
3. SSE2
Obviously the P4 and Prescott both have SSE2, but no other AMD chip does... and some programs (ahem, Premiere) require SSE2. And neither the P4 or Prescott (or Athlon XP) have #1 or #2.
Opteron Still Better (Score:5, Insightful)
Because the Opteron has an on-die memory controller. That can boost things up to 20% in some cases. It also makes designing motherboards easier because you don't need both a north and southbridge. It makes it harder to upgrade to a new memory technology, but it can be disabled allowing you to do that (I think). If they switched to that buffered "FB-RAM" or whatever (there was an article on the idea a while back on a big hardware site) that would fix that.
But anyway, Intel is stuck in a hard place. Because of the memory controller, their chips perform slower because of the extra latency, so they must ratchet up clockspeeds. The solution? An on-die memory controller. So why don't they do it? They CAN'T.
Intel has been pushing BTX for a variety of reasons (although most people blame Prescott's heat for it). But the way BTX is designed Opteron boards can't be made into a BTX form-factor because the memory is too far away from the CPU (there is too much electrical noise, IIRC). This means that Intel can't switch to an on-die controller without either changing BTX (what I think will happen because of AMD), or finding a way around the noise problem (little faraday cages?).
If you add in things like that the Intel chip only supports 36-bit address (I believe) while the Opteron handles 64-bit addresses (the actual bus is smaller right now, but that could easily be changed) and other performance factors (the top P4EE is outperformed in Doom 3 by a chip that costs more than $800 less, see the Inquirer) and Intel is in hot water.
All of this should be interesting to see what happens. Intel seems to be in trouble (performance wise, at least in the short term).
Re:Opteron Still Better (Score:2)
And everyone who can afford 2^36 bytes of RAM, raise your hand...
Re:Opteron Still Better (Score:2)
They did it many years ago as part of the ill-fated "Timna" project, which integrated a rambus memory controller on the processor. It was a cool and pretty performance oriented design, however it was intended for the value segment of the market -- and it was using a memory that was far more costly than SDRAM, so Intel killed it.
Whatever their reasons, the memory controller isn't on their current processors because it was design choice, not due to l
Re:Opteron Still Better (Score:2)
Rephrasing your point, they're committed to the non-integrated path by their choices. As AMD is to theirs -- so this should b
Re:Opteron Still Better (Score:3, Informative)
But the major reason to do it (at least in the server space) is because it's not shared. So if you have a 4 processor Intel server (which has a shared memory bus through the northbridge), and you have 1 GB/s of memory bandwidth (way to low, just an example), then if all processors are accessing memory they each get about 250 MB/s of data. If you go up to 8 processors the total
Re:Opteron Still Better (Score:3, Interesting)
So.... To get beyond 8 processors in a true global-memory ccNUMA configuration, A
A few months late to the party... (Score:2, Interesting)
Re:A few months late to the party... (Score:2, Informative)
http://www.nationmaster.com/encyclopedia/DEC-Alpha [nationmaster.com]
AMD welcomes Intel to the world of AMD64 (Score:5, Interesting)
It's kind of funny to watch. Intel is choosing their words very carefully. They're saying things like, the new chip "will run programs currently being developed for AMD's 64-bit processors with very little modification." They absolutely refuse to call the new chip "AMD compatible" even though that's exactly what it is. Intel is having a lot of trouble facing the facts: they poured zillions of dollars and years of R&D into an architecture that nobody wants (Itanium), meanwhile AMD got it right (Opteron) and now they're playing catch-up.
You'd think that Intel, moreso than anyone else, would know that you just can't kill x86.
Re:AMD welcomes Intel to the world of AMD64 (Score:3, Informative)
The Itanium series does have a few high-availability features nonexistent in Xeon or Opteron, and is a heavy-iron type chip. Unfortunately, the market for those are slim at best compared to the desktop and small server market. It doesn't help that there is something of a backlash against high-watt computers, for example, a lot of
Re:AMD welcomes Intel to the world of AMD64 (Score:3, Informative)
No, I'm sure that internally at least they know only too well that they stuffed up big time. That's got nothing to do with not calling these chips "AMD compatible". They don't want to do that because in the public's eye, that would make AMD chips the real deal, and Intel's ones a copy. If they're the same speed (all most people care about) and about the same price, then people will buy the "genuine" ones, not the Intel "copies".
It's marketing, pure and sim
So we wait for an Intel 64-bit because of slow MS? (Score:2, Interesting)
At the time, he said that Intel wouldn't enable the feature until Microsoft released a 64-bit version of Windows; that operating system is expected later this year.
But according to Computer World,
Microsoft Corp. has further delayed versions of Windows for PCs and servers equipped with x86 processors with 64-bit extensions. Analysts said the extra delay will slow the advent of 64-bit desktop computing and provide a head start for rival operating systems on servers.
Windows S
A Note on memory addressing (Score:5, Informative)
Thats right, the same 36 bits that intel has supported via PXE for years...
Thus, total system memory size for these processors is limited to 64GB, meanwhile the per-processor limit for AMD chips is 1TB, 256TB total in a system (max 256 CPUs, if anyone ever makes a board and Hypertransport bridges capable of supporting such a large number of chips).
Anyway, it is a big difference, and it hints that the actual implementation may be the same old slow PXE implementation intel has had for years (since the pentium pro, if I remember correctly).
------------ This post was made while on percocet and no spell checking has been done. deal.
Re:A Note on memory addressing (Score:2, Informative)
I know it's the percocet talking, but I think you mean PAE [thefreedictionary.com] not PXE [pxe.ca]...
Apart from that - absolutely correct.
thefreedictionary.com (Score:5, Informative)
Please do not post links to thefreedictionary.com - they are a dodgy site which repackages Wikipedia [wikipedia.org] content, with ads, for profit, whilst stretching the GFDL [wikipedia.org] as far as they possibly can.
Look at that link you posted - you'll see a credit to Wikipedia at the bottom. Now disable javascript in your browser and refresh - ooh, the credit is gone! They insert it in with javascript rather than putting it in the body of the page to ensure that Google doesn't pick it up. Why? Because a link to Wikipedia's article would help lift Wikipedia's pagerank above that of thefreedictionary.com.
Just say no, and if you want to read about PAE, read the original [wikipedia.org] Wikipedia article.
Re:A Note on memory addressing (Score:5, Funny)
Oh, no! Does that mean I can't run Longhorn?!
So what.... (Score:2)
Intel Marketing Blunder (Score:5, Funny)
Who wouldn't want a chip that's one better than the competition?
Dell is shipping 64-bit Pentium 4 workstations. (Score:5, Informative)
Also, Anandtech just posted a new roadmap [anandtech.com] with some info on upcoming 64-bit Pentium 4 CPU/chipsets for the desktop. The Intel 925XE chipset (with 1066MHz FSB) will ship in October along with 64-bit Pentium 4 "F" processors. "F" supposedly means it's a 64-bit Prescott.
Where does that leave Itanium? (Score:3, Interesting)
I am bringing this up because Intel refused for a long time to bring in a 64-bit x86 due to invement with HP for Itanium. It seems so odd that we have a chip based on 1970's technology.
Itanium was supposed to be surpacing x86 by now like NT replaced win95 derivitives. Intel has a notion of sunkin costs while HP would rather beat a dead horse than admit it failed after billions of billions of dollars of development. I guess its the culture of zero accountability and perfection with no room for mistakes that Fiona implemented.
x86 just wont die.
I would prefer to see the Alpha as an eventual replacement for the aging x86 and its a shame it was bought up just to boast the Itanium.
Well long live the Pentium 64-bit and forever x86.
Welcome to Trusted Computing. (Score:4, Informative)
Prescott is also Intel's first processor to support a security technology code-named Le Grande. While Intel has not yet detailed the technology, it is believed to provide a protected space in main memory for a secure execution mode required as part of Palladium, a new PC security scheme being developed by Microsoft Corp.
Le Grande is Intel's codename for Trusted Computing. HP's codename is ProtectTools, Cisco's codename appears to be either NetworkAdmissionControl or SelfDefendingNetwork, Phoenix BIOS code name is CoreManagedEnvironment, and of course we all know Microsoft's codename was Palladium and now is NaGSCaB and is slated to appear in Longhorn.
If you scroll down near the bottom of this page [chip-architect.com] you can catch a look at a micrograph of the Prescott from about a year ago. Note that the Trusted Computing core is it's own an entire CPU and memory and support structures, and eats up about 20% of the chip. In other words Trusted Computing core ties up around 25 million transistors of real-estate, or about half of a Pentium 4.
It will support encrypted code (to secure it against you, the owner), it will encrypt RAM access (again, secure against you) and take over a portion of your cache. It will carry a unique key to identify you and your machine, but far more powerful than the old CPU serial numbers. It will forbid you to know your own encryption keys and prohibit you from decrypting your own data. I know it's designed to work with a "secure clock" (wouldn't want you the owner to be able to "tamper" with the time, now would they?), but I'm not sure if the secure clock is inside the CPU or planned to be external.
AMD has their own Trusted Computing project, but I have been having trouble digging out any hard info. It *may* be incorporated into the Opteron processor.
Transmeta has a trusted Computing project too, the TSX system - Transmeta Security eXtensions. I beleive initially appearing in the Caruso5800.
Welcome to tomorrow. Resistance is futile, all your base already belong to us, Slavery is Freedom, and always remember The Computer Is Your Friend.
-
Prescott? Surely Not ! (Score:3, Interesting)
Characterised by:
1). Rambling incoherent communications.
2). A violent temper which could blow at any time.
3). A tendancy to do a rapid about about-face whenever challenged by the realities of hard work.
Do we really need a chip like this?
Note: For those not in
Re:AMD wins? (Score:2)
Re:AMD wins? (Score:4, Insightful)
You're joking right? That is barely true. I suspect for integer performance, the Opteron is the strongest out of all of them. Look at the SpecINT scores, it is dominated by x86 at the top end (Xeons & Opterons) and they are way above everything else at all.
For FP, you're half right. The Itanium2 & POWER4/5 are more than a match for the Opteron and will beat it (especially the POWER5). SPARC & MIPS are waaaay slower. No-one uses them for raw MHz performance, more for a large number of CPU systems.
My REAL WORLD tests show the Opteron is 33% quicker MHz for MHz over Sun's UltraSPARC3/3i/3+ processors. That is a problem for them when the Opteron clocks so much faster too!
Re:At least for now (Score:3, Insightful)
As long as Microsoft leads the desktop operating system market, and as long as people need backwards compatibility to apps compiled for x86."
Remove those two requirements, and you'll see a different architecture become dominant. But, really, is it likely to happen any time soon?
Re:strange (Score:2)
http://www.microsoft.com/windowsxp/64bit/evaluati
Haven't tried it yet though as I run Linux. Also FYI: 64bit support was introduced in the 2.4 kernel. Not that 2.6 didn't vastly improve on it(IMO).
Re:strange (Score:2)
http://www.microsoft.com/windowsxp/64bit
Actually, no you can't. They took it down for some reason. I really don't know why, it's been up there since february, but they took down the link 2 days ago and claim that it will be back up in "mid august".
Re:My Question... (Score:2)
Re:makes sense... (Score:2)
It would go to explaining some of the outrageously high hardware requirements for Longhorn, and although it is a number of years off from release, and one could argue that by the tim