Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Sunday October 15 2017, @07:07PM   Printer-friendly
from the watch-for-bugs-at-the-chip-buffet dept.

High Performance Computing (HPC) Chips – A Veritable Smorgasbord?

No this isn't about the song from Charlotte's Web or the Scandinavian predilection for open sandwiches; it's about the apparent newfound choice in the HPC CPU market.

For the first time since AMD's ill-fated launch of Bulldozer the answer to the question, 'Which CPU will be in my next HPC system?' doesn't have to be 'Whichever variety of Intel Xeon E5 they are selling when we procure'.

In fact, it's not just in the x86 market where there is now a genuine choice. Soon we will have at least two credible ARM v8 ISA CPUs (from Cavium and Qualcomm respectively) and IBM have gone all in on the Power architecture (having at one point in the last ten years had four competing HPC CPU lines – x86, Blue Gene, Power and Cell).

In fact, it may even be Intel that is left wondering which horse to back in the HPC CPU race with both Xeon lines looking insufficiently differentiated going forward. A symptom of this dilemma is the recent restructuring of the Xeon line along with associated pricing and feature segmentation.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
(1)
  • (Score: 0) by Anonymous Coward on Sunday October 15 2017, @07:17PM (6 children)

    by Anonymous Coward on Sunday October 15 2017, @07:17PM (#582719)

    IBM's superior POWER architecture hangs in there, and then suddenly, a RISC-V group begins producing chips that are interesting. IBM says "Aw, fuck it!", and puts all of its POWER resources behind the RISC-V project; this encourages the likes of Google and Facebook to go all in on the RISC-V system, and then the whole world benefits as this open-hardware technology trickles down to consumer products.

    • (Score: 0) by Anonymous Coward on Sunday October 15 2017, @07:49PM (3 children)

      by Anonymous Coward on Sunday October 15 2017, @07:49PM (#582741)

      RISC-V will end up like MIPS, rather than like ARM, due to too much flexibility allowed in the per-chip ABIs.

      The J-series of SuperH clone processors seems a more likely bet in my book, but they need to tape out a 'Pi alternative' chip in the next two years or less and either 64 bit addressing extensions or an SH5 equivalent (since AFAIK SH5 is still under patents and gcc just removed support..) ASAP for any of it to still be relevant. Same problem RISC-V has today: There are no serious plans for making a RISC-V desktop ecosystem, least of all a 'true' multi-source one with intercompatible components and royalty free cross licensing agreements.

      • (Score: 3, Informative) by RamiK on Sunday October 15 2017, @10:34PM

        by RamiK (1813) on Sunday October 15 2017, @10:34PM (#582787)

        RISC-V will end up like MIPS, rather than like ARM, due to too much flexibility allowed in the per-chip ABIs.

        No. RISC-V standardized the extension mechanism to prevent the per-chip ABIs fragmentation that crippled MIPS (off the v2 draft ISA manual):

        Standard-Compatible Global Encodings
        A complete or global encoding of an ISA for an actual RISC-V implementation must allocate a unique non-conflicting prefix for every included instruction encoding space. The bases and every standard extension have each had a standard prefix allocated to ensure they can all coexist in a global encoding.
        A standard-compatible global encoding is one where the base and every included standard extension have their standard prefixes. A standard-compatible global encoding can include non-standard extensions that do not conflict with the included standard extensions. A standard-compatible global encoding can also reallocate standard prefixes to non-standard extensions if the associated standard extensions are not included in this global encoding. In other words, a standard extension must use its standard prefix if included in a standard-compatible global encoding, but otherwise
        its prefix is free to be reallocated.

        The constraints allow a common toolchain to target the standard subset of any RISC-V standard-compatible global encoding, by specifying the supported standard extensions in tool command-line flags.

        The J-series of SuperH clone processors seems a more likely bet in my book

        Why? Once the patent is up you could see just as much fragmentation. Only, unlike RISC-V, there's no mechanism to deal with someone adding extra instructions.

        but they need to tape out a 'Pi alternative' chip in the next two years or less

        SiFive Freedom U500 can be evaluated on a $3.5k FPGA kit and should fit the RasPi3\ODROID-C2 space once produced on both cost and performance.

        There are no serious plans for making a RISC-V desktop ecosystem

        The x86 desktop market is a high-risk, low-reward venture. You're restricted to 4 instructions wide out-of-order superscalar pointer addressing designs since there's too much code to rewrite otherwise. Closest I've seen anyone coming near it was ARM's recent A75 that's targeting smartphones.

        --
        compiling...
      • (Score: 2) by driverless on Monday October 16 2017, @10:13AM (1 child)

        by driverless (4770) on Monday October 16 2017, @10:13AM (#582943)

        Nah, RISV-V will end up like the Motorola 88000, after some initial noise it'll fade slowly into oblivion, accompanied by the sound of no-one caring.

        And I don't mean that as a snarky comment, it's an also-ran with no support infrastructure outside of one or two obscure vendors, why would a device designer go with one of these? You're betting your product, and possibly your company, on a barely-there product that may not exist next month. There's no way I could convince any of my mgt to go with something like this for anything outside of a hobby project done on my own time.

        • (Score: 0) by Anonymous Coward on Monday October 16 2017, @04:22PM

          by Anonymous Coward on Monday October 16 2017, @04:22PM (#583037)

          RISC-V is something that will grow from niche to mainstream.

          You fuckers are always trying to imagine lucrative ventures, but that's not where this will start. As always, it will start in hackers' proverbial garages.

    • (Score: 0) by Anonymous Coward on Sunday October 15 2017, @08:36PM (1 child)

      by Anonymous Coward on Sunday October 15 2017, @08:36PM (#582756)

      Nah, they'll send in the Nazgul making claims of patent infringement and other forms of Imaginary Property theft. ARM And intel will shake their hands and do some more cross-licensing with IBM having one less competitor and the little people lose.

      • (Score: 2) by bob_super on Tuesday October 17 2017, @04:24PM

        by bob_super (1357) on Tuesday October 17 2017, @04:24PM (#583522)

        That's because most people are oblivious as they stare at Kim K's ass on their ARM or x86 machines.
        Now, if you paid enough money for Kim K to release her latest nudies in a way that only decodes on a specific platform, you might see either an uptick of interest, or people starting ignoring her for free porn elsewhere.
        Both are very positive outcomes, where's the GoFundMe page?

  • (Score: 4, Insightful) by frojack on Sunday October 15 2017, @07:23PM

    by frojack (1554) on Sunday October 15 2017, @07:23PM (#582721) Journal

    It would be interesting to put each of these behind a smart firewall and boot to their bios, then install some crippled OS and see which of them call home first.

    --
    No, you are mistaken. I've always had this sig.
  • (Score: 2) by RamiK on Sunday October 15 2017, @09:10PM (9 children)

    by RamiK (1813) on Sunday October 15 2017, @09:10PM (#582765)
    • (Score: 1, Interesting) by Anonymous Coward on Sunday October 15 2017, @10:07PM (5 children)

      by Anonymous Coward on Sunday October 15 2017, @10:07PM (#582775)

      Oracle's approach to Sun's technology seem to be "Fuck it".
      Their willingness to allow those to go out of support (surreptitiously or otherwise) seems very high.

      ...and Oracle is the epitome of closed technology.
      This is a company stuck in the late 20th Century.
      Why people would continue to give them money confounds me.

      Don't developers write their code in a high level language today, making the hardware brand immaterial as long as there is a compatible compiler available? [googleusercontent.com] (orig) [gnu.org]

      ...and on the Oracle software side, has anyone ever had a database that was so complex that FOSS couldn't handle it?

      -- OriginalOwner_ [soylentnews.org]

      • (Score: 2, Informative) by Ethanol-fueled on Sunday October 15 2017, @10:26PM (4 children)

        by Ethanol-fueled (2792) on Sunday October 15 2017, @10:26PM (#582780) Homepage

        "Fuck it" regarding Sun's physical technology, sure, but muh Java.

        Regarding your "high-level language" comment, there are plenty of situations where people use inline assembly within their C and C++ code. And that assembly is dependent on the machine.

        • (Score: 1, Informative) by Anonymous Coward on Monday October 16 2017, @02:55AM (3 children)

          by Anonymous Coward on Monday October 16 2017, @02:55AM (#582893)

          For over a decade, I've heard people intimate something like "If you can do assember that is better-optimized than what the compiler can deliver, you're in the 1 Percent of coders and have way too much time on your hands."

          Comments?

          -- OriginalOwner_ [soylentnews.org]

          • (Score: 2) by takyon on Monday October 16 2017, @05:23AM

            by takyon (881) <{takyon} {at} {soylentnews.org}> on Monday October 16 2017, @05:23AM (#582913) Journal

            Yeah, here's a comment. We should ditch all programming languages except JavaScript and Rust.

            --
            [SIG] 10/28/2017: Soylent Upgrade v14 [soylentnews.org]
          • (Score: 3, Informative) by coolgopher on Monday October 16 2017, @07:09AM

            by coolgopher (1157) on Monday October 16 2017, @07:09AM (#582921)

            Or you're working with more obscure hardware with lower quality compilers (that might not even be aware of the full instruction set).

            Or you're working on seriously performance critical code.

            Or you're working on sufficiently low-level stuff where you need register-level control anyway.

            Or you're in the demo scene and write seriously tight stuff for the joy of taking the hardware beyond what anyone thought possible.

            To mention a few.

          • (Score: 1) by Ethanol-fueled on Monday October 16 2017, @10:24PM

            by Ethanol-fueled (2792) on Monday October 16 2017, @10:24PM (#583192) Homepage

            Even if you don't directly use assembly within your C/C++ code when doing embedded stuff you still have the embedded mindset, such as using the keywords volatile and register.

            Volatile marks the portion of code as something which could change outside the code, such as by the hardware, so you don't want the compiler to optimize the code away if it is going to assume that the code is redundant and that there is no code which could change the value of whatever's in the register.

            Register throws the variable into a register to keep it on-hand (close to the processor, you can think of a register as being a kind of RAM that's directly on the processor metal) for super-fast operations. But optimizing compilers "know" when to throw certain variables into registers anyway, and knowing the optimization options available and how to use them is an art in itself.

            Embedded code is fucking everywhere -- dildos, realdolls, IoT devices, weapons and other robotics (3-D printers are a good example), calculators, wristwatches, etc. You don't see much embedded work written in Javascript or Ruby.

    • (Score: 2, Informative) by Ethanol-fueled on Sunday October 15 2017, @10:30PM (2 children)

      by Ethanol-fueled (2792) on Sunday October 15 2017, @10:30PM (#582785) Homepage

      Kind of a tangent here, but many years ago before I had even dreamed of studying computer science I had found a Sparcstation 10 [wikipedia.org] in the dumpster. I took it in and plugged my VGA monitor into it and surprisingly it booted to a command line with no problems. I ended up throwing it back in the dumpster shortly afterward and now I'm kicking myself for that...could have at least sold it to one of you for 100-200 bucks on eBay.

      Would any of you have bought it?

      • (Score: 2) by Post-Nihilist on Monday October 16 2017, @01:48AM (1 child)

        by Post-Nihilist (5672) on Monday October 16 2017, @01:48AM (#582866)

        Did it had it's original keyboard? If so I might have, Sun keyboards were great for all Unixes... Nowaday, i would not cause I have a 200$ mechanical RGB keyboard with 10 programmable keys and 3 in nvram profiles...

        --
        Be like us, be different, be a nihilist!!!
  • (Score: 2) by FatPhil on Monday October 16 2017, @06:20AM

    by FatPhil (863) <reversethis-{if.fdsa} {ta} {tnelyos-cp}> on Monday October 16 2017, @06:20AM (#582917) Homepage
    Blue Gene has had 3 overlapping incarnations, and all of them were Power based. Cell too was just a Power with a bunch of DSPs (of unknown heritage, at least to me).
    --
    Great minds discuss ideas; average minds discuss events; small minds discuss people; the smallest discuss themselves
(1)