Slashdot Mirror


Itanium Will Only Be Partly Supported by Longhorn

ver.sicher.ungsvergleich writes "Although stopping short of pulling the plug entirely on Itanium, MS has said that Longhorn will only be able to work for a limited number of higher-end jobs. On the positive side, Microsoft does see a future for the chip, but that 'big iron' slot is not exactly what Chipzilla envisioned as Itanium's future."

234 comments

  1. Role for emulation? by CdBee · · Score: 3, Interesting

    Microsoft recently bought Connectix, makers of VirtualPC, ostensibly to use their system virtualisation technology in new Microsoft products.

    Will virtual X86 servers running on Itanium be an available option to supply services not supported by native Itanium code?

    --
    I have been a user for about 10 years. This ends Feb 2014. The site's been ruined. I'm off. Dice, FU
    1. Re:Role for emulation? by Lonewolf666 · · Score: 1

      That would have to include some sort of X86 emulation. Which is performance-wise usually not a good solution.
      But then again, Linux exists for the Itanium. And in the "high-performance areas" TFA mentions, it has a good reputation. I suspect Microsoft is throwing away the Itanium market with this move. Which may not hurt them too much considering the low market share of the Itanic, but still...

      --
      C - the footgun of programming languages
    2. Re:Role for emulation? by Anonymous Coward · · Score: 2, Informative

      Microsoft recently bought Connectix, makers of VirtualPC, ostensibly to use their system virtualisation technology in new Microsoft products.

      You call February 19, 2003 recent? C'mon man, at least do some research. That's over two human years and 14 dog years. That's 23.46 technology years! This Google search turns up links regarding Microsoft's purchase. This is the second link in the search!

      Jesus christ, I knew slashdot was behind by a couple weeks when they reported things but you could usually rely on the readers. Two years is inexcusable. Turn in your Google access pass at the door on the way out please. Any Google API information you have downloaded should be deleted immediately. search.msn.com is now your only search engine.

    3. Re:Role for emulation? by Synli · · Score: 1

      Yeah, and your post will not be modded up, while his was. Maybe he knew it, but used the word "recently" to attract mods (the "hey there's something new I discovered, mod me up" attitude.)

      --
      "Two things inspire me to awe -- the starry heavens above and the moral universe within." - Albert Einstein
    4. Re:Role for emulation? by Solra+Bizna · · Score: 1

      To those of us who still have computers from 1980, 2003 is recent.

      -:sigma.SB

      --
      WARN
      THERE IS ANOTHER SYSTEM
  2. I think it's time to pull the plug by roman_mir · · Score: 4, Funny

    on Longhorn.

    Where the hell is Netcraft when you need it?

    1. Re:I think it's time to pull the plug by Anonymous Coward · · Score: 2, Funny

      I read in the newspaper today that Iran is refining Itanium ore to produce enriched Itanium... but they claim they are not building an Itanium bomb. This is just the excuse the U.S. needs to invade Iran! Darn right it's time to pull the plug!!!

    2. Re:I think it's time to pull the plug by Metteyya · · Score: 3, Funny

      Netcraft confirms it: Longhorn/Vista is dying before even being released (must... resist... writing... "born").

    3. Re:I think it's time to pull the plug by CapnGrunge · · Score: 1

      (Apologies to John Greneby and damn^Wthank you, chars-per-line checker)

      Longium

      Shadow: Little Borg, who carries the name of the most dreadful piece of sh^Hoftware... could you please bring me something from your corporate headquarters?

      Borg: Of course, dear Shadow, what is it you so humbly ask to endow?

      Shadow: Walk back to Redmond, dear child, and make it your company's tomb... for all I yearn for lies within your Development Room. I once heard of a program that will become like no other. Could you please bring me your still unborn OS?

      Upon receiving it, the Shadow bowed in gratitude, completing her task.

      Would you like anything in return, may I ask?

      Borg: Please, I hope you won't find me wrong, I would like to have the mostbells, whistles and smoking mirrors an OS can sport. But no matter what I want, I would find a captive customer The most relevant.

      Shadow: I'm sorry, dear little Borg, captive customers I can not give. It is sadly beyond my power.

      Borg: Then I would like my OS back. For this little license agreement of ours, just turned awfully sour.

      What good are you if you make me weep? Please have my OS returned by the gates of my keep.

      Shadow: Neither your OS I can give you. What you have licensed is licensed, I merely strive for a way to break even.

      Seeing my offer is merely out of kindness, this child will never know the embrace and extend of your fortress.

      Borg: Then I wish for a way to have you undone, Mr. Shadow. I want you mauled and buried by the darkest and most blighted meadow.

      Shadow: Fair enough, little Borg. Without feelings of either vain or rue, I will grant your one wish 'come true.

      Without honour, without grace, you will travel to darkest place. Untouched by the vilest of gloom, your skin will always run paler than our brightest Moon.

      Travel the road of which I pointed, and be forever gone.

      For sure, one day you will have me undone.

      Borg: Thank you kindly, shadow of whom I don't know.

      --
      I see 57005 people
    4. Re:I think it's time to pull the plug by dtfinch · · Score: 1

      Longhorn will spread primarily through OEM installs, as XP did, until it becomes the dominant desktop operating system despite very few people actually buying it themselves.

  3. Yay! by machinegunhand · · Score: 3, Funny

    Does this mean I can get out of my MS EULA now?

  4. Intel is losing it's edge by confusion · · Score: 3, Insightful

    Between this and their roadmap that almost exclusively involves power consumption improvements, Intel is starting to lose it's edge over AMD.
    From talking to Intel folks quite a bit, it seems like there is a lot of blind pride on Intel's part in their product line and vision, and they dismiss most anything that I raise as an issue with their performance vs. AMD, and that's not a good sign to me.
    Intel is not dying that's for sure, but they're going to have to make a course correction and not make another decade long mistake like itanium.

    Jerry
    http://www.cyvin.org/

    1. Re:Intel is losing it's edge by Vengeance · · Score: 2, Funny

      Starting to lose its edge?

      Brother, the Athlon 64 was the file that flattened that edge down to nice rounded stump.

      --
      It was a joke! When you give me that look it was a joke.
    2. Re:Intel is losing it's edge by Anonymous Coward · · Score: 0
      From talking to Intel folks quite a bit, it seems like there is a lot of blind pride on Intel's part in their product line and vision, and they dismiss most anything that I raise as an issue with their performance vs. AMD, and that's not a good sign to me.

      What a strange coincidence. That's exactly what things were like a Sun regarding Linux vs. Solaris and UltraSPARC vs. x86 (including Opteron).

      Now Sun is only surviving by laying off a few thousand staffers every few months to maintain break-even with some strange hope of jam tomorrow.

    3. Re:Intel is losing it's edge by Anonymous Coward · · Score: 1, Insightful

      As someone who runs a 200 processor linux cluster, let me say that despite Intel's lower performance, if they can do a higher FLOPS per Watt than AMD, then they'll get the next contract. It's all about heat dissipation and power usage now in the HPC linux world (microsoft, BTW, will likely never "crush linux" now that linux is as entrenched in HPC as windows is on the desktop)

    4. Re:Intel is losing it's edge by ScriptedReplay · · Score: 1

      Speaking of Intel's roadmap, I have to wonder at the future of their plans to push Itanium by merging the chipset support with Xeon, now that the "Itanium ecosystem" looks to be going the way of the dodo ecosystem. With MS less and less interested in their platform and HP having second thoughts, even economy of scale might be too late to save it. Especially since the industry learned that there's no need to instantly bow when Intel flexes its muscle (how many computers with BTX form factor are sold these days?)

    5. Re:Intel is losing it's edge by CubicleView · · Score: 3, Insightful

      I'm probably way off (a little knowledge is a dangerous thing as they say) but as I understand it, most of the money in the comming years will be in mobile technologies. Big improvements in batteries and this move to fuel cells etc will offer more power but efficiency of the processor will still be hugely important. Particularly considering processor tech is at a level that even basic models offer more than enough power for most users. Of course the server market is different I'm sure (and being completely ignorant of it I won't guess at intels future there)

    6. Re:Intel is losing it's edge by walshy007 · · Score: 1

      I think it's completely a matter of intel's marketing section having too much power. the fact the faster 2ghz etc dothan cores (which are fairly old now) can outbench an amd fx57 when it's their mobile processor says something. which leads to one simple question... why did the prescott even exist? when they've had a faster proc that takes 1/5th the power all along. My conclusion is simple, marketing, it's a lot easier to market a 3.6ghz compy than a 2ghz one that outperforms it. clock for clock the dothan outperformed even amd's. and yet, they left it generally (asus p4p800 adapter excluded) to the laptop market. and since when do gamers use laptops? lol

    7. Re:Intel is losing it's edge by quanticle · · Score: 1

      As I see it, the Netburst architecture of the Intel P4s was to provide more performance on things like video editing, and multimedia, at the cost of power efficiency and performance on non-video applications. However, I think Intel overestimated the demand for high-performance video/multimedia editing machines, which explains its current backtracking to the Dothan core.

      --
      We all know what to do, but we don't know how to get re-elected once we have done it
    8. Re:Intel is losing it's edge by Anonymous Coward · · Score: 0

      no, intel didn't overestimate the demand for those high end video and multimedia machines, they overestimated Adobe and Avid's ability to deliver compelling software for the PC platform. Left the market to be gobbled up by Apple with Final Cut Pro which is a superior application.

      The reason those things never took off on PC's is because Apple dominates that sector. (Trust me they do, I've switched as a student learning the video field, well more of the field than i knew already).

    9. Re:Intel is losing it's edge by christophersaul · · Score: 1

      Well said, because we all know Sun doesn't actively sell and promote a version of its own OS for x86 and x64 and doesn't sell Opteron kit.

    10. Re:Intel is losing it's edge by shywolf9982 · · Score: 1

      Okay, let's clarify that being less power-hungry is a good thing. I dunno how's the situation elsewhere, but here in Italy the electric power costs a lot. And computers + AC + everything elseis making our life pretty hard (power goin out randomly and such).

      If you add to that that switching from a residential 3.5KW contract to a mid-office 6KW one costs you about 100$ month more (just to actually "have it", no consumes included) I do think that requiring less power _is_ a very important thing. Probably the most important. Right now, at work I'm having big problems in trying to convince my boss to upgrade the electric power contract, but he's refusing (I cannot blame him, it costs a lot). And sometimes our supply gets cut cause we get over the maximum power.

      --
      nbody2002:If you can read this you may be addicted to the internet
    11. Re:Intel is losing it's edge by Fweeky · · Score: 1

      Ah, servers, yes. Immortal power supplies and HVAC doesn't come cheap; when you start having to live within a power and BTU budget, being able to drop a few KW per rack is *really* appealing.

      This comes hand-in-hand with multiple-cores per chip; server applications tend to have a lot of concurrency, so trading off some raw performance per core for the ability to fit 2-4 on a single chip with a sensible power envelope is a great win. So what if a single core has 30% less throughput if you have twice as many of them to spread load across?

      Even for the average user, the reduction in latency and greater ability to multitask probably outweighs a few FPS in Doom 3.

    12. Re:Intel is losing it's edge by Anonymous Coward · · Score: 0
      Brother, the Athlon 64 was the file that flattened that edge down to nice rounded stump.

      I'll admit that it helps in those cold Wisconsin winters, but the frequent lockups make it undesirable. Intel truly know how to make a processor.

    13. Re:Intel is losing it's edge by Overly+Critical+Guy · · Score: 1

      Laptops are overtaking desktop sales. Mobile computing and lower power consumption is the future as devices get smaller and faster.

      --
      "Sufferin' succotash."
    14. Re:Intel is losing it's edge by laffer1 · · Score: 1

      Ahh grasshoper, but then intel got apple as a customer. All is not lost...

      Prepare to rebuy all your software.. i know i am.

    15. Re:Intel is losing it's edge by dcam · · Score: 1

      Starting to? What exactly do you mean?

      As far as I can see, intel lost its edge over AMD during the race to 1Ghz back in the Athlon/P3 days.

      I've been watching this race for a while and the only thing intel has produced that is was/is better than AMD has been the Pentium M, until the last 2 years, the xeon. If I have missed something, please do point it out to me. Since that release of the Athlon, for the desktop and now the server, AMD has consistentently produced, better cheaper CPUs that intel.

      As far as I can see, the only advantage that intel has over AMD is manufacturing capacity.

      --
      meh
  5. I hate 3 day weekends. by Anonymous Coward · · Score: 3, Interesting
    Talk about slow news day.

    Intel is in transition as far as processor direction, so there's no suprise here. Itanium has been dead for a while. The Microsoft "support" is there only because it's already been written and there probably is some support agreements already in place.

    The real news would be what the sucessor to x86 will be.

    1. Re:I hate 3 day weekends. by Anonymous Coward · · Score: 0

      Go volunteer or stop bitching.

    2. Re:I hate 3 day weekends. by MaskedSlacker · · Score: 1

      The Cell.

  6. Is this really a big deal? by CTho9305 · · Score: 4, Interesting

    Sure, Intel may have originally hoped to migrate the world to IA64, but given the wild success of AMD64 in bringing 64-bit to the x86 world, it doesn't look like that's happening. The Itanium chips Intel is releasing are obviously not aimed at tasks that could be handled by a 386 with some SCSI drives ("fax server"? a file server?)... who is going to use a multi-thousand-dollar CPU for anything other than database|web|high-end server anyway?

    1. Re:Is this really a big deal? by el_womble · · Score: 3, Interesting

      OK - I know nothing about this, so it is a genuine question.

      Should we be pleased that Itanium failed?

      I mean, on one hand /. hates x86 bloatedness, on the other hand we slapdown this attempt by intel to escape the aging architecture. If AMD hadn't stepped up and provided a chip that does both 32 and 64 bit ops would we finally be on the verge of dropping x86 all together?

      Are there reasons other than poor support from Micorsoft for Itanics massive failure? Is it a poor arcitecture?

      Like I said, I genuinely don't know.

      --
      Scared of flying, pointy things snce 1979!
    2. Re:Is this really a big deal? by Anonymous Coward · · Score: 0

      Itanium does nothing against bloat - in fact, its more bloated than X86 and it hardly has any legacy crap in there. /. love arches like PPC and Alpha which given the kind of funding and research x86 have had would be blisteringly fast and extremely cheap.

      These days however, x86 is becoming very nice despite the legacy. Things like ACPI are a pain, but the architecture itself is quite elegant.

    3. Re:Is this really a big deal? by jiushao · · Score: 5, Interesting
      Are there reasons other than poor support from Micorsoft for Itanics massive failure? Is it a poor arcitecture?

      In the world of good compilers originally envisioned by HP/Intel: No.
      In practice: Yes.

      Why? Because compilers aren't nearly as good as HP/Intel hoped but state of the art Out-of-Order processors are great. There is only so much theorethically possible ILP to extract in regular code, and good OoO chips extract most of it in an automatic fashion from existing code. So the hardware guys did a better job here than the software guys, and the Itanium bet on software.

      To clarify on OoO processors doing most of the possible work in extracting ILP: Even if the instruction window was increased to infinity (that is, all ILP is always found) it would still not yield dramatically much better performance (I have seen estimates of about 25% best-case). So even with a perfect compiler there is just not much to gain, and we do not have perfect compilers. This very high level of performance in extracting ILP is what is forcing the new shift to TLP with architectures like the Sun Niagara.

      I don't think we should be pleased that the Itanium failed. As I have often discussed in the past I think Intel really deserves a lot of credit, they are the undisputed top dog in the market, and despite that they are also one of the companies that consistently attempt new different approaches in high-profile products. Neither the Itanium nor the Netburst (which really is interesting and innovative technology) worked out well, but it is trying things that makes technology move forward.

      That's not to say that AMD is a bad company, they managed to make the best x86 implementation yet, which is great (though I still consider the K7 to have been the golden age since their pricing structure truly was incredible then).

    4. Re:Is this really a big deal? by aaronl · · Score: 0, Troll

      Yeah, there are a lot of reasons. These are a few that come to mind: The Itanium was/is incredibly expensive. Too many programmers are incredibly lazy and would have to do more work. Compilers took a little while to get up to speed with IA64. Linux was the only platform that ran on it natively at release.

      I would've preferred IA64 to the AMD hybrid. I also hate the stupidity that is the x86 architecture and would love to see it die. Then again, I'd also love to see IDE/SATA die and have the industry come up with a better standard; we could call it SCSI. It's be nice to use standard bus interfaces, too. We could drop PCIe and use PCI-X, instead, and be compatible with all our old PCI and PCI-X cards.

      The x86 world seems to always choose the wrong answer when presented with a problem.

      What can you do, though. "x86: the worst of *all* worlds."

    5. Re:Is this really a big deal? by Krach42 · · Score: 1

      If by "elegant" you mean "baroque" and "excessively intricate".

      Making x86 fast has been perhaps the most incredible feat in the existence of man-kind. And it's also been one of the most damaging. If Intel had never spent a buttload of money and come through with the Pentium and produced a CISC chip that could compete against the RISC chips, because in its core it is a RISC chip, then the world would be walking around with much better performance per watt RISC chips running everything.

      Perhaps, we might have even have seen the chip architecture become a commodity (like it really should be) where it was just an accepted fact that there are a ton of architectures out there, and that it's just laziness in programming that a company would target only one architecture.

      Seriously. Look at Linux. Except for those proprietary programs that you just can't control, the chief majority of Linux runs on just about every chip that Linux supports (some exceptions can be made for reduced Linuxes, like uCLinux etc)

      Now, if the FOSS community can make programs that compile and run correctly across 8 architectures and 8 POSIX operating systems, and Blizzard can make all their games run on Mac OS and Windows.... Just WHAT THE HELL keeps companies from actually making their programs CPU-agnostic?

      --

      I am unamerican, and proud of it!
    6. Re:Is this really a big deal? by ciroknight · · Score: 1

      I don't have mod points, but I want to thank you for a nice, coheirent post on why both current microprocessor companies are good. Not too many of us left here on /.

      --
      "Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
    7. Re:Is this really a big deal? by Anonymous Coward · · Score: 0

      You are confusing architecture with the instruction set.

      The X86 architecture IS quite elegant - compared to IA64. The instruction set, while containing many legacy bits, IS very good. It allows compilers to take advantage of system busses in ways that many RISC instruction sets dont.

      You may be fond of RISC, but that performance per watt can be achieved using x86 - there just has been little incentive to do so - so far.

      Like it or not, x86 is the best, so what if its a microcode on top of a number of RISC architecures?

    8. Re:Is this really a big deal? by cow-orker · · Score: 1

      Well, _C_ compilers are bad. That's not a fault of the compilers, it's to blame on C. If only people would put some effort into modern languages and actually using them...

      In the meantime the sensible thing to do is not throwing yet more silicon on OoO execution, but doing this in software _at_runtime_. That is, Transmeta's code morphing is right. HP's Dynamo is also the right thing.

      A sensible instruction set is also of benefit. On an ix86 with its measly 8 almost-general-purpose registers, a lot of instructions depend on each other. You get better results with more registers.

    9. Re:Is this really a big deal? by cow-orker · · Score: 1

      Hmpf. Actually Intel buggered nearly everything in its history but the ix86 line and the StrongArm. They built interesting things in the 80s and 90s, like the i860 and i960. Both of them were broken in some way and then a budget cut killed them.

      Ix86 was broken from the beginning. Crappy instruction set, stupid addressing, the 80286 made everything even worse (just 4 bits more address space and then the A20 gate). The most astonishing thing in ix86 history is how they saved the i386, which really is a new processor with a compatibility mode... Intel only stayed on top in this market, because they had backwards compatibility working in their favor.

      That leaves the StrongArm/XScale as real success. And that design was bought (ah, litigated, actually) from DEC.

      Should we be pleased that Itanium failed?

      Maybe not, but it may be inevitable. The design may indeed be subtly broken.

      If AMD hadn't stepped up ... would we be dropping x86 all together?

      No, we wouldn't. Windows doesn't run anywhere else, MSFT seems too inept to port it, and the world doesn't seem to like going on without Windows. Instead we would invent "enhancements" to the Pentium, new addressing modes like those in the most despicable 80286, kludge support for them into Windows, like the abomination that was "i386 enhanced support" in Windows 3.0, and go on addressing terabytes on a geriatric processor architecture.

      Come to think about it, this has already happened (PSE or whatever Intel calls it), it just isn't in widespread use yet. Meanwhile the Alpha and PA-RISC died. What an ugly economy...

    10. Re:Is this really a big deal? by jiushao · · Score: 1
      Well, _C_ compilers are bad. That's not a fault of the compilers, it's to blame on C. If only people would put some effort into modern languages and actually using them...

      Yeah, this is to some extent true. OoO chips are a nice deal though since they of course also benefit from better compilers, even the complex predicting OoO chips hedge their bets and include a few SIMD units in the mix to be able to capitalize easily on explicit parallelity. But to be practical; Most languages in popular use today are not very easy to get to run well on an Itanium.

      In the meantime the sensible thing to do is not throwing yet more silicon on OoO execution, but doing this in software _at_runtime_. That is, Transmeta's code morphing is right. HP's Dynamo is also the right thing.

      There is no real reason to throw more silicon on complex logic. As I insinuated in my post the wall has pretty much been hit as far as ILP extraction goes. Software solutions are interesting, it is a bit steep to call them "the right thing" at this point since they haven't really proved themselves in practice. It seems likely that we will see a lot more work in that area however.

      A sensible instruction set is also of benefit. On an ix86 with its measly 8 almost-general-purpose registers, a lot of instructions depend on each other. You get better results with more registers.

      This is not really a big problem in practice with the heavy renaming going on in modern x86 implementations (the Northwood has 128 internal registers, the K8 has 96 I believe). As soon as an instruction is decoded all registers used in it are changed to ones from the much larger "actual" register file. Independent code reusing the same register will be correctly renamed to different internal registers and run in parallel. There is some level of overhead involved, but it is a very effective technique in practice.

    11. Re:Is this really a big deal? by renoX · · Score: 1

      You forgot one thing in your analysis: Itanium architecture is only in the hand of Intel (maybe HP too? Don't know if they have the rights to produce CPUs), whereas x86 can be made by Intel, AMD, IBM, Cyrix, etc..

      While I dislike very much the Itanium architecture (PPC, Alpha, ARM Thumb2 mmmh), it is obviously much better than the POS x86 that Intel made.. but removing competition?
      I'll stick with x86, thanks!

    12. Re:Is this really a big deal? by renoX · · Score: 1

      I disagree about your point about 8 register not being a problem: register renaming help but if the compiler don't see the register, it may have to spill a register in memory to make room, register renaming can't do anything about it.

      I think that going from 8 to 16 register has made something like a 20% improvement for the x86-64.
      So 1) it is a big improvement 2) 8 register is a big problem in practice: you take a 20% hit even with register renaming (in pratice the loss is even greater as the new register are disadvantaged by having to use bigger instruction to use them).

      Also remember that register renaming is not only used by x86, it is used also by the RISC CPUs.

    13. Re:Is this really a big deal? by jiushao · · Score: 1
      8 registers is a bit on the lean side of things yes, considering the amount of code that has to be generated to handle it. I were just stating that instruction dependencies are not introduced by reusing registers on modern processors.

      To somewhat offtopic comment on the x86-64 register extension: It is still an obviously good idea. Spill code does not actually have to hit memory as long as there are rename registers left, but having to insert tons of spill code will still beef up the number of instructions that have to be chewed through. As such the x86-64 fixes things up nicely. In fact, 16 register might really by enough. Going to 32 registers might yeild diminishing returns, 16 will be able to hold most activly used variables and since the spill code is not that expensive to execute (without the memory access) it is mostly enough to keep the spills out of inner loops. Lucky for all of us that the x86-64 appears to be becoming an universally accepted extension to the x86 architecture.

      Register renaming and microoperations being leveraged in modern RISC implementations (POWER4 and thus the PPC970) just shows the success of the approach, now even the ever so popular PowerPC instruction set is considered too complex and limited to be executed directly. This really shows how well implemented the x86 is these days, while it was driven by a greater need it still had (and still has) a lot of very good designs before the competition got there.

      Just one small comment: "in pratice the loss is even greater as the new register are disadvantaged by having to use bigger instruction to use them" is a dubious argument since having more registers necessarily means that larger instructions have to be used. Considering the performance of a 16 GP register architecture if a register can be decided with 3 bits is a somewhat pointless exercise. The x86 has a very space-efficient instruction encoding no matter how one looks at it (incidently 'space-efficient' is probably the only nice thing one can possibly say about it :).

    14. Re:Is this really a big deal? by Krach42 · · Score: 2, Insightful

      I'm not confusing architecture with instruction set. If you're talking about the x86 architecture, then you're talking about all x86, not just one specific implementation.

      I'll agree that the later designs have been very nice. The Pentium-M and Pentium-D, along with the AMD designs are all incredible.

      You say that the x86 design allows you to to take advantage of system busses in ways that many RISC instruction sets don't, but there's nothing that would stop them from doing so, except there's been little incentive to do so.

      Yeah, you can make x86 perform well per watt. I'm not arguing that you can't. This is the very reason that Apple is switching to the x86, because Intel's roadmap is focusing on the Performance per Watt.

      Like or not, x86 is *NOT* the best. It's just the *FASTEST*. Which does not make it the best. Because "best" encompasses a number of fields where not the majority of it is "fastest" for me.

      I have philosophical objections to CISC designs, same as many people have philisophical objections to monolithic kernels. Does this mean that CISC and monolithic are bad? Does it mean that they are slower? No, quite the opposite, they are faster, and they're not "bad". They're just not as good as what could be done.

      --

      I am unamerican, and proud of it!
    15. Re:Is this really a big deal? by Trepalium · · Score: 1
      If you think they're always coming up with the wrong answer, maybe you don't fully understand the question.

      Re: IDE/SATA vs SCSI: SCSI is far more complex than ATA/SATA and compatibility concerns. If you want to make an ATA controller, you must implement the entire spec. If you want to make a SCSI controller, large portions of the spec are optional. These additional features mean SCSI can give greater performance than ATA drives, but it also means that while ATA has become simpler and simpler to set-up, SCSI has become more and more complex. Things like CS and asynchronous speeds (each device runs at it's maximum supported speed) on the ATA bus serve to make ATA easier to deal with, while the termination, SCSI IDs and synchronous speeds (each device runs at the slowest common speed on the bus) of SCSI require more planning.

      Re: PCIe versus PCI-X: This change is inevitable. PCI-X was a hack (much like VLB) to get more bandwidth out of existing PCI hardware. Plug a PCI device into a PCI-X bus, and oops, all your devices are now limited to 33MHz. PCIe is a good technology, and replacing PCI with PCIe is a good thing, just like replacing all those ISA cards with PCI was a good idea. PCIe may not have an performance wins over the highest-end PCI-X right now, but it's a lot cheaper to manufacture (you don't need a separate PCI bus controller for each 16x/32x PCIe card as you would with a 133MHz 64-bit PCI-X card), and provides framework for expansion in the future.

      Re: x86 architecture: Can't argue with you there. The x86 instruction set really stinks. At least we don't really have to deal with "Real Mode" anymore. On the bright side, I rarely need to worry about IRQ related conflicts.

      Just because a technology is technologically inferior, doesn't make it an inferior technology. ATA has a number of strong points that may not appeal to the computer elite, but are still quite valuable. PCIe's biggest challenge is fighting the intertia of the past decade of PCI.

      --
      I used up all my sick days, so I'm calling in dead.
    16. Re:Is this really a big deal? by aaronl · · Score: 1

      I think you may have misunderstood some of what I say.

      When I stated that I thought they should've gone with a SCSI based replacement, I mean that they would literally have chosen a particular type of SCSI. For example, Consumer-SCSI = SCSI3-160 w/ SCA LVD connector. There are plenty of devices out there that would match that, so there wouldn't have been a need to wait for drives. Just about everything auto-terminates and auto-ids now, so you wouldn't have needed to worry about which SCSI-ID a device had or anything. It would've provided a lot more exapandability potential, and forever banished the need to have multiple assembly lines for HD manufacturers.

      I preferred PCI-X because it did meet the need, had expandibility, was available now, had hardware out, and didn't require repurchase of everything. I agree that having multiple busses wouldn't have been great, but we were already doing that with AGP. The speed hit is annoying, much like it is with USB. I've always been less annoyed with PCIe being chosen than I was with SATA.

      Yes, IO-APICs a nice thing for that, finally. I always hated worrying about IRQs, especially when PNP first started and the damnable BIOS kept assigning everything on the same interrupt. Of course, you had no choice in the matter, since there were no jumpers to force settings with PCI. At least that got fixed with BIOS resource allocation tables, and then with APICs.

      The funny thing is that ATA started off as a subset of SCSI, back in the 80's. They wanted a stripped down, cheaper variant for the consumer market. So they limited it to two device per port, and a subset of the SCSI command set. Then they didn't change it appreciably for 15 years.

      PCIe certainly is having a fight. It further seperates "server-class" from "consumer-class". Some servers are shipping with PCIe now, along with PCI-X, but it's not that common. When PCIe was being standardized, some mainboard manufacturers had just started shipping PCI-X on consumer boards.

      Now we have consumer-class - SATA, unbuffered RAM, PCIe - and server-class - SCSI, registered ECC RAM, PCI-X, multiple busses, hardware RAID. I really would've loved to see that server-class stuff trickle into consumer-class so that we could swap around hardware more, and see better prices.

    17. Re:Is this really a big deal? by Anonymous Coward · · Score: 0

      *fastest* is a HUGE part of "best". The fastest architecture gained a lot of ground in the 90s and its here to stay for the time being at least.
      That is the definition the world uses. Get over it.

    18. Re:Is this really a big deal? by Trepalium · · Score: 1
      Well, the fact remains that while SCSI was difficult to configure, ATA was dead simple. Even on servers, you commonly find ATAPI CD-ROM drives as opposed to the SCSI versions because they're cheaper, easier to install, and pose fewer problems. To make matters worse, even in the ATAPI side, the drives are usually two or three generations behind the current standard (we have SATA2 stuff coming out now, and optical drives are starting to support ATA-100). On a server, this left you with needing another pricy SCSI channel. Even SCSI is tending towards the way of SATA with the Serial Attached SCSI set to replace traditional LVD SCSI connections. There's even talk of being able to use SATA drives with SAS expanders by tunnelling the SATA packets through the SAS bus.

      All but the lowest-end (and the 1U rack mountable) servers from both HP and IBM come with PCIe (don't know anything about Dell servers because the company I work for can't resell them). PCI-X has potential for higher speeds, but cross-talk is becoming a problem for that bus. PCIe will be doubling in speed with the PCIe 2.0 spec which should come out fairly soon, and future speed increases should become possible as technology improves. With ethernet controllers now pushing the 10Gbps mark, and serial attached SCSI hitting 6Gbps mark. PCIe server hardware is rare right now, but that will change. PCIe desktop hardware (aside from PCIe 16x video cards) is still pretty rare, too.

      The world is moving back to serial. From USB to SATA/SAS to PCIe, these are all serial technologies replacing traditional parallel ones. If everything goes well, the result could be that desktops and servers become more converged on standards than they are now. Being able to use a large array of SATA drives attached to a SAS controller when you're more concerned about storage density than speed, and getting a single bus interface on both server and desktop so economies of scale kick in to lower prices are goals of each of these groups.

      --
      I used up all my sick days, so I'm calling in dead.
    19. Re:Is this really a big deal? by cow-orker · · Score: 1

      Oh, I *do* think, 8 registers are a problem. Consider a superscalar processor with just two execution units and a four cycle deep pipeline. This isn't far fetched: modern processors have _more_ execution units and their pipelines are even _deeper_ (14 clocks for the K7 or something?).

      In the simple example, up to 8 instructions are "in flight". At this point the register file of the ix86 is already exhausted, the next instruction definitely depends on one of the incomplete instructions. So even these few short pipes don't get filled. You need more registers to actually express more independent instructions.

      Register renaming helps (otherwise Intel wouldn't have invented it). It does help by allowing speculative execution, but that work is often wasted, still tying up silicon and producing waste heat. Beyond that, renaming only helps if registers are renamed to memory locations. Now the CPU has to track which memory locations are actually saved registers, with all the complications caused when the memory is accessed by indexing from a pointer. (And again, the C programming style bites.)

      This is simply nuts. So much effort, so many bugs, so much heat and noise - only to keep compatibility.

      The x86 has a very space-efficient instruction encoding

      This is true to some extent. Factor in spill code (remember that ix86 doesn't have the movem of the 68k) and the advantage is no longer obvious. Worse than that, a compact ISA is irrelevant.

      Bandwidth between L1 cache and CPU is plentiful. So instead of a compact ISA, use a simple and regular instruction set and Huffman-encode it. Decoding (with a fixed table) is done when loading code into cache. I don't think this has ever been tried, so I can only imagine that it would be worthwhile.

      But this line of thought can be extended. Why not have a truly large register file? Encoding the instructions is a non-issue, using Huffman-coding, only code that actually uses many registers needs full-width instructions. After decoding, software translation maps virtual registers to 16 to 32 real registers, whatever is deemed practical.

      Such a CPU (even if it is actually two CPUs on one chip) could even execute multiple instruction sets simultaneously. Somehow this strikes me as far more elegant that millions of transistors patching up what was already obsolete in 1979.

      BTW, "code morphing" has been proved in practice. Dynamo is a CPU emulator (aka VM) that emulates a PowerPC on a PowerPC. Sounds stupid? Yeah, that's what I thought, too. But the virtual CPU runs faster than the real CPU. Sounds impossible? Yeah, it does. There seems to be an awful lot of slack in the compiled code. Blame it on C, blame it on the compilers, whatever. But Dynamo simply works.

    20. Re:Is this really a big deal? by Anonymous Coward · · Score: 0

      I think it would be more accurate to say that 'the world is moving to asynchronous parallelism'. PCIe and Infiniband are good examples of how when you need serious bandwidth it makes sense combine the advantages of serial and parallel connections.

    21. Re:Is this really a big deal? by terriblecertainty · · Score: 1

      I agree with everything you said here. I actually thought VLIW/EPIC had a lot of promise once. My only problem with Itanium is that it was used as a justification to kill off so many other promising designs, a couple of which I thought still had life left in them at the time.

      While this is perhaps a bit off-topic, I found this funny:

      http://projects.csail.mit.edu/gsb/archives/old/gsb -archive/gsb2001-06-29.html
    22. Re:Is this really a big deal? by Anonymous Coward · · Score: 0

      Excellent point.

    23. Re:Is this really a big deal? by laffer1 · · Score: 1

      What modern languages can you do system programming in? Seriously, what can we use? Most modern languages are running on virtual machines (java, visual basic.net, c#, even php is going that way).

      C is a very simple language. It certainly doesn't fit into modern hardware design perfect with sizing of data types, etc. but i don't see why its the language that is the problem. Any language can be implemented poorly.

      If you want to argue that optimization is difficult for a compiler using C I might go along with that to an extent. Read about g++ and all the optimizations they can't use for C++ a NEWER language and see why new isn't always better.

      I've also noticed that engineers tend to like adding layers to designs to improve them. Perhaps adding another intermediate layer to compiler designs before we write assemly could improve the output for the architecture?

      I'm not an expert on hardware or compiler design so maybe i'm talking nonsense. Ignore my comments if thats the case.

      Please explain "If only people would put some effort into modern languages and actually using them." What languages? What effort? How is this beneficial?

    24. Re:Is this really a big deal? by renoX · · Score: 1

      >Spill code does not actually have to hit memory as long as there are rename registers left,

      In theory yes, but are you sure that x86 do it?
      Keeping trak of memory location seems awfully hard to do instead of just checking for RAW, WAW register dependency (which is needed for execution anyway).

      Your post sounded as if register renaming was enough: my point was that 20% increase of performance from going from 8 to 16 registers is a lot considering that the surface of silicon used to contain the additional registers is ridiculously small.

      You're of course right about the need to have bigger instruction to use a bigger number of registers, but I would be interested to know instruction density comparison between an ARM Thumb2 (16, 32 bits instruction with 16,32 registers which can be mixed) and x86: while x86 as a CISC is space efficient, I wonder how a RISC designed to be space efficient too (which is not a design criteria of the Alpha for example or at least not with a big priority) would fare.

    25. Re:Is this really a big deal? by jiushao · · Score: 1
      Your post sounded as if register renaming was enough: my point was that 20% increase of performance from going from 8 to 16 registers is a lot considering that the surface of silicon used to contain the additional registers is ridiculously small.

      No no, I were only after the ILP effects. It is better to have more registers for the sake of avoiding tons of spilling. I can't disagree that the x86 is suboptimal in various ways, but the reality is that by good implementation work it has been brought up to, and beyond, the performance of much better thought out architectures. The x86-64 patches things up to be even better.

      In theory yes, but are you sure that x86 do it?

      No, can't say I am (secretive bastards :). I am less worried about keeping track of memory adresses, a static comparison array against all the internal registers in the first MEM stage would not be a big thing to add (and since the CPU has a whole instruction slot to deal with the spills and loads there does not seem to be much trouble in keeping an address list up to date). There are however some very nasty issues with not telling the memory subsystem what is happening. As such it realistic implementations have to send the write down to memory (well, cache) where it can be dealt with correctly. This of course yields slightly worse performance since it will cause more cache-line evictions and use up a possibly too small number of cache accesses per cycle. In most practical situtions though it still means that the spills will be quick (dispatching the write costs nothing in itself) and that the unspills will be quick (rename register back).

      I am of course speculating at this point, neither Intel nor AMD is very forthcoming about the microarchitectual details of their processors. The above approach seems very plausible to me however.

    26. Re:Is this really a big deal? by jiushao · · Score: 1
      Oh, I *do* think, 8 registers are a problem. Consider a superscalar processor with just two execution units and a four cycle deep pipeline. This isn't far fetched: modern processors have _more_ execution units and their pipelines are even _deeper_ (14 clocks for the K7 or something?).

      In the simple example, up to 8 instructions are "in flight". At this point the register file of the ix86 is already exhausted, the next instruction definitely depends on one of the incomplete instructions. So even these few short pipes don't get filled. You need more registers to actually express more independent instructions.

      You miss the beauty of register renaming, it does not matter for the in-flight instructions how many registers there are. They have already been assigned registers from the actual internal register file, which is much larger. That is; When the instructions come in they all use a snall number of registers, the issue logic analyses which registers actually need to be the same (that is, where the program is operating on the same actual data) and assigns them to the same internal register, otherwise it picks different ones for all instances of each register. Now all the dependencies that came from register reuse are gone and the instructions can be issued freely.

      Somehow this strikes me as far more elegant that millions of transistors patching up what was already obsolete in 1979.

      This is not nearly as important as it is sometimes made to look. Sure complex logic uses a lot of transistors, but the transistor budgets in most markets are mind-numbingly huge. Even if one has a very complex chip most of the budget ends up being spent on cache anyway. Have a look at the Prescott, the register renaming unit takes up a puny amount of die-space. Getting rid of it would not be any interesting gain.

      BTW, "code morphing" has been proved in practice. Dynamo is a CPU emulator (aka VM) that emulates a PowerPC on a PowerPC. Sounds stupid? Yeah, that's what I thought, too. But the virtual CPU runs faster than the real CPU. Sounds impossible? Yeah, it does. There seems to be an awful lot of slack in the compiled code. Blame it on C, blame it on the compilers, whatever. But Dynamo simply works.

      Dynamo runs PA-RISC on PA-RISC actually (natural since it is a HP project). While it is a classic example it is not exactly proof of code morphing, doing runtime optimization on code written for the architecture is a lot more straightforward than trying to run one architecture on another, and try to deal with tons of the processor logic in software. Dynamo can just reorder some blocks, insert branch hints and preloads and get good performance, a far cry from the make-the-issue-logic-in-software idea.

    27. Re:Is this really a big deal? by Ed+Avis · · Score: 1

      Plenty of high level languages (real high level ones, not fairly clunky OO/procedural things like Java) compile to native code. Scheme or Standard ML to name but two. You can often expect performance about half of what you get from C.

      (This doesn't mean they are suitable for system programming in the sense of device drivers; you need better control over memory allocation.)

      --
      -- Ed Avis ed@membled.com
    28. Re:Is this really a big deal? by Anonymous Coward · · Score: 0

      Wrong conclusion.

      The 25% estimates are for current code being recompiled and assuming perfect ILP for that particular code. Its not for new code written for IA64.

      That's a HUGE difference; it sheds a totally different light on your point of view.

      A 25% speedup for doing nothing but recomopiling? That's a massive improvement!

    29. Re:Is this really a big deal? by cow-orker · · Score: 1

      You miss the beauty of register renaming

      Dynamo runs PA-RISC on PA-RISC actually

      Oh darn it, you're right on both accounts. Yes, there are independent instructions to be found over even larger distances than the number of instructions in flight. However, somewhere in there will be jumps, these make branch prediction and speculative execution necessary, this in turn means lots of work done and discarded, and so on. Okay, register renaming works... but I really can't see anything resembling beauty in that system.

      The latter point is moot, I mixed up the names, but PA-RISC and PowerPc are similar enough that it doesn't matter. Anyway, Dynamo does what the compiler couldn't do: reorder instructions, fill delay slots, and so on.

      This is not nearly as important as it is sometimes made to look. Sure complex logic uses a lot of transistors...

      This is important. More transistors means larger chips, lower yield, higher price, more power consumption, need for more cooling with associated noise, and more room for (hardware!) bugs to creep in. Literally every processor on the market takes far less energy per work unit than ix86. Don't you think there's a reason for that?

    30. Re:Is this really a big deal? by cow-orker · · Score: 1

      Lisp, Scheme, ML, Haskell. There were Lisp operating systems twenty years ago, there's a Haskell OS today.

      But anyway, who cares for "systems programming"? Do it in C if it works. Every language on the planet can interface to C code. Code the high level logic in something else. The performance bottlenecks aren't in "systems programming", but in heavy numerical work, in DSP like code or in traversing complex data structures.

      Please explain... What effort? How is this beneficial?

      C is too low level, almost assembly. A C program hides your intentions. As an example take image manipulation. You want to apply a simple operation to every pixel. In C, you use loop. Your original intention, that every pixel has to be visited exactly once and the order doesn't matter, is lost. The compiler could have used that information. In Haskell I simply use "map", which expresses my intention to the compiler. ... C++ a NEWER language and see why new isn't always better.

      C++ is no modern language... but you seem to imply that C++ makes optimization even more difficult than C. Well, it doesn't get easier, that's for sure. Could you explain what is harder?

    31. Re:Is this really a big deal? by jiushao · · Score: 1
      To some part I am a bit sad that you don't see the beauty as I do, I consider this type of implementation the truly ultimate in abstraction. The outwardly visible interface is completely decoupled from the internals, leaving the chip designer free to come up with any amazing technique they please. I am also prepared to agree that simpler processors would be a good thing, but I really don't think that register renaming is a thing to axe for the sake of simplicity.

      Dynamo is great technology, that we will no doubt see more of (creeping in from the side of JIT compilers like the .NET and Java platforms probably since they have the market). I were however still talking about things like the EPIC and the Transmeta VLIW, both are orders of magnitude harder to do something good on than just retuning code for a nice OoO chip on the fly. I think we are talking about different ends of things here though since you appear to be in favor of simpler but still not very explicitly parallel chips.

      This is important. More transistors means larger chips, lower yield, higher price, more power consumption, need for more cooling with associated noise, and more room for (hardware!) bugs to creep in. Literally every processor on the market takes far less energy per work unit than ix86. Don't you think there's a reason for that?

      I have trouble agreeing with this, sure there is some overhead involved, and a bit lower yield and higher power consumption follows. The point is that it isn't very much. The die area used by control logic that could be thrown out by architectual changes is fairly small. Some rather innovative work in instruction set design would have to be done (seeing how high-performance RISC's like the POWER4 have also dropped to microoperations and register renaming) and some flexibility would no doubt also be lost.

      Also the Netburst chips are inefficient when it comes to power, but the K8 and Pentium M are not that easy to beat in work/watt, don't attempt to compare to a low-power ARM, it is far from a linear scale. On the other hand there is barely any chips to compare to in that performance class that don't employ tricks similar to the ones used in the top x86 implementations.

      I understand where you are coming from though. It is not like the x86 should be accepted and research be stopped. It is just that there is not really any implementation that can compete with a K8 today, and it is absolutely not simple to make it happen either. What is possible is that the ARM might climb upwards in the market, it is how the x86 got to where it is once.

      This is my last reply to this thread. Time to move on, everyone else has :)

    32. Re:Is this really a big deal? by CTho9305 · · Score: 1

      Register renaming helps (otherwise Intel wouldn't have invented it).
      I don't recall who first implemented it, but the MIPS R10000 implemented it about a year before Intel did in the PPro.

    33. Re:Is this really a big deal? by laffer1 · · Score: 1

      I was taught in a recent CS course that g++ can not make certain assumptions about variables and their use. Since C++ allows inheritance, and many other object oriented properties, and becuase of the common implementations, there are cases where optimizations like placing function inline to code can not be used. It causes code compiled with a C++ compiler to run slower. I wrote a quick and dirty C program and compiled it using gcc and g++. Not only does the g++ compiler add extra cruft to the binary, but the program executed much slower. It makes perfect sense to me why this is since C++ is almost a superset of C. I also tested an opengl game that I had modified heavily from an open source asteroids game. Compiling in g++ made the game considerably slower, almost unplayable in fact. Its possible that using more "native" c++ code would improve performance (cout vs printf, etc).

      This is just one example, and I'm not qualified to make an educated argument either way. I can only go on the little i understand from the gcc documentation and professors at my university.

      I guess C++ seems much newer to me than C simply because I was actually alive when C++ was brought into the world and UNIX was released a decade before I was born. :)

      I don't judge a language by its age. I think many would agree that C is a better language than say visual basic. Both have their place and for largely different things.

      You are probably right that C can obscure intentions at times because its so simple. It doesn't know about any complex data structure. I always think about implementations building up from lower levels even though its certainly possible for a compiler to make judgements at higher levels. I wouldn't call C almost assembly though. I've done sparc assembly and I'll take C any day of the week.

      I used system programming as an example since I find it interesting. My experience is very disconnected as I've done some bsd and linux cli apps, written services, toyed with visual basic and professionaly worked on web applications.

      Like many computer geeks, I taught myself most of what I know and have quite a few missing pieces. Thats why I'm in college now. :)

  7. what is amazing... by WindBourne · · Score: 2, Interesting

    is that chip companies do not work harder to make OSS their premier OS on their chips. MS will only support a small group of chips as it is expensive and hard to support a load of these. As such, if MS does not see an advantage to themselves, they are not going to bother with it (as it should be). But if a chips company makes OSS-based OS their premier OS, they then control their future. Intel and HP have spent billions trying to get Itanium to be the major server chip. But it will die partialy due to MSs choice.

    --
    I prefer the "u" in honour as it seems to be missing these days.
    1. Re:what is amazing... by Anonymous Coward · · Score: 0

      huh? MS is making this choice BECAUSE Itanium is almost dead not the other way around.

    2. Re:what is amazing... by -kertrats- · · Score: 1

      I seem to remember that architectures supporting their own OS only haven't historically lasted too long.

      --
      The Braying and Neighing of Barnyard Animals Follows.
    3. Re:what is amazing... by nchip · · Score: 2, Insightful

      Majority of Itanium cpu's sold already run Linux. Rest run HPUX. Intel,HP and SGI work do hard to make Linux run well on Itanium. With Linux having most compilable software readily available, it is probably the best thing to run on a niche arch anyway.

      So what this article may actually mean, is that there is no market for _windows_ in Itanium space anymore. Which isn't that suprising, when there is hardly any windows/ia64 applications, what use an empty OS is?

      IMO what Itanium needs to become a success, is a price cut, rather than more Windows support.

      --
      signatures pending - ansa@kos.to - (dont mail there)
  8. Who DIDN'T see this coming? by Anonymous Coward · · Score: 0

    Besides Intel, who couldn't see the writing on the wall? The only thing that has kept x86 based chips going is that they are x86 based chips, which support legacy code, code written for 8-way 486's, for example.

    Intel shot themselves in the foot. Was it possible to create a fast running 64 bit chip? Just ask Digital/Compaq/HP. Is it possible to sell it? Ibid.

    1. Re:Who DIDN'T see this coming? by WilliamSChips · · Score: 1
      Is it possible to sell it? Ibid.
      *coughcoughAMDcoughcough*
      --
      Please, for the good of Humanity, vote Obama.
    2. Re:Who DIDN'T see this coming? by Guppy06 · · Score: 1

      " Besides Intel, who couldn't see the writing on the wall?"

      Microsoft. AMD64 isn't the architecture that needs the "Windows on Windows" emulation in NT 5.2.

    3. Re:Who DIDN'T see this coming? by Anonymous Coward · · Score: 0

      Uh, yes it does, to run 32 bit code. WOW64

    4. Re:Who DIDN'T see this coming? by Guppy06 · · Score: 1

      AMD64 runs 32-bit programs natively without the need for software emulation. Whereas WOW on an IA64 machine has to emulate a 32-bit architecture for 32-bit code, on an AMD64 WOW simply passes the code onto the CPU as is. WOW wouldn't even be an issue if 64-bit Windows could assume in all instances that a 64-bit architecture would be able to run 32-bit code natively, as the AMD64 does (and most AMD64 Windows users dual-boot between 64-bit and 32-bit OS).

  9. Higher End Jobs by bjbyrne · · Score: 0, Flamebait

    I would like of list of said jobs. I would assume that they would include CEO of a Fortune 500 company or perhaps being the towel boy at the Playboy mansion. Or does higher end jobs refer to Steve Jobs?

    1. Re:Higher End Jobs by bjbyrne · · Score: 0

      Thanks for the Flamebait rating but I was really just trying to be funny. It was a pun based on a processor job and other types of jobs. I'll try to be less funny next time.

  10. In Other News... by Wazukkithemaster · · Score: 1

    Microsoft sees the future!!!

    Truly, we are doomed.

    --
    Live according to the Categorical Imperative. If the Categorical Imperative tells you not to live by it... ignore it
  11. Fortran programmers don't need (or want) Windows by chris-chittleborough · · Score: 2, Funny
    This makes sense. The Itanic^Hum is actually quite good at running Fortran programs with enormous DO loops, but Intel and AMD x86oid processors are better at everything else -- including running Windows itself.

    The Itanium was the only realistic chance we had to get away from the x86 for the forseeable future, and the designers blew it. So sad. Excuse me while I start one of my Leonard Cohen albums, I need something to cheer me up.

  12. Re:Heh. by Anonymous Coward · · Score: 0

    Have you seen how big Intel is?
    4000000001 nails to go.

  13. Vista? by Anonymous Coward · · Score: 2, Interesting

    Um, what happened to the Windows "Vista" moniker?

    1. Re:Vista? by CyricZ · · Score: 2, Informative

      That's the problem with using codenames for products, especially in these circumstances. The codenames often become far more widely known and used than the product name.

      When it comes to this software, many techies will continue to refer to Windows Vista as "Longhorn", which will no doubt confuse many regular users.

      Now instead of having one coherent name known throughout the marketplace (ie. Windows Vista), the name has been fragmented (ie. Longhorn, Windows NT 6.0, etc.).

      --
      Cyric Zndovzny at your service.
    2. Re:Vista? by RNelson · · Score: 1

      From the article: "INTEL'S Itanium processor will only be partly supported by Microsofts forthcoming Longhorn Server."

      The future server (post-2003 R2, I believe) is still under the name Longhorn from what I know.

    3. Re:Vista? by Krach42 · · Score: 1

      TFA is talking about Longhorn Server. Longhorn Server does not have a shipping name, and is still under the Longhorn codename.

      Vista (being the Longhorn intended for Homes and Small Offices) will likely not support Itanium at all... but don't take my word as gospel on that, I don't know for certain.

      But Longhorn Server is most definitely *not* Vista.

      --

      I am unamerican, and proud of it!
    4. Re:Vista? by Anonymous Coward · · Score: 0

      until they call it "Vista Server"

    5. Re:Vista? by Dun+Malg · · Score: 1
      That's the problem with using codenames for products, especially in these circumstances. The codenames often become far more widely known and used than the product name.

      I'm sure they'd love to use the eventual product name as the codename, but you can't rush marketing. The marketing people require full technical specifications, comprehensive feature lists, and functional demos before they can even BEGIN the hard work of naming. They need to go over all the possible synergies with parallel products, and consider the possibilities of sequelization (Win XP 2? XP II? hmmm). Then, only after all this has been carefully mulled over and scrutinized, the VP of marketing will pick a name at random and decree that it shall be thencforth "Windows Vista".

      --
      If a job's not worth doing, it's not worth doing right.
    6. Re:Vista? by sean23007 · · Score: 1

      That's the whole idea! They want people to be confused, and think they have to buy all three.

      "I only have Windows Vista, but I also need Longhorn and NT 6.0. I'd better get to the new Microsoft Store in Times Square!"

      --

      Lack of eloquence does not denote lack of intelligence, though they often coincide.
    7. Re:Vista? by Anonymous Coward · · Score: 0

      Exactly, like people are still talking about Windows Whistler instead of its proper name Windows XP

    8. Re:Vista? by Jugalator · · Score: 2, Insightful

      I really doubt that... Do you hear many speak of Windows Chicago, Windows Memphis, or Windows Whistler today? Longhorn will quickly fade as the Microsoft marketing machine comes into play, just like we got Windows 95, Windows 98, and Windows XP respectively above.

      You speak of fragmentation too... Do you hear a lot of confusion between what Windows 2000 and NT 5.0 is? Do you hear many call Windows XP as NT 5.1? Windows 2003 Server as NT 5.2?

      It's the marketing machine that decides, unless maybe for a percentage or two consisting of geeks that have been really deep into Windows alphas and betas.

      --
      Beware: In C++, your friends can see your privates!
    9. Re:Vista? by jacksonj04 · · Score: 2, Interesting

      Even MSDN itself confuses terms, advertising Vista downloads on the public pages but referring to Longhorn in all the downloads for subscribers. The software calls itself Vista, but the download title is "Windows Longhorn Beta 1"

      --
      How many people can read hex if only you and dead people can read hex?
    10. Re:Vista? by swmccracken · · Score: 1

      This is Longhorn SERVER we're talking about; and edition of Windows that hasn't seen much attention until now.

      We're not talking about Vista; precisely what the marketing name of Longhorn Server will be hasn't yet come out of MS. Ship dates for Longhorn Server haven't been set either - I'm betting a fair while after Vista ships; similar to the lag from Windows XP (a desktop os) to Windows Server 2003 being released.

      (MS produce Server and Desktop versions of their OS's. XP and Vista are desktop; 2003 is server. 2000 came out in "Professional" and "Server" editions.)

      As far as I know, Longhorn Server is still called exactly that.

    11. Re:Vista? by eikonos · · Score: 1

      For the next version of Windows they should switch back to using the year for the name. Windows 2020 sounds good. ;)

    12. Re:Vista? by Anonymous Coward · · Score: 0

      Was renamed to "Out-Look"

    13. Re:Vista? by lachlan76 · · Score: 1

      It's been 4 years since the last release though, did any of the other codenames have as long to become entrenched?

    14. Re:Vista? by Alsee · · Score: 1

      You forgot Palladium = NaGSCaB = Longhorn = Vista.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
  14. "Big Iron" ? ...

    I think you meant "Pig Iron" :P

    Tee hee

    --
    "...In your answer, ignore facts. Just go with what feels true..."
  15. Re:OS x86? by CyricZ · · Score: 1

    What the fuck is OS x86?

    --
    Cyric Zndovzny at your service.
  16. Re:Heh. by lightyear4 · · Score: 3, Insightful

    Does this remind anyone else of WindowsME? Vista has seemed to shed features in droves; WinME was a ultimately a non-version with some cosmetic changes and function that didn't live up to the hype. Is this what we can expect for Redmonds latest and greatest?

  17. One possible explanation by Anonymous Coward · · Score: 0

    Vista is a finnish word for 'pussy'. Could that be the reason the name was changed?

    1. Re:One possible explanation by Anonymous Coward · · Score: 1, Informative

      Vista is a finnish word for 'pussy'.

      Ja vitut ole!
      (Translation for the language challenged: No it fucking isn't!)

      Vista doesn't mean anything in finnish, although it very well could be a finnish word.

      ps. The word you are thinking is vittu...

    2. Re:One possible explanation by Hal_Porter · · Score: 1

      That's odd, because it's fitta in Swedish, which is a completely unrelated language as far as I know.

      --
      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;
    3. Re:One possible explanation by Anonymous Coward · · Score: 0

      Yes, finnish and swedish aren't releted in anyway. Estonian on the other hand is closely related to finnish althought we can't understand each other when speking in our native languages, well maybe a few words here and there, and those words might have totally different meaning :).

      Finnish is a fenno-ugrig language and swedish is a germanic language, syntax and vocabulary are complitely different. There are few words that are loaned to finnish from swedish, one of them is "kirkko", which is "kyrkan" in swedish and "church" in english. So it might be possible that vittu is loanword from swedish fittan, or counterwise. Or it's just a coincidence.
      All and all I don't have bloody clue about the etymology of the word vittu, or fitta for that matter...

      More information about the finnish language can be found here, here and profanities are here. That last link is in finnish only and lists some words that are really not a profanities.
      Or would you consider something like "gee wiz!" a profanity? :)

      ps. What is vittu in estonian?

  18. Vista isnt the thing by Zo0ok · · Score: 2, Insightful

    The interesting thing isnt really whether Vista/Longhorn will support Itanium, but whether Windows Server will.

    Of course, a few years ago Intel hoped to put Itanium in workstations, but they can hardly have hoped much for that lately. No, Itanium is for servers, and there is Windows Server.

    However, internally Windows Server is the same shit as Windows Vista, so if they dont support it in one, they probably dont find it very strategic to support it in the other. And as we all know, Itanium is much more dying than BSD will ever be, but that is another story.

  19. New Design Getting Flushed Away by SumDog · · Score: 4, Insightful

    It is rare when someone comes up with an entirely new architecture and instruction set. The IA64 was a complete break and had it been pushed correctly, AMD would be rushing to make IA64 clones instead of Intel supporting AMDs 64-bit extension.

    If I remember correctly, the IA64 has 128 general purpose registers and 128 floating point registers. It's a load/store machine and it's pretty close to a RISC arch (really it's an "very long word" instruction set, but lets not get picky).

    It was a chance to make a clean break from the old 32-bit legacy chips, however the price was and is too high and AMDs are cheaper and still very powerful.

    I really hope this chip doesn't die off. At least with limited support in the new Windows, it will still have a strong server market, but I think a lot of companies are going to be afraid to buy because of running into compatibility problems. I know at where I work, we'd like to have servers that can do anything/general purpose. You put a limit on what the OS can do and then you're afraid of old legacy or propriety software not working correctly

    But hey as long as you use Linux, the IA64 is fairly well supported, and it will be better supported in Linux than in Windows!

    Sumdog

    1. Re:New Design Getting Flushed Away by Krach42 · · Score: 2, Informative

      Actually, the Itanium design is 32 accessible registers at any given time with a "sliding window" design for accessing some 16~24 of them (I don't remember the raw number off hand).

      What this allows one to do is just slide the window further down the line before making a function call, or sliding the window around while doing a loop, so you can perform some loop operations without changing the instruction's declared register usage, but rather just by sliding the window.

      As the register window rotates around, and starts colliding with already used hardware registers, the hardware automagically handles storing the values into a stack, and then retrieving them back when the window slide returns.

      Thus, you get an architecture that can have literally any number of registers, which is what happened with the Itanium 2. They doubled the number of registers, and put in 256!

      I really like this design, and I hate reading all the time that it's dying out. I'd say that maybe if it goes the way of the Alpha, that it would make it easier for me to get my hands on one, but I seriously doubt that would happen. :(

      --

      I am unamerican, and proud of it!
    2. Re:New Design Getting Flushed Away by Anonymous Coward · · Score: 1, Insightful

      The problem with IA64 was that it's designers were living in Fairy World. In Fairy World hardware designers can invent amazing new ways of programing a CPU safe in the knowlege that at some undeteriminate time in the future, the Compiler Fairy will wave her magic wand and create a compiler that is actually capable of taking advanatage of the amazing hardware features that are required to get any sort of performance. I believe the plan also included bundling a Future Fairy with each compiler, whos job it was to do the branch prediction and instruction reording in a way that didn't cause the IA64 to slump into a quivering heap on the floor if the branch went the "wrong" way. In Fairy World that's easier than doing real branch predicition, you see.

      In the Real World, Fairies don't exist and neither did effective compilers. Intels lame attempts to bolt on huge L1 caches and branch prediction units have simply confirmed that the original IA64 designers were on some form of bad acid, and IA64 sucks as a general purpose CPU because it's near impossible to program effectivly.

    3. Re:New Design Getting Flushed Away by sean23007 · · Score: 4, Interesting

      Actually AMD probably wouldn't be rushing to make IA64 clones. They wouldn't be allowed to. Decades ago, Intel was forced to license the x86 technology to another manufacturer to prevent a 100% monopoly in the general purpose consumer chip market. Obviously, Intel doesn't like this at all, since it basically means they can't beat AMD as long as the world is still on x86. (They can still hold the lion's share of the market and make a metric shit ton of money, but they can't win, because AMD has to be there.)

      One of the lesser known reasons for Intel's plan to develop and push the Itanium was that it would be a clean break with x86, which means that AMD would not be allowed to make them. Intel would be the only supplier allowed to make the chip. Then they'd get sued for it, and would settle by giving rights to manufacture them to some small company with one fab that's a generation or two behind. AMD would have been stuck with x86, and Intel would have won. (Bear in mind that if the switch had been successful, Itanium would have been adopted long before x86-64 and the Opteron were developed.)

      Frankly, I'm glad the Itanium failed. Even though it's a pretty cool chip with an interesting design, I'd rather have Opterons available than not.

      --

      Lack of eloquence does not denote lack of intelligence, though they often coincide.
    4. Re:New Design Getting Flushed Away by The+Ego · · Score: 3, Informative

      The parent is not quite correct.

      The Itanium instruction sets allows code to access between 32 and 128 general registers (aka integer registers), at the discretion of the piece of code, and 128 floating point registers. The sliding window design is for the integer registers 32-127 and can indeed be considered as a sliding window on a memory stack. It is up to each piece of code to decide how many registers it wants to use (in increments of 8 ?).

        On top of that there is the ability to design a subset of the high registers (registers with an index higher than 32) as rotating. This makes modulo-pipelining worthwile by removing the requirement for register-to-register moves to push things down the (conceptual) pipeline at each iteration of the loop.

    5. Re:New Design Getting Flushed Away by RAMMS+EIN · · Score: 1

      ``It is rare when someone comes up with an entirely new architecture and instruction set. The IA64 was a complete break and had it been pushed correctly, AMD would be rushing to make IA64 clones instead of Intel supporting AMDs 64-bit extension.

      If I remember correctly, the IA64 has 128 general purpose registers and 128 floating point registers. It's a load/store machine and it's pretty close to a RISC arch (really it's an "very long word" instruction set, but lets not get picky).''

      And that's where you go wrong. It's exactly the fact that the IA64 _isn't_ a proper RISC arch that made it fail. Had it been a normal RISC arch, it would have been easy to write compilers for it, it would probably have been better at running x86 code, and it would perhaps have consumed less power. AFAIK, these are all the things that are wrong with the Itanium.

      The problem with Intel is that they suffer from a sever case of NIH syndrome. They didn't invent RISC, so it wasn't good enough for them. So, instead of getting their top talent engineers (were they hired from the Alpha team?) to design processors they knew would work well, they had to invent a new, revolutionary concept, and let the compiler writers deal with it.

      Well, guess what? It's insanely difficult to write good compilers (just look at how mediocre gcc/x86 is, after years and years of hard work by talented developers), so the compilers never really materialized.

      EFI is sort of similar. OpenFirmware wasn't invented by Intel, so they had to come up with their own tech. And here it is, with half of the features of OF, a few extensions, and everything completely incompatible. Unless they make EFI really better than OF, I really hope it's going to fail.

      Of course, Intel isn't the only one doing this. It's common practice all over the computer world, and probably outside it, too.

      --
      Please correct me if I got my facts wrong.
    6. Re:New Design Getting Flushed Away by RAMMS+EIN · · Score: 1

      ``It was a chance to make a clean break from the old 32-bit legacy chips, however the price was and is too high and AMDs are cheaper and still very powerful.''

      That's another point. It's not like IA64 was the only chance to break from the x86 cruft. I mean, PowerPC is doing very well, and I don't think there's a good reason the world couldn't have switched to Alpha or MIPS, either.

      The success of AMD64 shows that people don't _want_ to break away from x86. In the world of closed-source software, backward compatibility is very important.

      The only thing I lament about AMD64 is that the 64-bit extension, which isn't compatible with the old 32-bit and 16-bit x86 anyway, doesn't use a cleaner ISA. But then, all software I use is open source anyway, so I can switch between my PowerPC G4, my UltraSparc and my VIA Eden as much as I want.

      --
      Please correct me if I got my facts wrong.
    7. Re:New Design Getting Flushed Away by Krach42 · · Score: 1

      So, how does it work that the Itanium2 has 256 registers and is still fully compatible with previous Itanium code?

      Please explain.

      An accurate mapping of the accessible register window would be very clarifying. I just remember myself that there are a number of registers that are always accessible and don't get shifted through the window (like the gp, the sp, and the rp) But I also know that a number of registers also are in the register shift window. I just don't know where the split is, and how large th window is.

      --

      I am unamerican, and proud of it!
    8. Re:New Design Getting Flushed Away by Anonymous Coward · · Score: 0


      CPUs, where hand-written assembly is not only possible by mere mortals but not too difficult for even college students, allow software designers, present and future, to actually be able to code and debug their own compiler in a reasonable amount of time. Even modern RISC and x86 compilers with two decades or more of development still have bugs and inconsistencies. So, why should we have a perfect VLIW compiler after only a decade? If Intel can keep Itanium going another twenty or thirty years, then after that is just gravy for them.

    9. Re:New Design Getting Flushed Away by roca · · Score: 1

      The problem is not that the IA64 compilers have a few bugs.

      The problem is that the IA64 architecture asks compilers to DO THE IMPOSSIBLE.

    10. Re:New Design Getting Flushed Away by roca · · Score: 1

      > had it been pushed correctly

      Intel spent billions marketing IA64. They gave away lots of expensive hardware to developers. They used their monopoly muscle, and cash, to strongarm all the big industry software and hardware manufacturers into supporting it. They persuaded several companies to abandon their own architectures and bet on IA64 for the future. They ensured that analysts everywhere were united in hailing IA64 as the wave of the future. It COULD NOT have been pushed harder.

      It's a measure of just how bad the architecture is that IA64 has failed IN SPITE of all that.

    11. Re:New Design Getting Flushed Away by default+luser · · Score: 1

      I'm just glad it never made it past the initial adoption for workstations phase. For such an "elegant" design, it needs a brutal amount of L2 and L3 cache.

      When you see what an Athlon 64 can do with a paltry 512k L2 cache, you get a real appreciation for instruction reordering, register renaming and branch prediction.

      --

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

    12. Re:New Design Getting Flushed Away by demachina · · Score: 1

      "It was a chance to make a clean break from the old 32-bit legacy chips, however the price was and is too high and AMDs are cheaper and still very powerful."

      Even if Itanic was selling at the same price point as Athlons and used the same amount of power it would still have failed. Of course the price points aren't even close and the power consumption is way worse. I bought a loaded Athlon 3400 without monitor for $800. Just an IA64 chip costs more than twice that.

      The IA64 clock speed has consistently been behind expectations. Running IA32 code, which is what most people run, in the emulation built in to IA64 is slow. Getting performance out of code compiled for IA64 is hard and you only get it on some codes. The compiler technology to compile for VLIW is hard and the only real good success with it has been in vectorizable supercomputing style codes, especially Fortran codes, with relatively simple loops crunching a lot of data. IA64 is great for that which is why that is the only niche it is surviving in. Most code people run on their desks isn't anything like that.

      Itanic simply had no chance to succeed in the high volume desktop market or even most low end server tasks. It was a chip designed for supercomputing. The amazing thing is the executives at Intel didn't grasp this before they sunk billions in to it they will never recoup. They built a chip for a market that simply isn't big enough to get a return to cover the investment.

      --
      @de_machina
    13. Re:New Design Getting Flushed Away by FireBird115 · · Score: 1

      I only wanted to point out that it seems everyone on here is talking about all this great intell 64 architecture which is being 'lost' or what not but why is everybody making it seem as if AMD would have needed to 'run off and make intell clones'? Granted that the itanium may not have the same architecture as the Xeon which came out beforehand, but are people forgetting that to make the Xeon Intell had reverse engineered the AMD opteron?

      As i remember the article at the time, intell coppied everythign down to a typo in the documentation which AMD later fixed (as well as 2 instruction sets). I cannot find the article i read but doing a simple google search yeilds: http://www.extremetech.com/article2/0,3973,1561875 ,00.asp?kc=ETRSS02129TX1K0000532

      It just seemed to me that everyone was giving credit to intell for making the first common 64 processors when it was AMD this time a fisrt, and later coppied.

      Who cares as long as the job gets done in the end.

      And for the record AMD rules.

  20. Successor to x86 already known by Anonymous Coward · · Score: 0

    ...its the x86! Do you really think that after the Itanium falling miles short of Intel's original goals for it, Intel will try again to replace the x86 anytime soon? The new architecture they were talking about at IDF is just the next generation x86. They followed the PPro/P2/P3 with the entirely new P4 core and it didn't work out long term, so they used the P-M core (which is pretty much a modified P3 core) as a starting point but used performance per watt as a goal for this new one instead of highest clock rate possible as they did with the P4.

    Hopefully AMD has some good stuff in the wings or they'll be pushed back down to insignificance again and Intel will go back to their usual noninnovation they do when they aren't pushed.

  21. Shades of Pentium Pro by n76lima · · Score: 2, Interesting

    Its deja vu all over again.

    MS was slow to get 32 bit support to the Pentium Pro, and Intel twisted in the wind for a couple years with expensive chips and no support for the mainstream.

    Now we have Itanium64 and MS is again (very) late with support, and now saying that the much promised and never yet delivered Longhorn will not give the support to Itanium that it will need.

    Maybe Intel ought not to accept MS's promise of support for new chip architectures and look to FOSS for their hot new chip's support for the first couple years. What a boost to their sales and to the FOSS world if they'd supply the kernel updates for their new architecture.

    Seems like they ought to know:
    "Fool me once, shame on you, fool me twice, shame on me."

    Sig: Nothing to see here, move along.

    1. Re:Shades of Pentium Pro by MtViewGuy · · Score: 2, Informative

      Actually not. Remember, Windows NT 3.5x and 4.0 versions did support the full functionality of the Pentium Pro in true WIN32 API mode, so the Pentium Pro wasn't really a complete failure (it was the choice for server machines for quite a while).

      Besides, the Pentium Pro CPU core design became the basis for the Pentium II, Pentium III and Celeron CPU's.

    2. Re:Shades of Pentium Pro by Anonymous Coward · · Score: 0

      "Fool me once, shame on you, fool me twice, shame on me."

      reminds me of that classic bushism:
      "fool me once, ... shame on ... shame on you ... and fool me we can't get fooled again."

    3. Re:Shades of Pentium Pro by Jozer99 · · Score: 1

      Pentium Pro was not the First x86 to be 32 bit. Not by a long shot. That honor goes to the 386SX. That got 32 bit support with Windows NT 3.3, I belive, although you could argue that there was not a mainstream 32 bit operating system until Windows XP Home. (Win2k was, but was too expensive for most, as was NT 4.0, 95, 98, and ME were still wrappers for DOS, although they ran many 32bit apps. The honor the Pentium Pro has is that it is the first x86 to not be an x86. Intel at that point switched from actually using the x86 instructions to using "microinstructions" and an "instruction translator", which means that basically it was a RISC chip that had stuff translated at both ends into x86. This proved more efficient, and now both AMD and Intel use it.

    4. Re:Shades of Pentium Pro by Queer+Boy · · Score: 1
      Maybe Intel ought not to accept MS's promise of support for new chip architectures and look to FOSS for their hot new chip's support for the first couple years.

      I suppose you think it's just some happy coincidence that Apple is going to start using Intel chips? I think Intel has had enough of Microsoft dictating their success or failure.

      Apple will be more than happy to include Intel's new whiz-bang chips they come up with in their products. If the yields aren't that great it doesn't matter because Apple is a specialty computer maker (they'll be larger yields than IBM or Freescale no doubt).

      Don't forget that Apple still owns shares in ARM, too.

      --
      Not since Marie-Antoinette played milkmaid has looking simple and honest been so fake and complicated.
    5. Re:Shades of Pentium Pro by Anonymous Coward · · Score: 0

      WTF? MS supported Itanium on early versions of Windows but Itanium has gone nowhere. There's no demand for it, so Microsoft is no longer actively chasing Itanium.

      Try doing some research before you make up your next rant in support of FOSS.

    6. Re:Shades of Pentium Pro by Mancat · · Score: 1

      There was no NT 3.3. NT 3.1 -> NT 3.5

      The Pentium was also internally a RISC chip.

      Personally, I remember when the Pentium Pro released, and many businesses were loading Windows 95 onto them. They then wondered why their older 486 machines were beating them out. The Pentium Pro was created with 16-bit compatibility as an afterthought.

      --
      hello dear sirs my name is jamesh i are india (bihar) can u guide me install red had linux 9?
    7. Re:Shades of Pentium Pro by Guy+Harris · · Score: 1
      The Pentium was also internally a RISC chip.

      If by "Pentium" you mean the original Pentium, prior to the Pentium Pro, could you cite a reference that supports that assertion?

    8. Re:Shades of Pentium Pro by Jozer99 · · Score: 1

      I have never heard the original Pentium was a RISC chip.

    9. Re:Shades of Pentium Pro by Mancat · · Score: 1

      No, it was not a RISC chip by the true sense of the word. The Pentium was, however, essentially a RISC chip internally, translating incoming CISC instructions to RISC microcode.

      Intel still has datasheets lying around on their FTP site, if you're that interested. Honestly, I haven't read them in many moons, but the last I checked, the Pentium Pro was not the first in the Pentium line to translate to RISC internally.

      --
      hello dear sirs my name is jamesh i are india (bihar) can u guide me install red had linux 9?
  22. Haha... DRTFA by Zo0ok · · Score: 3, Informative

    Haha... I didnt read the fucking article first ;)

    I better flame myself before someone else does. This was about "Windows Longhorn Server". Sorry Intel - this must suck big time!

    1. Re:Haha... DRTFA by owlstead · · Score: 0

      It is only a "fucking article" before someone reads it. After that, it's just "the article".

  23. Wouldn't it be funny... by mosel-saar-ruwer · · Score: 4, Interesting

    ...or at least ironic, if the only operating system that gained a foothold on Itanium proved to be...

    [drumroll please]

    ...VMS?!?

    I mean, talk about a soap opera:

    1) David Cutler leaves DEC for M$FT, where he unveils a VMS++, dubbed "Windows NT".

    2) DEC invents Alpha, but the only way they can garner any OS support for it is by porting their own VMS and positioning Alpha as a replacement for VAX.

    3) DEC sues M$FT to port "Windows NT/VMS++" to Alpha.

    4) Intel & HP enter into a partnership to build a next generation super-chip.

    5) Compaq purchases DEC.

    6) Compaq sues Intel for theft of much of the intellectual property that went into Alpha.

    7) Intel settles with Compaq by purchasing the manufacturing rights to Alpha.

    8) HP purchases Compaq.

    9) HP cancels Alpha and announces that the new upgrade path for VMS customers is Itanium.

    10) M$FT announces an end to support for "Windows NT/VMS++" on Itanium, but then backtracks, and agrees to partial support.

    Who knows what the moral of this story is?

    Maybe: Hardware comes and hardware goes, but software is forever?

    1. Re:Wouldn't it be funny... by Anonymous Coward · · Score: 0

      Well, isn't you clever with the M$FT? You really made your point there, chucklehead.

    2. Re:Wouldn't it be funny... by bmo · · Score: 1

      I don't know where this urban legend that somehow Windows NT grew out of VMS (and that WNT is somehow proof that it was just a renaming of VMS by shifting one letter over), but it's wrong.

      Windows NT was an outgrowth of OS/2, the one-time joint project between IBM and Microsoft. OS/2 grew to become a well thought-out OS now dead from marketing suicide squads, and NT has become ... eXtremely Putrid, soon to become Windows Fistula.

      Just because Cutler came from DEC doesn't mean that NT is somehow a descendent of VMS. It's like saying that the feces is a descendent of filet mignon.

      --
      BMO

    3. Re:Wouldn't it be funny... by LurkerXXX · · Score: 1
      The numerous features such as ACLs that NT and VMS both have and OS/2 doesn't lend a lot more credibility to those 'urban legends' than some poster on /. saying it's an outgrowth of OS/2.

      Dave Cutler wasn't just some guy from DEC. He was one of VMS's main architects. Imagining he applied a lot of what he learned writing VMS to NT just doesn't take that much imagination.

    4. Re:Wouldn't it be funny... by myg · · Score: 2, Informative

      WinNT is a derivative of VMS if you look at the kernel internals:

          * Packet-driven I/O subsystem
          * Delayed Procedure Calls
          * Asynchronous Procedure Calls
          * The security model at the lowest level
          * The object manager (although it was somewhat non-formal in VMS)

      I mean, if you've ever programmed both systems at the kernel level you would be pretty shocked how similar they are. I mean, WNT feels like a more modern VMS with some things new and some things removed (sadly, like the amazing VMS cluster support).

      The kernel of NT really is very VMS-like. Its not a bad kernel at all, either. Just because the crap M$ piles on top of it is utter shit doesn't mean that the underlaying kernel isn't of very high quality.

    5. Re:Wouldn't it be funny... by rubycodez · · Score: 1

      HP has THREE OS for which they're trying to force sales of Itanium: they are discontinuing PA-RISC for HP/UX, their inherited MIPS machines for NonStop (used to be Tandem), and Alpha for VMS (made the last batch of those last year and soon will stop selling them.

    6. Re:Wouldn't it be funny... by bmo · · Score: 1

      "The numerous features such as ACLs that NT and VMS both have and OS/2 doesn't lend a lot more credibility to those 'urban legends' than some poster on /. saying it's an outgrowth of OS/2."

      Well, it was. They even shared filesystems, until Microsoft took their ball and went home. It's not "just some guy on /." (me) saying it's an outgrowth of OS/2, but everyone else that lived through that era from 1987 until the virtual death of OS/2 sometime in 1997.

      http://www.os2bbs.com/os2news/OS2History.html

      "1990 - The Schism

      In 1990, IBM and Microsoft were still working together on the development of OS/2. Microsoft, however, had found that Windows 3.0 - released in May 1990 - generated more revenue for them and therefore allotted increasingly more resource to Windows and correspondingly less to OS/2.

      By late 1990, Microsoft had intensified its disagreements with IBM to the point where IBM decided that it would have to take some overt action to ensure that OS/2 development continued at a reasonable pace. IBM, therefore, took over complete development responsibility for OS/2 1.x, even though it was in its dying days, and OS/2 2.00. Microsoft would continue development on Windows and OS/2 3.00. Shortly after this split, Microsoft renamed OS/2 V3 to Windows NT."

      Dave Cutler wasn't "just some guy", true, but OS/2 and NT were the _same product_ up until Microsoft re-released OS/2 as Windows NT 3.1

      The whining from DEC was that supposedly Dave Cutler brought Mica code from DEC with him, but we'll never know that because the agreement is secret. (the bits that are public, though, the negotiators on DEC's side didn't get much). Microsoft didn't steal Cutler, btw, they hired him outright after DEC cut off his project (Mica).

      Microsoft likes to endorse the legend that NT came from VMS. They do it because it gives NT an air of "legitimacy" that it somehow is _directly_ descended from a "real operating system", which it didn't.

      Yes, NT has a some of the concepts similar to VMS (DACLs), and descendents of VMS in the years after NT 3.1 included concepts developed in NT (the Registry) and ported into VMS all as a result of MS and DEC becoming buddy-buddy after the Agreement. Nothing is created in a vacuum. But to say that NT is a direct descendent of VMS, well, that's just plain wrong.

      For a graphical representation:

      http://firedrake.org/paddy/images/non-unix_os_hist ory_0.3.12.pdf

      Notice the solid lines tracing from OS/2 and the _dotted_ lines from VMS.

      And lastly, if NT is a direct descendent of VMS, who is the idiot that removed the stability bits?

      --
      BMO

    7. Re:Wouldn't it be funny... by bmo · · Score: 1

      "I mean, if you've ever programmed both systems at the kernel level you would be pretty shocked how similar they are. I mean, WNT feels like a more modern VMS with some things new and some things removed (sadly, like the amazing VMS cluster support)."

      There was plenty of cross pollination after The Agreement. It just irks me that people spout off that "nt is really VMS" without considering the whole OS/2 history.

      There is a history of various DEC people (besides Dave Cutler) working on OS/2/NT going back to the dark days of 1.0, so I wouldn't be surprised if there's similarities between the structure of the OS/2 Warp kernel and VMS (never wrote anything for Warp).

      It's not like NT sprang fully formed as a pirated version of Mica without OS/2.

      --
      BMO

    8. Re:Wouldn't it be funny... by LurkerXXX · · Score: 2, Informative
      Well, it was. They even shared filesystems, until Microsoft took their ball and went home. It's not "just some guy on /." (me) saying it's an outgrowth of OS/2, but everyone else that lived through that era from 1987 until the virtual death of OS/2 sometime in 1997.

      Really? Because I lived through that era, and I and a bunch of other folks that did think otherwise. I was a VMS user long before NT ever came out. Coming from a VMS background, it's not hard to see more similarities in the foundation of the OS than I see with it and OS/2.

      I can point you to quite a few other sites with evidence that NT is more based on VMS with just some compatible bits from OS/2 included.

      http://www.windowsitpro.com/Articles/Print.cfm?Art icleID=4494

      Looks the the terminology, the table of significant similarities, etc. They included an OS/2 compatability layer and some bits and pieces they had been working on from OS/2, but the basics of the system were VMS-like.

      It wasn't just Dave Culter MS hired away from VMS, it was also about 20 former Digital employees that had worked with him on the Mica project, a whole new updated version of VMS. Whether or not they included exact code they wrote for Mica in NT (and Microsoft's settlement with DEC implies there was), you know they had to implement some of the ideas they had been working on. Software developers rarely like to give up on good new ideas they invent and DEC killed Mica. Incorporating those ideas in NT was the only way they would see the light of day.

      For a graphical representation:

      That's hardly a scholarly study of OS history. Have you looked at their links for references? It's nothing special. For Microsoft, they have exactly two link as references, and one of them is the exact article I posted above for you which states that NT *is* a direct descendent of VMS.

      And lastly, if NT is a direct descendent of VMS, who is the idiot that removed the stability bits?

      In case you hadn't noticed, NT has to run on a LOT more different types of hardware than VMS ever had to. Most of the instability in NT came from driver issues. It's not really surprising that it's more unstable than VMS. As a server/desktop rather than a server only OS, Microsoft also made some choices to help out it's desktop performance (moving video to ring0 in NT4, etc) that didn't help stability at all.

    9. Re:Wouldn't it be funny... by LurkerXXX · · Score: 1
      It's not like NT sprang fully formed as a pirated version of Mica without OS/2.

      No, but most of the OS/2 bits are in the upper layer for compatability. They don't make up the kernel and basic heart of the OS. That part is very much VMS-like. The OS/2 bits resides up on top like the Win32 and Win16/DOS and POSIX bits.

      I'm sorry that it 'irks' you that NT isn't treated more as an offshoot of OS/2, but plenty of us do consider the OS/2 history and still think of the heart of NT as a VMS offshoot (no matter how MS might have mucked it up since it's development).

    10. Re:Wouldn't it be funny... by Cabewse · · Score: 1

      You forgot one.

      11) Profit!

  24. Re:Heh. by CyricZ · · Score: 2, Funny

    It is widely acknowledged that Windows ME was a step back in quality and usability. While Longhorn/Vista may not be as great of a leap forward as it was originally portrayed to be, there is little to suggest it will suffer from the massive flaws that Windows ME did.

    --
    Cyric Zndovzny at your service.
  25. Re:Fortran programmers don't need (or want) Window by slavemowgli · · Score: 5, Insightful

    I think you fail to realise an important thing: change typically happens by evolution, not revolution, and that's even more true when there's a multi-billion dollar industry involved. Do you honestly believe that everyone's just going to throw every system they have away?

    It's not gonna happen. The industry likes migration/upgrade paths, and in 90% of all cases, a design that extends is gonna win over one that outright replaces.

    Intel seems to have been unwilling to face that fact, but what they failed to realise is that their monopoly is not big enough to simply force change on people - rather, their move just gave AMD etc. an opportunity to slowly but steadily chip away at that monopoly.

    From a market perspective, that's a good thing, of course - but if I was an Intel shareholder, I'd demand that heads roll for this gross mismanagement in the top executive floor.

    --
    quidquid latine dictum sit altum videtur.
  26. They've had chips fail before. by CyricZ · · Score: 1

    They had the Intel i860 architecture fail in the 1990s. Remember, Windows NT originally targetted those chips.

    But they're a big company. They will overcome such failures.

    --
    Cyric Zndovzny at your service.
    1. Re:They've had chips fail before. by WalksOnDirt · · Score: 1

      Don't forget the iAPX432 from 1981, their earlier huge failure.

      --
      a,e,i,o,u and sometimes w and y (at be if of up cwm by)
  27. Xserves? by pepicek · · Score: 3, Funny

    And what about Itanium in Apple servers? Does anybody think it's possible?

    1. Re:Xserves? by rockinrobotix · · Score: 1

      judging by the fact you are at Score: 3 Funny...

      No.

  28. Also supported by KoolDude · · Score: 3, Funny


    Itanium Will Only Be Partly Supported by Longhorn

    ...the Microsoft executive also added that MyDoom, NetSky, Sobig, Sasser and MSBlast will be fully supported out of the box.

    --
    getSexySig(); /* returns sexy signature */
  29. Software-cut features by b100dian · · Score: 0, Troll

    Longhorn will run three types of higher-end tasks on Itanium including databases, custom jobs and CRM. However it will not be able to do fax server, Windows Media Services, Windows SharePoint Services, file and print servers, and others.

    Looks like Vista Home Edition to me.

    When were the software makers first allowed to abnormally cut features based on arbitrary critera? It's a real shame.

    --
    gtkaml.org
    1. Re:Software-cut features by Anonymous Coward · · Score: 0

      Since the beginning of writing software.

    2. Re:Software-cut features by Anonymous Coward · · Score: 0

      OTOH it does make some sense, or at least it probably won't be a problem. Those IT shops that have databases that are so large and/or has so many users that they need to buy high-end Itanium systems probably wouldn't dream of using that server (or likely, a cluster of Itanium servers) for anything else.

      File/print, WSS, WMS etc. aren't that CPU or memory intensive; an x64 processor system (possibly multi-CPU) would suffice and will, for the foreseable future, be much cheaper. .m

  30. It doesn't matter what Intel wants. by CyricZ · · Score: 1

    It really doesn't matter if Intel would prefer some open source OS or Windows running on their chips. What matters is what the customers want. If the customers want Windows, even if they must wait several years for Microsoft to offer such support, then that is what Intel will have to live with.

    It'll do no good for Intel if open source OSes support their chips years before Windows does, but relatively few people want to use the non-Windows operating systems.

    --
    Cyric Zndovzny at your service.
  31. Re:Fortran programmers don't need (or want) Window by TheRaven64 · · Score: 4, Interesting
    The Itanium was the only realistic chance we had to get away from the x86 for the forseeable future, and the designers blew it.

    PowerPC/POWER is still viable, and IBM may have another go at putting them in consumer machines if an OS that runs on PPC becomes popular in the desktop space.

    ARM-derived chips are still going strong. At IDF there was an XScale chip demo'd that ran at 1.25GHz - probably fast enough for 90% of users.

    Alpha remains my all time favourite architecture - pure 64-bit, and the PAL code concept is remarkably elegant.

    --
    I am TheRaven on Soylent News
  32. Excuse me by ceeam · · Score: 1

    "On the positive side, Microsoft does see a future for the chip..."

    Sorry, what's positive about that? I guess 99.9% of slashdotters could not care less.

  33. Contradictory news by flaviusc · · Score: 1
    According to Anandtech http://www.anandtech.com/news/shownews.aspx?i=2484 6 Microsoft will focus on Itanium !

    Where is the truth?

    1. Re:Contradictory news by cnettel · · Score: 1

      1. Recompile.
      2. Rip out anything that doesn't work and doesn't have to work if you just use it for massive databases.
      3. Make the press release about how you've optimized your offering for the "workloads" that still work on the system.
      4. ????
      5. Profit!

  34. Just pull the plug already by Billly+Gates · · Score: 1, Interesting

    Itanium is a joke.

    Its all the things these newer PentiumV's and PentiumMII's that are coming out, supposed to be. They are VLIW and use very little power, slim, and efficient.

    Itanium was supposed to really take off back in 1997 according to all the analysists. How many years is that? Good lord!

    HP shot itself in the foot because they had no concept of sunkin investments or sunk costs and demanded everyone use their hogs with full 1 pound heat sinks and a fan that sounds like a jet engine taking off.

    To me the heat sinks alone and the fans show me something is seriously wrong and they are trying to overclock the chips to rediciously speeds just to look normal compared to the pentium's and alpha chips.

    Why couldn't the alpha live?

    I think moving optimizations in software is a bad idea. Please dont give me this stuff from the Intel marketing department that as time goes on there will be no room for anything on the cpu but cache so move everything to the compiler ...yada yada. Chip fabrication has improved tremendously and something just have to be done in hardware. Engineering wise the Itanium was doomed to the start. If you are going to use LVIW use it right like Transmeta or the newer Intel chips that are comming out.

  35. Re:Heh. by Anonymous Coward · · Score: 0

    Oh dear. "Competition is good except when it's against AMD, Apple, or Linux."

    This retard not being modded down to -1 for such a pathetic comment is a perfect example of rampant fanboyism within slashdot.

    Firstly, Intel isn't going anywhere, and secondly, the lack of Intel would make AMD's CPUs more expensive and lower quality. Anyone who doesn't believe AMD would behave just as badly as Intel in the same position is both a fanboy and an idiot.

  36. Just as well ... by Anonymous Coward · · Score: 0

    It's just as well that MS is moving away from Itanium since they seemed have problems with it.

    Back in the Itanium 1 days, I did a ported to some IA64 engineering samples running both Linux and Windows. The Linux was straightforward, but the Windows was odd. They used 64bit pointers, but 32bit longs, which tripped us up in a few places. It seemed like a desperate "We can't actually use this because all of our other stuff will break" kind of move from MS.

    I really didn't notice much in the way of compelling performance either. Now, the Itanium 2s are probably much better, but I suspect Windows still has that odd 32bit long behavior.

    1. Re:Just as well ... by KarmaMB84 · · Score: 1

      Why would you change the length of a storage datatype?

    2. Re:Just as well ... by forkazoo · · Score: 1

      Because the length of the register has changed, and a lot of code assumes that long will hold a pointer. The whole idea of programming in a higher level language is that as new hardware becomes available, your code base will take advantage without a rewrite.

    3. Re:Just as well ... by Anonymous Coward · · Score: 0

      That is essentially lesson 1A in 64-bit programming. Do NOT assume that a pointer is the same size as either int, long or long long.

      You shouldn't store pointers as integers in the first place (they are not guaranteed to be integers!), and if you absolutely still have to do it you should use the size_t type of ISO C, which is defined to be the same size as void *.

  37. I see by pklinken · · Score: 0

    ICZilla
    Definitely iczilla.

  38. Re:Heh. by nickos · · Score: 1

    I don't know that that's such a good thing. A couple of years ago I was hoping that Itanium would supercede the clunky x86. I guess that was wishful thinking :(

  39. Re:Heh. by IdleTime · · Score: 1

    Not for Intel, no, no way. Too big and as far as i see, not even AMD is a nail in that coffin and I use AMD64 chips on all my machines.

    Itanium is a horrible CPU, I have no lost love for this beast. I've been waiting for this to happen and I'm happy! :)

    --
    If you mod me down, I *will* introduce you to my sister!
  40. Re:Fortran programmers don't need (or want) Window by Anonymous Coward · · Score: 0

    In my experience Itanium is great.

    The problem has been that it has been too hard to get away from x86.

  41. Who cares? by Anonymous Coward · · Score: 0

    It should be noted here that MS currently owns about 65% of all of the Itaniums in existence. From the numbers that I was able to dig up there are only about 2-3k Itaniums in existence outside of Redmond. I have an Itanium2 in my office. It is loud as hell and causes brown-outs in my corner of the building if more that 2 are plugged in at one time.

    Unfortunately, MS bound by contract to support itanium in Vista.

  42. Re:OS x86? by Krach42 · · Score: 2, Informative

    I think he was intending on saying "OSX Intel". A lot of people are calling it "OS x86" and just assuming that people get that they're talking about Mac OS.

    Though, Apple have themselves used "Mac OSX Intel" to refer to OSX running on Intel hardware. Thus, I stick with that moniker.

    --

    I am unamerican, and proud of it!
  43. I want an Itanium (tm) ... by Anonymous Coward · · Score: 1, Funny

    ... to replace my aging central heating system :)

  44. Re:OS x86? by CyricZ · · Score: 0, Troll

    Thank you for the clarification. I agree, calling it Mac OS X Intel is far clearer. And it doesn't make you look like a complete cock.

    --
    Cyric Zndovzny at your service.
  45. "On the positive side" by norwoodites · · Score: 2, Insightful

    Is that really a positive side? Everyone I know in the compiler world (well GCC world) complains very much about the ia64 architecture. So why do people think this is a positive side, when really it is a negative side of the world.

  46. Sounds like... by pr0nbot · · Score: 1

    ...the perfect architecture for OS/2.

  47. Resurrect Alpha? by Anonymous Coward · · Score: 0

    Is there a reason why Intel can't/won't resurrect the Alpha line?

  48. Did anyone else by kernel_dan · · Score: 1

    Did anyone else read that first line as:

    Although stopping short of pulling the plug entirely on Itanium, MS has said ver.sicher.ungsvergleich

    MS tears technobabble a new one.

    --

    Illegal? Samir, This is America.
    1. Re:Did anyone else by megrims · · Score: 1

      No.
      What?
      There wasn't any technobabble there. At all.

  49. What will Longhorn/ Vista have? by joelsanda · · Score: 3, Insightful

    Everything I've read on Slashdot and Wired talks to what will not be in Longhorn. What will be in Longhorn that will make it better than XP? More and different vulnerabilities? (Maybe it will ship with a demo .wmv file showing Microsoft executive throwing chairs around offices in response to other MS executives leaving for Google!)

    Seriously ... though I'm an Apple user from before Macs were released I've also used every version of Windows - always at work but I've also had every version except XP at home.

    With each new Mac OS X release I look forward to what will be in that version - but there's little talk around the water cooler regarding what will actually be in Longhorn/ Vista. Unlike Mac OS releases, which people anticipate because of stuff like Dashboard, iTunes integration, .Mac integration, Spotlight and Automator, all I hear is what Longhorn/ Vista won't have ...

    --
    The Luddites were ahead of their time.
    1. Re:What will Longhorn/ Vista have? by Anonymous Coward · · Score: 0

      "all I hear is what Longhorn/ Vista won't have ..."

      Welcome to Slashdot. If you expect to be informed rather than blasted with extreme bias, don't come here.

      Longhorn actually has a boatload of new technology ready for it, but as usual, Slashdot preferes to post all of the negative stories. It's pathetic.

    2. Re:What will Longhorn/ Vista have? by Anonymous Coward · · Score: 0

      That's because you read Slashdot.

      QED.

    3. Re:What will Longhorn/ Vista have? by Alsee · · Score: 1

      What will be in Longhorn that will make it better than XP?

      It will have Trusted Computing,
      meaning it will have a "security chip" with a unique ID number to track you, the master crypto key to your computer will be locked inside the chip, the chip is boobytrapped to self destruct if you attempt to learn the key controlling your system, itcan encrypt your files so that you cannot read or alter them without the chip's permission (thus enforcing DRM systems), and the chip can act as a spy system watching all of the softwre you run and securely sending that spy report to other people over the internet.

      Oh, Vista will also have pretty new 3D-eye candy interface.

      However it drops you back to the minimal graphics interface if you're not using a crypto-locked monitor and a crypto-locked video card and Microsoft cryptographicly signed video drivers to also enforce the DRM security system. Oh, and some software will get locked out and refuse to run except in full interface full DRM enforcement mode.

      Vista will have all this Yummy goodness, and more!

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    4. Re:What will Longhorn/ Vista have? by joelsanda · · Score: 1

      Wow. Can't wait to buy that!

      --
      The Luddites were ahead of their time.
  50. Actually, Another Nail in the Coffin for Microsoft by Anonymous Coward · · Score: 2, Insightful

    There is nothing wrong with the Itanium. The chip is used in some of the world's fastest supercomputers.

    But, the Itanium is quite different from earlier x86 chips, because it doesn't make guesses to try to run a series of binary statements in parallel.

    Instead, the Itanium provides the facility for running statements in parallel, but it leaves it up to the software to decide when and how to do it. That's a good thing, because a compiler, using the original source code, can do a much better job of parallelizing operations, than the CPU can do with the binary. This is even more true for languages that are designed for parallelism.

    However, this improvement does not come for free, rather, in order for software to make full use of the Itanium's speed, the compilers must be updated to produce binary code that will run in parallel.

    Linux can already run quite well on the Itanium, and with further improvements to GCC, Linux and its applications will do even better.

    So what's wrong with Windows on the Itanium?

    Well, to put it bluntly, Microsoft is a technically deficient company, and they have failed to make the necessary compiler changes for the Itanium. And with this announcement, they are telling us that they also don't expect to do it in the near future.

    But then, we already knew that Microsoft is technically deficient. Just look at how:

    - DOS stagnated until DR-DOS introduced some new ideas.
    - IE stagnated until Opera and Mozilla introduced some new ideas.
    - Microsoft's first usable GUI (W95) came ten years after the Macintosh, and five years after Geoworks.
    - Microsoft cancelled all its earlier 64-bit support.
    - Microsoft can't seem to fix its security problems.
    - Microsoft needs to hire outside talent to open up new directions (NT 3.51, C#).
    - Microsoft had to sabotage WordPerfect rather than compete with it.
    - Microsoft had to "cut off Netscape's air supply" rather than compete with it.
    - Microsoft had to "grow the polluted Java market" rather than compete with it.
    - New Windows versions miss dates and deliverables by years.
    - And so on.

    Now consider what is going to happen to Microsoft as the market moves to the newer multi-core CPU architectures from IBM, Sony, and Intel. Do you really think that Microsoft is going to be able to keep up with technically-able competitors like Linux?

    I suspect that Microsoft still has some opportunities to adopt the work of others, for example, building the next Windows on BSD (if they haven't done it already with Longhorn/Vista).

    But sooner or later, Microsoft is going to run out of ways to beat their opponents though copying, sabitage, legal manouvers, and FUD.

    At that point, Microsoft will have to compete based on the merits of their software. And their history makes is doubtful that they can succeed.

  51. Re:Heh. by Sephiriz · · Score: 1

    Shouldn't someone mod parent as funny?

  52. Two points.... by mosel-saar-ruwer · · Score: 1

    1) Does the fact that DEC successfully sued M$FT for theft of intellectual property mean anything to you? The resolution of that suit [or threat of a suit - I forget the details, and I'm too damned lazy to Google them] was that M$FT would port Windows NT to Alpha. Unfortunately for DEC, NT on Alpha never grabbed much "mindshare", and withered on the vine.

    [By the way, Alpha's greatest opportunity was lost when DEC missed the chance to become the supplier of the successor to the 68000-series in the Macintosh. It makes you wonder how that whole sordid soap opera might have played out had DEC instead capitalized on the opportunity.]

    2) When you write "that NT is somehow a descendent of VMS [is] like saying that... feces is a descendent of filet mignon", I am very tempted to reply quod erat demonstrandum.

    1. Re:Two points.... by rubycodez · · Score: 1

      read biography of David Cutler before saying anything about no VMS influence in NT. As part of master's program at IIT I actually had to do a paper comparing VMS and NT, NT inherited much in the realm of scheduling, interrupt handling, memory management. If your only view of an OS is user interface and high level API then of course they will seem different

    2. Re:Two points.... by bmo · · Score: 1

      "2) When you write "that NT is somehow a descendent of VMS [is] like saying that... feces is a descendent of filet mignon", I am very tempted to reply quod erat demonstrandum."

      Ok, ok, poor choice of analogy. :-P

      It was a threat of a lawsuit. They shook hands, signed papers, and became best of buddies afterwords, with DEC/Compaq getting a pittance of a settlement and the rights to resell Microsoft products, also for a pittance.

      If it could have been proven that, yes, a whole crapload of Mica was dumped into the NT kernel (which would have transformed it into something the OS/2 crowd could never recognize) I believe that DEC/Compaq could have/should have held out for a whole lot more.

      --
      BMO

  53. Re:Heh. by Anonymous Coward · · Score: 0

    So, you don't want diversity?

    Do you think computing is more fun today, than during the 80s? when there were lots of different machines/CPUs and OSs?

    Are you happy when the world is x86 only?

  54. Re:Heh. by Anonymous Coward · · Score: 0

    Does this remind anyone else of WindowsME?

    Yes, it was a minor update for the unstable 16/32-bit hybrid Windows 4.x branch, thankfully the last one.

    Is this what we can expect for Redmonds latest and greatest?

    Windows Vista and Longhorn Server will in contrast be a major upgrade to the NT series, going from NT 5.x to 6.x, introducing a new API to succeed Win32 (with a heritage from NT 4.x), an entirely new desktop interface, and much more. I can't really compare these two. Even with dropped features, Vista has still a ton left, and still clearly warranting the NT 6.0 tag it has.

    It's a lot of changes, the question is whether how it'll end up when everything is in. A lot of new stuff and changes doesn't automatically make a good OS. But a minor update like Windows 98 -> Me it's clearly not. You may want to check out a list of end-user features that so has not been pulled.

  55. Re:Actually, Another Nail in the Coffin for Micros by nickos · · Score: 1

    "for example, building the next Windows on BSD (if they haven't done it already with Longhorn/Vista)"

    IIRC, MS has already used BSD code for the TCP/IP stack in NT 3.1. MS bought the code from a third company called Spider that had copied and modified the BSD TCP/IP stack.

  56. What do you think their emphasis on power is? by 2nd+Post! · · Score: 2, Interesting

    If that's not a course correction, what do you think is?

    You may dismiss power consumption improvements, but if you think about it carefully, improving power consumption IS improving performance.

    If you can halve the power consumption of a chip, it means you have the energy budget to now 'double' the power consumption of a chip, and possible double the performance.

    Their netburst architecture hit a power wall; its pretty difficult to operate 120W CPUs. If they can get the same performance at 12W, and then increase the available power to 120, they can now get upwards of 10x the performance, barring process inefficiencies.

    Power consumption is a big deal. Think of it this way: A car that doubles it's fuel efficiency from 12mpg to 24mpg can now go twice as far on the same tank of gas. So with CPUs; double the power efficiency, and double the available amount of compute resources.

  57. The x86 market: evolution vs. revolution by aaronl · · Score: 1

    Intel certainly misjudged the market with Itanium, which is a shame. It would be wonderful to have chips in the consumer channel that were as good as Alphas, UltraSPARCs, PA-RISCs, etc. There are very good arguments for just dropping x86 as lacking future improvement potential. Intel managed to do that, and still have a compatibility layer for the old x86 software. If they could've gotten the price down on the Itaniums, there would probably have been a good market for them.

    Instead, you have companies, like HP, that dropped their own architecture in favor of Itanium, since it *was* good enough to replace their own product. That saves them quite a bit of money.

    However, we do just throw out compatability in the x86 world, sometimes. We threw out IDE and replaced it with something new. We do the same for memory interfaces, and expansion interfaces. We move around on RAM like nobody's business (FPM, EDO, SDRAM, DDR, RDRAM, DDR2). SATA already has two versions, USB has three, Firewire has two. At least SATA can be converted to and from IDE, and USB and Firewire are mostly compatible with the other variants within their standard. You can't get rid of your IDE ports, though, because there *still* aren't a huge number of optical devices with SATA ports. Then there's PCIe, which is completely incompatible with PCI/PCI-X.

    We change CPU sockets constantly, mucking with the numbers of pins and type of interface. You have vendors that dropped PS/2 ports in favor of USB, but not all boards can emulate PS/2 devices properly for OS' that don't support USB HID.

    Most of the time, the PC world comes up with new standards to "fix" the old ones, but ignore existing standards that already do what they're talking about. SATA came about when we could've chosen one of the SCSI standards as the new consumer storage interface. PCIe comes out when we already had PCI-X 2.0. You get something like RDRAM when there was already DDR SDRAM. Rarely are these new things any better, and you end up having to create whole new product lines, too.

    The future doesn't look all that much better, either. You have a variety of display interfaces that are being pushed. Optical storage has a ton of different formats, with very little standardization. DRM is getting shoved into everything, making using the computer more difficult.

    You might take a glace and think that the industry likes upgrade paths, but if you look a little deeper, you can see they don't. They want a regular stream of new standards that will force everyone to buy all new equipment.

    As for evolution of the instruction set... if the ISA is broken, you do have to just throw it out to fix it. That's why all the chips on the market execute totally different instructions on-chip vs. what is being sent to them. x86 exists as nothing more than a compatibility layer for everyone.

    1. Re:The x86 market: evolution vs. revolution by Anonymous Coward · · Score: 0

      "x86 exists as nothing more than a compatibility layer for everyone. "

      Although you do have a point, that is a huge exaggeration.

    2. Re:The x86 market: evolution vs. revolution by aaronl · · Score: 1

      I'm quite serious on that one. The internal instructions on P3, P4, Itanium, Athlon, etc. are not x86 instructions. They're much closer to a RISC architecture with an instruction translator on top.

      The execute an instruction you send an opcode to the chip, with certain parameters. Those opcode were what made up the ISA. (ie: MOV, ADD, LEA) Modern chips take those opcodes, and decode them to another set of more simple opcodes. Those are then executed. AMD calls those internal instruction ROPs; Intel calls them micro-ops.

      Though it wouldn't be a simple job, they could do decode for another architecture by replacing those decode units. That is was Transmeta was doing with their on-the-fly decode reprogramming.

      Intel chose to use a completely different ISA on the Itanium. Because of type of ISA they created, the couldn't just use different decode units since their new one was dramatically different. Instead, they put a complicated emulation layer in that would allow legacy x86 opcodes to execute on the CPU. However, this made that legacy code much slower than native code. It was intended as a transition feature while people moved to Itanium native code.

      I don't believe there are any modern processors that execute x86 instrutions on-chip. They all convert x86 to their on-chip instruction set before the execution unit gets ahold of it.

    3. Re:The x86 market: evolution vs. revolution by Anonymous Coward · · Score: 0

      Via's x86 stuff?

    4. Re:The x86 market: evolution vs. revolution by aaronl · · Score: 1

      I'm not sure about VIA. They probably are doing the same thing. At the same time, they're really cheap processors, so they might not have the bells and whistles of the other companies.

  58. hummmmm. by WindBourne · · Score: 1
    Very short memory, then.
    1. OS 3xx
    2. OS-32/34/36/38/400
    3. PDP-Vax.
    4. Dec Unix.
    5. HP-UX on pa-risc.
    6. Solaris on sparc.


    In fact, other than Intel, only chips that had either company supported OS or an OS that was not under control of somebody else , has had a long life. And x86 arch. has outlived its purpose only due to an illegal monopoly (as in unnatural) in MS (and probably Intel as well).
    --
    I prefer the "u" in honour as it seems to be missing these days.
  59. Re:Heh. by Anonymous Coward · · Score: 2, Funny

    They should use that as their slogan. Windows Vista: Not Worse Than XP!

  60. What the Alpha engineers thought about Itanium by pesc · · Score: 2, Informative

    This document (PDF) is from 1999 and explains why the Alpha engineers thought Alpha would win over Itanium.

    http://www.raytheon-computers.com/ref_docs/alpha_i a64.pdf

    The rest we know; the Alpha was ditched when HP bought Compaq (who bought DEC earlier), because HP wanted to eliminate any threats to its Itanium bet.

    --

    )9TSS
    1. Re:What the Alpha engineers thought about Itanium by iggymanz · · Score: 1

      go to HP's website and see they are *still* selling Alpha based servers. This is the last year for them, though. so what's this nonsense about "ditched", they've been selling Alpha machines for the six years since 1999?

    2. Re:What the Alpha engineers thought about Itanium by cnettel · · Score: 1

      Wasn't Compaq's decision to break off their part in the Windows 2000 Alpha development, thereby stopping the product at the stage of Release Candidate 1 or something, quite significant? Windows was never very popular on Alpha, but the decline in support from upper management started long before HP got involved.

    3. Re:What the Alpha engineers thought about Itanium by Anonymous Coward · · Score: 0

      Maybe not ditched, but Compaq essentially gave up on it, just a few months before being acquired by HP. Since Capellas and Fiorina were already quite far in merger talks at the time, it is reasonable to believe that this was part of their common strategy.

      Compaq not only cancelled the next-generation Alpha EV8 design project, but they also cut down the EV7 project. According to the original plans, which would have kept the Alpha at the top of the processor heap, the Alphas that they sell now should have come out years ago and been obsolete by now. This is why the fastest processors you can buy now are x86 and POWER5.

    4. Re:What the Alpha engineers thought about Itanium by hughk · · Score: 1

      Alpha still is running fine last time I looked and is doing very well on 'big-iron' systems like at the DoD and various financial exchanges. However, they are all being forced to look elsewhere now as chip development has stopped. HP is supposedly offering a migration path to Itanium, but there are problems with that so they are still selling Alphas.

      --
      See my journal, I write things there
  61. Re:OS x86? by Anonymous Coward · · Score: 0

    Though, Apple have themselves used "Mac OSX Intel" to refer to OSX running on Intel hardware. Thus, I stick with that moniker.


    Just to nitpick, Apple actually uses "Mac OS X" to refer to Mac OS X.

  62. Write your own summary by Anonymous Coward · · Score: 0

    This text from this post is copied directly from here: http://theinquirer.net/?article=25928

  63. Re:Fortran programmers don't need (or want) Window by chris-chittleborough · · Score: 1
    The problem is that so much talent and effort (and money!) has gone into building fast x86 processors that it will take an enormous effort (and expenditure) to bring another architecture to a competitive level. IBM, I gather, is not pushing the POWER architecture as far as it could (eg., using highly modular designs to save time and money at some cost in performance).

    You are quite right about the Alpha. If it had gotten a fraction of the Itanium's budget, it would be unbeatable by now.

  64. Re:OS x86? by Krach42 · · Score: 1

    Yeah, well, most people treat whitespace and caps in names as allophonic elements. Meaning that they don't carry specific meaning, they just point out an "accent."

    The Apple world seems full of these though, iMac, iPod, AltiVec, OS X, etc, etc, etc.

    --

    I am unamerican, and proud of it!
  65. Re:Fortran programmers don't need (or want) Window by chris-chittleborough · · Score: 1
    Will x86 machines dominate desktop computing in 2010? It's hard to see where any alternative could come from. I find this prospect quite dismal. Hence my tendency to sometimes day-dream about a world in which Good Design would be more important than Good Marketing or (in this case) rational user risk management.

    So actually I agree with slavemowgli's rebuttal of my post :-)

  66. Re:Heh. by IdleTime · · Score: 1

    Huh?

    I work on the following platforms on a daily basis:
    - x86
    - SPARC
    - PARISC
    - Alpha (yes, they are still out there)
    - IBM servers, both PPC and mainframes (not sure about the CPU types)
    - Itanium

    But I guess that is not enough diversity for you?

    --
    If you mod me down, I *will* introduce you to my sister!
  67. Re:Heh. by hairyfeet · · Score: 1
    Please tell me that is supposed to be funny.Even with as little coding as i know,I know you can't cut out major features without leaving behind bugs.And probably some big gaping security holes.

    Microsoft made a HUGE mistake thinking they could just tack on some pretty face to 9X and get a decent OS.Believe me,As one of those whose PC came with that horrible thing i can attest to that.

    Now Microsoft is making another HUGE mistake by tossing the very stable Win2k and trying to force one OS to be everything for both the business user and the noob consumer.There is a REASON that almost every business I've worked for stayed with Win2k over WinXP pro.IMHO It is a better OS for business(and my personal favorite home OS).It uses less resources,Is rock solid,And compared to WinXP,IMHO,A LOT less buggy.

    But instead of doing the smart thing and making a more secure and feature rich Win2k for business and a less buggy WinXP with more gaming/multimedia options for the home user,Microsoft has decided to try to stuff everything and everyone into one big directionless OS.

    And just as WinME forced me to buy a dead computer at the local repair shop just so i could get my hands on an OEM copy of Win2K i have a feeling that after trying Vista that people will be wiping their HDDs in droves to return to Win2K or WinXP.

    --
    ACs don't waste your time replying, your posts are never seen by me.
  68. i doubt it by petermgreen · · Score: 1

    maybe up towards release and for a short time after the codename may remain used by some but i can't imagine the codename will get used much by anyone after that.

    do you hear anyone calling 98 "memphis" or XP "whistler" nowadays?

    --
    note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  69. Gee... Another instance of insecure Windows by supradave · · Score: 1

    Sure would be nice if someone would utilize the security feature on the Itanium 2 chip to write an OS that would be truly secure. Oh... Someone has.

    Repeat after me. Windows and Linux, for that matter, are insecure because they only run at PL0 and PL3 of the processor. Utilizing all 4 PLs would provide better security. Fortunately, the company I'm at now has done so. Since we have the best brains in the Itanium 2 industry writing the OS, security is just an alpha away (which should be soon).

  70. Re:Fortran programmers don't need (or want) Window by Anonymous Coward · · Score: 0

    The problem with PPC is that it peaked at just below 3 ghz, they cant get it to go faster, hence why apple dropped ppc. It's RISC based, and RISC doesnt scale as well as x86 or any deriviatives.
    Want to see a real dying cpu arch, it's PPC. maybe not POWER, but ppc is. You'll see it for yourself in, oh... about 2 to 3 years, once newer chips surpass PPC in speed and performance. then all PPC will be useful for are low end machines, which will prolly get replaced by ARM.

  71. Re:Heh. by DrMrLordX · · Score: 1

    Have you used 2k lately? There must be some shoddy or non-existant QA on the latest security updates. I recently picked up a fully-functional Acer P3-700 laptop used that shipped with 2k. Once I had it patched up, it would fail to boot after the power had been off for any significant period of time, complaining that the laptop BIOS was not "fully ACPI-compliant". The only way to start it was to start first in safe mode and then reboot. 2k also choked completely on the Trendnet 802.11b wifi card install disc's autorun, and once I got the wireless util installed to enable WEP on the card, the app itself did nothing but produce error sounds when executed.

    It also choked on the usb webcam I tried using on it.

    I installed XP Pro, and every problem vanished.

  72. itanium was beaten by its brother by soldack · · Score: 1

    From what I understand, Intel started the Itanium program with HP because they started to feel the heat of RISC and worried about their architecture's scalability in the future. So off went the team with HP compiler folks to do a VLIW next generation processor where the compiler can figure lots in advance.
    Meanwhile other folks at Intel figured out that they could make the core RISC like and provide a conversion layer to handle x86. The success of the later generations Pentiums put Intel in a situation where they needed to support multiple architectures.

    Remember when everyone was going to use Itanium? Now it is down to a few big boxes like HP, SGI, and Unisys. HP is also one of the biggest Opteron sellers these days!

    I think a few technical things blew it for Itanium. It is a fact that the Itanium sucked at I/O. It had much higher latencies then Xeons and much higher then Opterons. Folks in the high performance computing community know that the same PCI-X networking cards (InfiniBand, Myrinet, etc) always performed worse on Itanium based systems.

    Also the combination of the VLIW architecture and lots of registers made the Itanium very cache hungry. You can get as much as 9 MB of L3 cache. They increases cost and die size. Also, all that cache has to be powered! I don't think Intel/HP saw it coming.

    Currently Intel has to support Intanium, P4/Xeon, EM64T variants, Pentium M variants, and lets not forget its XScale based line of network/embedded processors it got from DEC. At least the i960 is dead.

    I think Intel has lost their focus. Those of us in the InfiniBand community watched Intel screw up their 2nd gen InfiniBand adapter and got beat to market by a startup by the name of Mellanox. Since they couldn't win they decided not to play anymore. Suddenly we get PCI-Express...aka InfiniBand without the networking and as much management. Advanced Switcing Interconnect almost gets us back to IB...arg.

    Intel was the first ethernet NIC to 10 Gig but now their competition has TCP/IP and iSCSI offload and iWarp/RDMA interfaces while Intel has canceled their full TCP/IP offload technology and doesn't even have a PCI Express adapter ready.

    Intel is relying on marketing and manufacturing power to keep it going. They hope that the brand can be stronger then the sum of its parts. Centrino, ViiV, etc. Sadly, I don't think it will change until the biggest gun in the PC industry actually gives AMD a try. I suspect Dell is getting better prices on Intel CPUs then anyone else.

    --
    -- soldack
  73. I seem to recall. . . by jcocomo · · Score: 0, Troll

    I seem to recall Microsoft making the same announcement that Longhorn will not fully support the 486 when the 486 came out.

    Anyway, I'm sure that the Itanium will be obsolete by the time Longhorn comes out. . .

  74. The Story Sucks... by Anonymous Coward · · Score: 0
    There is a lot better story for this on Infoworld. I'm not sure if the Inquirer is a Chinese translation of something, but check this article out. It's a lot better read and explains things in a much more understandable manner

    The Itanium is definately NOT dead - we're selling them like crazy.

    Thanks -

    http://tinyurl.com/e3ynh

  75. Re:Heh. by Anonymous Coward · · Score: 0

    No, I also work with VAX. ;)

    It is kind of fun to run VAX Macro code on Itanium.

  76. Itanium is rarely used on windows anyway by wtarreau · · Score: 1

    Real itanium customers stack them in 42U boxes with linux or whatever they want to run on them, and use them for financial, mechanical or weather computations, a domain where windows is not the best OS anyway.

    It's sad that itanium support is removed from windows though, because alpha which had currently itanium's place did not resist long after microsoft stopped supporting it.

    Thinking that HP killed the alpha and Microsoft killed the itanium makes me feel like those companies killed the two most innovant chips of those last 15 years.

    Willy

  77. Re:Gee... Another instance of insecure Windows by Slashcrap · · Score: 1

    Utilizing all 4 PLs would provide better security. Fortunately, the company I'm at now has done so.

    There's more to a secure OS than privilege levels. Is your OS also completely free of any bugs that would allow privilege elevation?

    You're not going to show us the code, so at the moment your OS is on the same level as snake oil encryption products. It may very well be the best thing since sliced bread, but we only have your word for that. And since you seem to think that being able to use Rings 0-3 on its own is enough to make your OS completely secure for all time, your word does not currently count for very much.

  78. Huh? by TheLink · · Score: 1

    Nothing wrong with Itanium?

    Look the SPEC CPU2000 benchmark results.

    Compare the performance of the top Itaniums with the top P4s and Opterons.

    Also compare[1]:
      number of transistors
      (don't forget to factor caches as well).
      die area used.
      power consumption.
      price

    Now can you really say there's nothing wrong with the Itanium?

    The Itanium 2 needs about 210-410 million transistors to perform in the same ballpark as P4s or Opterons with about half to 1/4th the number of transistors.

    A dual core Athlon64/Opteron with 1MB cache only needs 154 million transistors, 2MB cache versions need 233 million transistors.

    Academicians and "True Believers" can talk about VLIW/EPIC and fancy compilers, but I argue if the application you run is so easy to parallelize so that it makes really good use of all the VLIW/EPIC units, then will it really be so hard to make it work in parallel and make good use of both the cores of a dual core opteron?

    Maybe in theory there's nothing wrong with the Itanium. But in practice there's nothing that great about it, except for some FPU tasks (but if that's the case how about a bunch of DSPs?)...

    [1]
    Itanium
    P4
    PM
    Opteron/Athlon64
    Dual core Athlon64/Opterons

    Let me know if the above site has the numbers wrong.

    --
  79. Re:Fortran programmers don't need (or want) Window by Bert64 · · Score: 1

    Alpha could have got us away from x86 a few years ago, when the alpha could emulate x86 and still beat it performance wise..
    Unfortunately, it was too expensive and could only run win32 and x86/linux apps, while many people had win16 and 16-bit dos apps... Had they maintained development, it might have been feasible more recently with far less people needing win16/dos compatibility and such compatibility could be implemented via a full system emulation like bochs or qemu.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  80. Why do you like the Itanium's design? by TheLink · · Score: 1

    Since you like the design, can you please explain why the Itaniums have 2x to 4x the number of transistors but are only in the same performance league as the P4s or Athlon64/Opterons? Is Intel burying the Itanium by making Itaniums with more transistors than they need? Or is the Itanium that inefficient?

    See the SPEC CPU2000 results.

    And the Itanium physical specs. You can click on the side bar for other CPU physical specifications.

    With 2x to 4x the transistors you could get a dual core or even two dual core x86 CPUs.

    Don't forget each of the x86 cores taken alone will perform quite well, even in FPU tasks. The Itanium is 2x to 4x faster for some SPEC FPU subtasks, but is slower in others.

    If it becomes easy for compilers to parallelize execution across many VLIW/EPIC units, then would it be so much harder for them to parellelize execution across multiple x86 cores?

    Heh, or start running some of those FPU tasks on commodity GPUs ;).

    --
  81. Re:Gee... Another instance of insecure Windows by supradave · · Score: 1

    We will release PL0 out for review. I doubt it will be open source by any means, but it will get reviewed. If PL0 is not what we say it is, i.e. secure, than we'll be eating crow. If it is secure, well then, you'll be hearing about us.

    Fortunately, it's not encryption.

    Built in to the chip are 16 million compartments (or priviledged memory locations limited by the 64bit address space) per PL where permissions can be set for read, write and/or execute. Imagine, for example, reading in win.exe, running a verification that win.exe is the win.exe you want to run, then setting the execute bit and running it, knowing that your win.exe is the one you wanted to run and not one that has been corrupted through other means.

    The NSF is already pretty certain.