Slashdot Mirror


Red Hat Reveals Support For AMD's Hammer

Anonymous Coward writes "Red Hat had been rumored to be working on support AMD's Hammer architecture, and now they have made it official. Now if I can get a hold of one of these my little site will finally be able to handle a good slashdotting with 16GB of DDR333! 'Red Hat will provide native 64-bit support for processors based on AMD's x86-64 technology, while providing support for existing 32-bit Linux-based applications.'" Combine this with Linus' feelings and Hammer is looking better and better.

18 of 170 comments (clear)

  1. Linus's hammer support?! by NicolaiBSD · · Score: 5, Informative

    Doh! Linus doesn't have warm fuzzy feelings towards the Hammer, or rather he's never expressed them. The poster is referring to a post on LKML on paging issues with Itanium.
    Linus didn't endorse one platform or the other, he only explained that if Hammer was to become dominant instead of Itanium, it would save the kernel developers problems solving the Itanium paging problems.

    1. Re:Linus's hammer support?! by cperciva · · Score: 5, Informative

      Linus didn't endorse one platform or the other, he only explained that if Hammer was to become dominant instead of Itanium, it would save the kernel developers problems solving the Itanium paging problems.

      I think you mean linux's paging problems. Specifically, the fact that gcc being broken means that linux uses 32 bits for fields which should be 64 bits.

  2. Hardware upgrade by GodlikeDoglike · · Score: 3, Funny

    Now if I can get a hold of one of these my little site will finally be able to handle a good slashdotting with 16GB of DDR333!

    Just as long as you lose that 14.4 modem you are hosting off.

    Replacing your commodore 64 is just a start ;)

    1. Re:Hardware upgrade by gazbo · · Score: 3, Funny
      Replacing your commodore 64 is just a start

      That's all some people have got - they couldn't fit a bigger computer under the chicken coop, so the Taliban will have confiscated them.

  3. IA-64 anyone? by Critical_ · · Score: 4, Interesting

    Moderate this as a flame if you want cause I am sick and tired of this x86-64 bullcrap.

    Lets see, the history of slashdot and most of computer-geekdom has always ribbed Intel for maintaining backwards compatibility with processors more than a decade old. Sure, x86 is great due to all the applications out for it, but in all honesty why can't we move away from it?

    With Slashdot, Linus and most of the online review sites pushing for x86-64, one has to wonder if AMD is slipping cash under the table to all these parties. If not, then what happened to those people who wanted innovation in the releam of processors and just not cheap hacks upon hacks upon hacks? It's kinda funny but the way AMD is going is sorta the way Microsoft is: maintain backward compatibility at all costs.

    My guess is that most people pushing x86-64 have yet to write a program more complicated than "hello world!". Let's stick to our desire for innovation and truely stand behind the company willing to shed the baggage: Intel.

    1. Re:IA-64 anyone? by div_2n · · Score: 3, Insightful

      For good or for ill, backwards compatibility is usually necessary in order to insure rapid acceptance and usage.

      Imagine you are a software company. "We have to retrain all our programmers, buy new compilers AND ditch our old codebase? Can we still write for the old stuff for now? Good . . ."

      I would bet dollars to doughnuts that if DVD players were incapable of playing CD's, there would be quite a few unhappy campers. The relation is the same -- slowly phase out the old while promoting the new.

    2. Re:IA-64 anyone? by rchatterjee · · Score: 5, Insightful
      Let's stick to our desire for innovation and truely stand behind the company willing to shed the baggage: Intel.
      So where were you when the 64bit Alpha came out ten years ago?

      It had nothing to do with x86 compatability and whooped on all x86 chips on every benchmark that was out there but its all but dead now.

      And now you're saying a architecture that doesn't beat the current crop of x86 chips in performence, breaks compatabilty with the x86 architecture, and costs 10 times as much for similar capabilities will somehow succeed?

      Once you break compatability with vast amount of software that is out there for x86 you're suddenly no better than all the other 64bit chips that have been out there.

      Why go with a relatively untested IA-64 arch when i could go with a Sun, IBM, or SGI box who have all been 64bit for years and have no x86 baggage at all? I'm certanly not saving any money going with Intel's chip plus the other 64bit architectures have much more software support in compairason to IA-64.

      As a customer if i buy IA-64 and it fails in the marketplace and support dries up, I'm left with a fairly useless box that can only run the few programs made specifically for IA-64 but if i buy x86-64 and it fails in the market i still have a very usable x86 machine and tons of 32bit software to work with.
  4. SuSE's work on supporting the Hammer by Roger+Whittaker · · Score: 5, Informative

    Press releases detailing SuSE's work on Linux for the Hammer can be found here (20th March 2002), here (28th February 2002) and here (31st January 2001).

    Roger Whittaker (SuSE Linux Ltd)

  5. 64 bit versions of current tech misses the pont? by shic · · Score: 5, Insightful
    my little site will finally be able to handle a good slashdotting with 16GB of DDR333

    Hmmm. I'm probably more interested than most in the prospects of large address spaces, however I don't imagine typical web sites are where this technology will be best exploited. Think seriously, moving to 8 byte addresses has the following effects:

    1. Massively expanding address space and hence (for the first time - IMHO) making the holy grail of direct manipulation of persistent data structures a realistic proposition.
    2. Expanding the size of today's simple data structures. Consider, for example, a simple bi-directional linked list of 32-bit integers using a forwards and backwards pointer. A 32 bit arch has a 200% overhead, but 64 bit ach has 400% which should somewhat diminish expectations for magical performance!
    Don't get me wrong. I think 64 bit is likely to be at least as important a step as 32 bit was c. 20 years ago, however I don't expect more than a small niche for such systems until resource allocation is re-thought.
  6. Perhaps not by thasmudyan · · Score: 3, Interesting

    I can't help but feel that "real" manager's will just say Itanium plus winXP despite the advantages of Hammer and RedHat

    AMD has almost constantly succeeded to deliver technically better hardware for a lower price. Given the current economic downturn (blabla) and the lessons learned in the dotcom meltdown (e.g. that image is not everything) even your average modestly intelligent manager type will perhaps chose the cheaper, better product. Besides, I don't think AMD is still viewed as that kind of an underdog anymore! And Linux on the server front looks good, too. So I think the chances are good.

    Another issue is of course whether an 64+ bit addressing architecture is needed for mainstream PCs yet. But as we all know: it's not whether you need it - it's whether the industry thinks you need it!

  7. It only took 10 years :) by jukal · · Score: 3, Informative

    Remember this, year 1992?
    "Digital Equipment unveils the 150-MHz Alpha 21064 64-bit microprocessor". That was kind of one checkpoint, this year, I believe might be another.

  8. Remeber when 32bit came in by oliverthered · · Score: 3, Interesting

    My thoughts were the same when 32bit came in, until I relealised.
    The new insturusction and architecture improvements in 32bit x86 made for a good performance overhead.

    The memory bus was twice wide on a 32bit system , so the pointers on the linked list may have been twice the size but becuase of the wider bus there was no performance hit.

    One of the create benifits of 32bit was that you could have numbers +-64000 in one register, giving the greatest performance increase.

    The extra wide bus is gonig to give some performance gains on 64Bit systems, but I don't see the extra address space or larger numbers being that benifitial.. Well maybe the extra address space will help with threading and process management, and mean that bloatware can be even more bloated.

    --
    thank God the internet isn't a human right.
  9. You're missing the real need by back@slash · · Score: 3, Funny

    Anonymous Coward writes: Now if I can get a hold of one of these my little site will finally be able to handle a good slashdotting with 16GB of DDR333!

    Not only that Anonymous Coward, but with the amount of posts you make to /. you need one of those just to keep up!

    --
    This comment was generated by a Squadron of Ultra Ninjas
  10. I remember... by AppyPappy · · Score: 5, Funny
    16 gig???

    I remember when 48K was considered overkill because you couldn't fill it


    I remember when 360k was enough for software and data

    I remember when I got a 20 meg hd for my XT "just in case"

    I remember when I didn't wear these damn Depends. NURSE!!!

    --

    If you aren't part of the solution, there is good money to be made prolonging the problem

  11. Re:what does linux have to do with this? by Rydia · · Score: 3, Insightful

    SuSE made the 64-bit hammer patch and submitted it to the gcc group a long, long time ago. 'Course, no one cares because it was SuSE and not Red Hat or debian. *scowl*

  12. MandrakeSoft as well by joestar · · Score: 3, Informative

    According to a recent press-release, MandrakeSoft has also worked with AMD to get Hammer supported on early 2003.

    The joint Press release (MandrakeSoft/AMD- June 27th) is available here.

  13. Why should we support AMD again? by vandan · · Score: 3, Informative
    AMD have already stated their intention to make Palladium-ready chips.
    Here's what AMD is really thinking ...
    We'll take advantage of Linux Losers' programming ability now (We could sure use all the help we can get there). And then we'll turn around and dictate the conditions under which these 'customers' can use their computers and provide a big-brother service to keep the ol' boys in the white house happy. It makes no difference to us that Palladium will destroy Linux and Open Source software. There's more money in it for us if they have to upgrade every 18 months to an ever-more-inefficient Microsoft Piece of Shit.

    Come on, people, really. Don't support AMD. They are not the noble David against the nasty Goliath. They are just as much a nasty Goliath themself, except for the fact that they don't have much market share... But they sure are acting like they do. If AMD and Intel keep pushing their 'Trusted Computing' wheelbarrow, I swear I will buy an underpowered Transmetta or even a fucking Macintosh just to avoid Palladium.
  14. Re:Why the Hammer will come out first... by roca · · Score: 3, Interesting

    > On the SPEC CPU2000 benchmarks, the two fastest
    > boxes are 1ghz I2s

    That's only true because of Itanium 2's floating-point performance. Real server workloads don't use floating point. For a slightly more realistic workload, look at the SPEC CINT numbers. There, the 1GHz Itanium 2 falls behind 2.4GHz Pentium 4s and Xeons.

    Furthermore, none of these SPEC bencharks are nearly as memory-intensive as real server workloads. That's where Itanium really gets Hammered.