Mark Papermaster, CTO at Advanced Micro Devices, gave the keynote address at the Hot Chips 24 conference in Cupertino today. Papermaster's mission was ostensibly to talk about heterogeneous computing, a drum that the chip peddler has been banging on since last fall. But the real news was that Papermaster divulged some of the …
What does ''emergency schedule handling'' mean
As in ''The integer scheduler will sport better emergency schedule handling'' ???
Re: What does ''emergency schedule handling'' mean
I think this is where the execution queue handler has to be either flushed or interrupted and higher priority instructions than the existing items in the queue executed instead. For example, when a high priority hardware interrupt is triggered it needs to use the processor resources with low latency rather than waiting around for a lower level process to complete.
It used to be "simple" when the persistent process chip state was just a few registers - add a higher number of registers, such as those in the non-core specialist functions, and execution queuing and things get "interesting".
AMD seems to be refining the cores and processes to where they should have been when BD was released. If Piledriver and Steamroller provide the 15% projected performance goal then AMD is back on track and sales will grow significantly. Trinity was a great performance bump so AMD has learned a few things.
The problem is the consumer lines have been pushing sales as of late since the business market is skittish about the economy, and the simple fact is unless you take Windows 8, already shaping up to be one of the most hated Microsoft OSes since WinME, then you are SOL when it comes to anything based on the Bulldozer module design, and this is coming from someone who has built nothing but AMD for years and is typing this on a Thuban.
The problem is every version of Windows OTHER than Windows 8 has a scheduler that treats the BD module as TWO cores, this is wrong. What it is actually is more like a single core with hardware assisted hyperthreading thanks to only having half the FP, why is this bad? Lets say you have two heavy loads..the SMART way to execute on a BD module would be one load on module1/2 and the other on 3/4, that way each load would have its own FP unit. What you will get in any Windows OTHER than Windows 8 is that Windows will schedule BOTH loads on 1/2, which means they are fighting over a single FP unit and the whole thing just drags. This is why in many tests with Win 7 a Thuban or Deneb will beat a BD with the same amount of cores, sometimes even beating BD chips with MORE cores.
Frankly this is a server chip that NEVER should have been released on the desktop, desktop loads are more and more multimedia which is FP city which is exactly what BD is worst at. Instead what they should have done is kept Thuban and Liano for the desktop while working on a new design, pushed out a new Brazos quad for mobile, and kept the BD/PD design for servers where most loads are integer and not FP heavy.
As someone who has been building and selling AMD systems exclusively as well as having my entire family on AMD if they haven't come up with a better design by the time I run out of AM3+ chips I'll have no choice but go Intel, my customers and I are skipping win 8 and there simply is no selling point for BD on Win 7.
- SMASH the Bash bug! Apple and Red Hat scramble for patch batches
- BENDY iPhone 6, you say? Pah, warp claims are bent out of shape: Consumer Reports
- NASA rover Curiosity drills HOLE in MARS 'GOLF COURSE'
- WHY did Sunday Mirror stoop to slurping selfies for smut sting?
- Business is back, baby! Hasta la VISTA, Win 8... Oh, yeah, Windows 9