{"id":1966,"date":"2009-11-13T13:51:54","date_gmt":"2009-11-13T17:51:54","guid":{"rendered":"http:\/\/www.schollnick.net\/wordpress\/?p=1966"},"modified":"2009-11-13T13:52:03","modified_gmt":"2009-11-13T17:52:03","slug":"amd-avoiding-larrabee-route-on-road-to-cpugpu-fusion","status":"publish","type":"post","link":"http:\/\/www.schollnick.net\/wordpress\/2009\/11\/amd-avoiding-larrabee-route-on-road-to-cpugpu-fusion\/","title":{"rendered":"AMD avoiding Larrabee route on road to CPU\/GPU &#8220;Fusion&#8221;"},"content":{"rendered":"<p>Ars Technica&#8217;s Jon Stokes discusses what he has learned about AMD&#8217;s new &#8220;Fusion&#8221; CPU \/ GPU designs&#8230;<\/p>\n<blockquote><p>My immediate reaction on hearing Moore describe this was that AMD was planning to pursue the Larrabee route, and replace the GPU with a pool of small x86 cores. Obviously, you have to expose this &#8216;GPU&#8217; hardware (in whatever form) to the OS as x86 hardware, so you&#8217;d do this by either making it actual x86 hardware or by doing binary translation. But Moore&#8217;s answer to a subsequent question along these lines made it clear that AMD sees the cost of replicating x86 front-end decode hardware across multiple small cores as too steep; instead, the company will more &#8216;tightly integrate&#8217; the math hardware into the CPU core.<\/p><\/blockquote>\n<p>(<a href=\"http:\/\/arstechnica.com\/hardware\/news\/2009\/11\/amd-avoiding-larrabee-route-on-road-to-cpugpu-fusion.ars?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=rss\">View the rest of the article at ARS Technica &#8211; AMD avoiding Larrabee route on road to CPU\/GPU &#8220;Fusion&#8221;<\/a>)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Ars Technica&#8217;s Jon Stokes discusses what he has learned about AMD&#8217;s new &#8220;Fusion&#8221; CPU \/ GPU designs&#8230; My immediate reaction on hearing Moore describe this was that AMD was planning to pursue the Larrabee route, and replace the GPU with a pool of small x86 cores. Obviously, you have to expose this &#8216;GPU&#8217; hardware (in <a class=\"read-more\" href=\"http:\/\/www.schollnick.net\/wordpress\/2009\/11\/amd-avoiding-larrabee-route-on-road-to-cpugpu-fusion\/\">[&hellip;]<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0},"categories":[12,23],"tags":[265,123,212],"_links":{"self":[{"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/posts\/1966"}],"collection":[{"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/comments?post=1966"}],"version-history":[{"count":0,"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/posts\/1966\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/media?parent=1966"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/categories?post=1966"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/tags?post=1966"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<!-- WP Super Cache is installed but broken. The constant WPCACHEHOME must be set in the file wp-config.php and point at the WP Super Cache plugin directory. -->