The K8 is here to stay

One of the most interesting points that we came away from our discussion of future AMD architectures was Weber's stance that the K8 execution core is as wide as they are going to go for quite some time.  Remember that the K8 execution core was taken from the K7, so it looks like the execution core that was originally introduced in the first Athlon will be with us even after the Athlon 64. 

What's even more interesting is that Intel's strategy appears to confirm that AMD's decision was indeed the right one. After all, it looks like the Pentium M architecture is eventually going to be adapted for the desktop in the coming years.  Based on the P6 execution core, the Pentium M is inherently quite similar (although also inferior) to the K7/K8 execution core that AMD has developed.  Given that Intel is slowly but surely implementing architectural features that AMD has done over the past few years, we wouldn't be too shocked to see an updated Pentium M execution core that was more competitive with the K7/K8 by the time that the Pentium M hits the desktop. 

Fred went on to say that for future microprocessors, he's not sure if the K8 core necessarily disappears and that in the long run, it could be that future microprocessors feature one or more K8 cores complemented by other cores.  Weber's comments outline a fundamental shift in the way that microprocessor generations are looked at.  In the past, the advent of a new microprocessor architecture meant that the outgoing architecture was retired - but now it looks as if outgoing architectures will be incorporated and complemented rather than put out to pasture.  The reason for this reuse instead of retire approach is simple - with less of a focus on increasing ILP, the role of optimizing the individual core decreases, and the problems turn into things like: how many cores can you stick on a die and what sort of resources do they share? 

In the past, new microprocessor architectures were sort of decoupled from new manufacturing processes.  You'd generally see a new architecture debut on whatever manufacturing process was out at the time and eventually scale down to smaller and smaller processes, allowing for more features (i.e. cache) and higher clock speeds.  In the era of multi-core, its the manufacturing process that really determines how many cores you can fit on a die and thus, the introduction of "new architectures" is very tightly coupled with smaller manufacturing processes.  We put new architectures in quotes because often times, the architectures won't be all that different on an individual core basis, but as an aggregate, we may see significant changes. 

How about a Hyper Threaded Athlon?

When Intel announced Hyper Threading, AMD wasn't (publicly) paying any attention at all to TLP as a means to increase overall performance.  But now that AMD is much more interested and more public about their TLP direction, we wondered if there was any room for SMT a la Hyper Threading in future AMD processors, potentially working within multi-core designs. 

Fred's response to this question was thankfully straightforward; he isn't a fan of Intel's Hyper Threading in the sense that the entire pipeline is shared between multiple threads. In Fred's words, "it's a misuse of resources."  However, Weber did mention that there's interest in sharing parts of multiple cores, such as two cores sharing a FPU to improve efficiency and reduce design complexity.  But things like sharing simple units just didn't make sense in Weber's world, and given the architecture with which he's working, we tend to agree. 

Weber’s Thoughts on Cell An Update on Turion and Final Words
Comments Locked

35 Comments

View All Comments

  • bersl2 - Thursday, March 31, 2005 - link

    #1: Thank you for the paralepsis.
  • Googer - Thursday, March 31, 2005 - link

    I have set up the OFFICIAL SOVIET RUSSIA thread in the forums section, so we can keep this garbage out of the news section.

    Let the bad humor fly here:

    http://forums.anandtech.com/messageview.aspx?catid...
  • oupei - Thursday, March 31, 2005 - link

    should be:

    "it's clear that sacrificing hardware complexity isn't a sacrifice that EITHER amd OR intel are (IS?) willing make"

    or

    "it's clear that sacrificing hardware complexity IS a sacrifice that neither amd nor intel are (IS?) willing make"

    or how about just writing a sentence that is easier to understand...
  • ksherman - Thursday, March 31, 2005 - link

    "It’s clear that sacrificing hardware complexity isn’t a sacrifice that neither AMD nor Intel are willing to make..."

    Or not so clear... what exactly does this mean?
  • Bonesdad - Thursday, March 31, 2005 - link

    I was going to say "first post" but i won't

Log in

Don't have an account? Sign up now