itsmydamnation
Platinum Member
- Feb 6, 2011
- 2,907
- 3,517
- 136
<br />
<br />
Hey itsmydammnation, do you think that the biggest part of Zen IPC increase come from beefing up the excution engine per core(like adding two ALUs and doubling the per core FPU)?
yes and no....lol
The idea of race to sleep/stall is an important one so more INT ALU is a good thing and in high ILP scenarios AMD probably was/is at a large disadvantage to intel right now.
Given that AMD moved some instructions from ALU to AGU from bulldozer->piledriver is a good indication that con cores are ALU limited. The idea that 30-50% of x86 instructions contain address gen(execution + address gen) yet bulldozer is 2ALU:2AGU also points that way.
FP being 4 wide will be interesting, most "normal" FP code (written by code monkey) is float, double etc not SIMD, So having 4 low latency execution units should be good for that race to stall idea. it is more complex then that as x86 uses x87 for these and x64 uses SSE so we will have to wait and see how much focus amd give x86/x87.
On the flip side i guess i hope AMD can reduce misspredict and the misspredict penalty which even from piledriver to excavator are better ( on the assumption a uop cache hit reduces pipeline length) then bulldozer. Given Zen is targeting a lower clock rate the pipeline length will be interesting to see.
But i think the cache system will be the really critical thing we don't know anything about it yet. latency, inclusive/exclusive ( something horrible in the middle like bulldozer ) is it a ring, a mesh, some sort of "fabric" how does it work across silicon imposer etc.
as a layman i think what we know about Zen (mainly from the compiler patch) looks good, i think we will see stuff from both the cat and con cores used as the base of which Zen is built on but i really think the uncore will be the linchpin. get that right and all is good, get that wrong :'( ........