Slashdot Mirror


AMD Sued Over Allegedly Misleading Bulldozer Core Count

An anonymous reader writes: A class action suit accuses AMD of misleading buyers about the number of cores in its Bulldozer-based CPUs. The complaint claims that the chips effectively had only four cores, while AMD claims there are eight. According to Ars: "AMD's multi-core Bulldozer chips use a unique design that combines the functions of what would normally be two discrete cores into a single package, which the company calls a module. Each module is identified as two separate cores in Windows, but the cores share a single floating point unit and instruction and execution resources. This is different from Intel's cores, which feature independent FPUs. The suit claims that Bulldozer's design means its cores cannot work independently, and as a result, cannot perform eight instructions simultaneously and independently. This, the claim continues, results in performance degradation, and average consumers in the market for a CPU lack the technical expertise to understand the design of AMD's processors and trust the company to give accurate specifications regarding its CPUs."

18 of 311 comments (clear)

  1. Extremetech sums it up pretty easily... : by Anonymous Coward · · Score: 5, Informative

    http://www.extremetech.com/extreme/217672-analysis-amd-lawsuit-over-false-bulldozer-chip-marketing-is-without-merit

  2. Re:So AMD called their Hyperthreading a CPU core? by Entrope · · Score: 5, Informative

    AMD's CPU architecture has a similar purpose as hyperthreading -- to share hardware resources between what looks to the OS like independent cores -- but the tradeoff is different. Intel's hyperthreading approach only works to cover memory latency, because the hyperthreads share so many physical resources (I think basically everything except register files and hyperthreading-related state). AMD's is somewhat different in that each "module" has two independent integer ALUs, register files, and L1 data caches. The module has one L1 instruction cache, one L2 data cache, one FPU, and one instruction fetch/decode unit.

    But AMD has always been pretty up-front about this architecture. There is maybe a cause of action against resellers who package the AMD chips into systems and do gloss over which aspects each "core" shares with another core, but AMD publicly presented the core-vs-module distinction well before the chips were released.

  3. Pretty Laughable by TooManyNames · · Score: 5, Insightful

    Why is this even reported? This suit isn't going to go anywhere (unless AMD's lawyers are extremely incompetent, and the judge is extremely incapable of understanding basics about computer architecture and ISAs).

    The AMD cores shared an FPU, sure, but sharing a resource doesn't mean that cores cannot execute simultaneously. The AMD cores still have independent integer-based execution units (instruction registers, register files, ALUs, branch counters, etc.), after all, and are fully capable of executing integer instructions simultaneously (which accounts for the vast majority of instructions under typical loading).

    --
    "Is not a sentence" is not a sentence. Well damn.
    1. Re:Pretty Laughable by Ramze · · Score: 3, Interesting

      I agree. Also, if I understand correctly, that shared FPU can be used either by one CPU core as a 256 bit FPU, or by both simultaneously as 2 independent 128 bit FPUs.

      So, shared, but not likely to be a bottleneck.

      Also, since when do cores have to include all the "extras" ? I recall when 486's had a math co-processor and there were no mmx instructions or other such multimedia or physics sets. This guy is going to have a really tough time explaining how exactly AMD's architecture doesn't provide exactly the number of cores listed -- even if the architecture has its limitations due to sharing resources.

  4. Re:Damnit by Gaygirlie · · Score: 4, Insightful

    The sooner AMD goes down the toilet, the sooner someone competent takes over, the sooner Intel and Nvidia get competitive again.
    At the moment, consumers and society as a whole are suffering from this beating of a dead horse. We need its death accelerated to the whole industry back on its toes again.

    Why do you think AMD going bust would magically mean someone new stepping up to the plate? There are effing ginormous obstacles for a start-up to come and compete in the x86-scene, so much so that it's nearly impossible, and if Intel got a monopoly on the market even for a brief moment the situation would become even worse!

    No, the better option is that AMD gets their shit together, never giving Intel full monopoly on the x86-market even for a bit.

  5. Re:i5, same thing? by Anonymous Coward · · Score: 3, Informative

    i5 is just branding, it doesn't describe physical features. Broadwell desktop i5 has 4 cores no threads, mobile has 2 cores as 4 threads,

    https://en.wikipedia.org/wiki/Broadwell_(microarchitecture)#Mobile_processors

  6. Why did they buy based on "cores"? by rbrander · · Score: 4, Insightful

    I was shopping for VCRs about 20 years back and asked the Future Shop guy how much better it was for having (quoting from the card beside the VCR) a "19 micron tape head". Turns out they ALL had 19 micron tape-heads (whatever the hell that *meant*) as it was the spec for a VCR tape head, at the time, at least. It was just another bit of science-y sounding technobabble to put on the card.
    Buying based on core count is like buying for the 19-micron thing; it's either a fast machine for your purposes or not. Absolutely the only way to tell that for sure is a test. The only thing that was ever useful with, say, "megahertz" was that it had for a decade or so there a correlation with the performance you'd get in real use. I've never found "cores" to have anything of the sort.

    1. Re:Why did they buy based on "cores"? by dotancohen · · Score: 3, Insightful

      Wrong.

      99% of software out there is still single threaded. that makes a old pentium 4 single core running at 4GHZ will beat the hell out of a i7 3ghz 8 core processor brutally if that i7 has hyperthreading turned on essentially cutting the processor speeds in 1/2 to emulate more cores.

      To make this clear: last year I wrote Python-based system to interface with Intuit Quickbooks, which the client was running on a 3.4 Ghz dual-core something. He asked what he could do to improve performance as we really were pushing the limit of that poor machine, I told him to get the fastest clock speed processor that he could as Quickbooks is single-threaded, even when in Multi-User mode or whatever they called it. So the expert at the computer shop convinces the client to buy an octocore 2.8 Ghz something (numbers pulled out of ass for example only) which absolutely tanked performance.

      Tools are tools and the best tool for somebody else's job might not be the best tool for _your_ job. Processors or any other complex component cannot be judged on a single merit alone. See how consumers buy their cameras based on megapixel count for example.

      --
      It is dangerous to be right when the government is wrong.
  7. Re:So AMD called their Hyperthreading a CPU core? by gbnewby · · Score: 4, Interesting

    Concur. The design of the bulldozer modules was abundantly clear. The fact that the "cores" share an FPU was clearly disclosed and part of any diagram of the parts. The shared FPUs played a huge role in assessing bulldozer-based CPUs for high performance computing workloads. For HPC, the usual benchmark is HPL (a.k.a., high performance LINPACK), which is a measure of double precision floating point performance for a particular matrix operation called DGEMM. The fact that the FPU was doing double-duty for two "cores" on a module meant that the peak theoretical performance was limited by the number of FPUs in a CPU, not the number of cores or modules or anything else.

    As others have noted, hyperthreading via Intel can have exactly the same impact: the threads share various components, including the FPU.

    Another aspect that can have a major impact on performance is the number of memory channels, and how things like cache coherency is handled. Among other things, AMD's hyper-transport exhibits different scalability characteristics depending on the number of sockets. In a four or eight-socket configuration, latency due to cache coherency operations can have a big impact on performance.
        - gbn

  8. Re:Damnit by Gaygirlie · · Score: 4, Informative

    AMD has always been behind Intel in the performance area for most of its life.

    Well, there was the Athlon - era where they were sweeping the floors with Intel; the classic Athlons and Athlon XPs were phenomenal CPUs at the time and highly overclockable. It was glorious, but yeah, I think that was pretty much the only time they beat Intel.

    Lets hope AMD gets their shit together. As I've said before. The fat lady hasn't sung yet on AMD but she is warming up in the bullpit. Lets hope that as she waddles up on stage AMD pulls a rabbit out of the hat and she falls off the stage into a tuba.

    I really, *REALLY* hope they can manage to do it, but.. I just haven't heard any promising news in that regards anywhere. There's quite literally nothing to indicate that AMD has in any way or form stopped digging even further down the hole they are already in. I do dread the day when Intel becomes the sole x86 - vendor and can practically demand whatever they want, do whatever they want and laugh all the way to the bank.

  9. Re:Damnit by TheRaven64 · · Score: 3, Informative

    Sony or Microsoft might buy their chip facilities since they do use AMD chips as the CPU/GPU in their consoles

    Given that AMD spun off its chip facilities a few years ago, I think we can probably ignore your market analysis.

    --
    I am TheRaven on Soylent News
  10. Re:The AMD chip by Martin+Blank · · Score: 3, Informative

    Intel doesn't want AMD to die off because that would subject its practices to monopoly scrutiny. It shares just enough patent information with AMD to allow it to trail a bit behind (in exchange for access to AMD patents, of course) and not completely collapse. The one time that AMD managed to move ahead of Intel (when the Athlon was the king of the hill), Intel pulled out all the stops to prevent it getting a solid foothold in the PC market until Intel's Core 2 Duo could come along and put Intel technologically back in the lead. AMD hasn't had the money to effectively compete since then in part because Intel ensured that its bank accounts couldn't build up too far.

    --
    You can never go home again... but I guess you can shop there.
  11. Re:The AMD chip by Lisandro · · Score: 3, Informative

    I understand they're very popular on the embedded market due to their low cost, but i can't honestly tell why. Any half decent ARM platform will run circles around it.

  12. Re:i5, same thing? by radarskiy · · Score: 3, Informative

    i3, i5, and i7 represent "good", "better", and "best" respectively. That's it. A *particular* SKU with an i5 mark may have 4 physical cores, but 4 physical cores is not a requirement to receive the mark.
    For example, this i5 has 4 physical cores: http://ark.intel.com/products/... while this i5 has 2 physical cores http://ark.intel.com/products/...

  13. Re:blame windows not amd by cheater512 · · Score: 4, Informative

    Err except with HT there is one execution unit, and with AMD there are two.

    They are real cores, that share instruction decode and a FPU.
    Actual execution is parallel (unlike HT which is more interleaved).

    HT isn't similar to Bulldozer modules in any sense.

  14. Re:So AMD called their Hyperthreading a CPU core? by Anonymous Coward · · Score: 3, Informative

    Intel's cores since Nehalem have nothing of the sort. There's one set of ALUs, one FPU, one front-end, one each of L1i and L1d caches, and one peak of the memory hierarchy per core. However the front-end can decode two threads concurrently, tracking two sets of ISA regs at the same time, and sharing all resources between the two. But there are still ony one set of ALUs, and one FPU, per core.

    Intel gets more oomph per core this way. AMD merely took the other road, but their process tech was behind and their R&D hamstrung by budget cuts, so the things that would've made Bulldozer properly competitive only materialized in Piledriver, and then AMD was firmly in the "cheapo" tier already.

    The "pretend multicore" is a throwback to the first hyperthreaded Netburst family chips, where it was offered precisely as a substitute for AMD's genuine single-chip "SMP in a socket" multicore.

  15. Re:So AMD called their Hyperthreading a CPU core? by hairyfeet · · Score: 3, Informative

    Sigh, does nobody know how the BD/PD arch works here? It CAN share the FPU but absolutely does NOT "have to". Allow me to quote from Wikipedia: "."Two symmetrical 128-bit FMAC (fused multiplyâ"add capability) floating-point pipelines per module that can be unified into one large 256-bit-wide unit if one of the integer cores dispatches AVX instruction and two symmetrical x87/MMX/SSE capable FPPs for backward compatibility with SSE2 non-optimized software."

    So each core DOES have an FPU, they simply used a simpler 128bit FPU that CAN be joined together to make a single 256bit FPU for use with AVX instructions and ya know what? The majority of users will NEVER NOTICE as every program and game Joe Average runs will run great on an AMD chip. I myself run an FX-8320E which I upgraded from a Phenom II X6 (which according to the lawsuit is a "full" core compared to mine) and the FX blows through transcodes and multieffects layering a good 40% faster than the P II X6. And if his BS was true how does he explain the fact that the 6350 and 1100T are equal in performance despite the fact that according to him its a triple core versus a hexacore?

    --
    ACs don't waste your time replying, your posts are never seen by me.
  16. Re:i5, same thing? by fyngyrz · · Score: 4, Interesting

    Mod parent up. It is correct. Some i5's do have 2 cores. The original AC post near the top is also correct, which I notice the mods have knocked to -1 in the usual frenzy of "I disagree, although I am uninformed about the matter."

    For a couple decades, "core" meant CPU. 4004, 1802, 8080, 6800, 6809, Z80, 68000... etc.

    Then it meant CPU+MMU.

    What's funny is that "core" now seems to mean CPU+MMU+FPU (which is great... I love me an FPU per core.) But some (often aimed at mobile or tablets or phones) also have GPUs.

    So how long before we won't accept "core" except as a label for CPU+MMU+FPU+GPU?

    Then it might be "Nah, that thing has no NPU (neural processing unit), that's not a "real core": CPU+MMU+FPU+GPU+NPU

    Then perhaps it'll be "Nah, that thing has no QPU (quantum processing unit)", that's not a "real core": CPU+MMU+ FPU+GPU+NPU+QPU

    Then... well, I have no idea. But I do think it'll be something. It's always something. :)

    --
    I've fallen off your lawn, and I can't get up.