Isn't experience and fine tuning on new nodes something that AMD is good at though? No doubt we'll likely see slightly lower clocks with Steamroller given that it's a new process given that GF's 32nm SOI process is probably quite mature, but that doesn't mean 28nm bulk is going to mean <3ghz processing levels. That'd be a nightmare of a press release...
You know what is a nightmare? Finding numbers that fit into 998.4 and 1049.x. (x being 5 to 9)
Server parts go by base frequency and desktop parts go by boost frequency.
Berlin: 998.4 GFlops
Kaveri: 1049.9 GFlops
Opteron 6386 SE = 179.2 GFlops ÷ 140 Watts = 1.28 GFlops * 7.8x improvement = 9.984 GFlops/Watt * 100 Watts = 998.4
So, far for Berlin which was REALLY EASY to do:
CPU: 2.4 GHz
GPU: 0.9 GHz
(2.4 GHz * 2 Modules * 16 Flops)->76.8
+
(0.9 GHz * 512 ALUs * 2 Flops)->921.6
= 998.4 GFlops
So, for the base clocks for Kaveri/Berlin it must be 2.4 GHz for CPU and 0.9 GHz for GPU.
Knowing that in the PDF slides GFlops for Llano/Trinity/Richland/Kaveri is heavily rounded. I set out for the boost clocks and ultimately failed! So, here is a really bull explanation why I think the GPU clock is what it is.
Trinity - 800 MHz
Richland - 844 MHz
Berlin GPU Base - 900 MHz
Berlin GPU Boost - 944 MHz
Yep, only an 100+ MHz boost and the expectation the GPU may actually have boost clock.
Kaveri Base: 2.4 GHz CPU/0.9 GHz GPU -> 998.4 GFlops
Kaveri Boost: 2.6 GHz CPU/0.944 GHz GPU -> 1049.9 GFlops
https://semiaccurate.com/assets/uploads/2013/06/AMD-Berlin-Slide.png
^-- what I am basing everything on.
I'm 100% certain that the GFlops/Watt calculation is dealing with SPEC2006, not theoretical max GFlops.