<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: UPDATE: AMD&#8217;s Fab38 and New York Fab4x are 22nm</title>
	<atom:link href="http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/</link>
	<description></description>
	<lastBuildDate>Thu, 09 Apr 2015 17:57:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.1.1</generator>
	<item>
		<title>By: Pasquale Uncapher</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10320</link>
		<dc:creator><![CDATA[Pasquale Uncapher]]></dc:creator>
		<pubDate>Tue, 30 Aug 2011 17:33:31 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10320</guid>
		<description><![CDATA[For a nice and identified by continue to be upward delayed looking through until Five or perhaps 5am. Rarely instead of for a short time now, but it surely includes transpired! Like it so much each time a website side handles a person a lot you have to try this!]]></description>
		<content:encoded><![CDATA[<p>For a nice and identified by continue to be upward delayed looking through until Five or perhaps 5am. Rarely instead of for a short time now, but it surely includes transpired! Like it so much each time a website side handles a person a lot you have to try this!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Theo Valich</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10319</link>
		<dc:creator><![CDATA[Theo Valich]]></dc:creator>
		<pubDate>Sun, 24 May 2009 22:59:05 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10319</guid>
		<description><![CDATA[Hi Mike,

here&#039;s a question. What would you rather have: Grumman and Airbus building tankers for US military and creating 50,000+ jobs in AL plus 30,000 in other states or American Boeing offshoring tens of thousands of jobs to Japan, Italy and other places?

If you want to put a nationalistic spin on it.... that is.

Regards,

Theo]]></description>
		<content:encoded><![CDATA[<p>Hi Mike,</p>
<p>here&#8217;s a question. What would you rather have: Grumman and Airbus building tankers for US military and creating 50,000+ jobs in AL plus 30,000 in other states or American Boeing offshoring tens of thousands of jobs to Japan, Italy and other places?</p>
<p>If you want to put a nationalistic spin on it&#8230;. that is.</p>
<p>Regards,</p>
<p>Theo</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10318</link>
		<dc:creator><![CDATA[mike]]></dc:creator>
		<pubDate>Fri, 22 May 2009 17:05:04 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10318</guid>
		<description><![CDATA[If they become arab, then im throwing them in the boycott bin with RIAA]]></description>
		<content:encoded><![CDATA[<p>If they become arab, then im throwing them in the boycott bin with RIAA</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Franzius</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10317</link>
		<dc:creator><![CDATA[Franzius]]></dc:creator>
		<pubDate>Thu, 05 Feb 2009 04:38:41 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10317</guid>
		<description><![CDATA[This is for Joe&#039;s peace of mind: native 22nm  means that the fab will start out producing 22nm wafers. Nothing more is to be inferred from Theo&#039;s wording. If you still have a hard time with what I am saying, just imagine how you would accurately describe the same implementation in a language other than your native tongue. GOT it?
Don&#039;t be dense and move off the point. We all understand your clarifications and really appreciate them. But, move one please.]]></description>
		<content:encoded><![CDATA[<p>This is for Joe&#8217;s peace of mind: native 22nm  means that the fab will start out producing 22nm wafers. Nothing more is to be inferred from Theo&#8217;s wording. If you still have a hard time with what I am saying, just imagine how you would accurately describe the same implementation in a language other than your native tongue. GOT it?<br />
Don&#8217;t be dense and move off the point. We all understand your clarifications and really appreciate them. But, move one please.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10316</link>
		<dc:creator><![CDATA[Joe]]></dc:creator>
		<pubDate>Wed, 04 Feb 2009 06:42:16 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10316</guid>
		<description><![CDATA[OK, I&#039;ll keep it civil (my apologies).

&quot;There were significant changes in the way how a fab is being designed and case is closed there. Ecological, space-wise, construction wise. That Fab is the first APM 4.0 Fab, so we’ll see how it will go.&quot;

The case is not closed - just because changes were made, doesn&#039;t make them unique or native or in anyway tied specifically to 22nm process technology.  My question: is any of this specific to 22nm to make F4X a &quot;native&quot; 22nm fab?  I&#039;m still trying to understand your original blog that the NY fab is a native 22m factory

Basically what I&#039;m asking is APM 4.0 specific to 22nm technology or is it more a matter of that technology being ready to be implemented when the fab happens to be starting up? (or  in other words if F4x turned out to be a 32nm fab for whatever reasons, would APM 4.0 not be implemented?). As for ecological, again I would like to understand how the improvements are specific to 22nm, or are they merely fab improvements that just happen to intercept the timing and are ready to implement in the NY fab?

I&#039;m not questioning that these improvement are real.  I&#039;m not questioning whether they will be done in the NY fab or whether that fab will be different.  I&#039;m questioning your characterization of the fab as &quot;native 22nm&quot; and implying (or perhaps I&#039;m just misreading), that something is  somehow unique or specifically designed to 22nm.  I would propose that these are merely technologies that are ready to go when the NY fab is being built and would have been implemented regardless of what technology node that fab would be running (and thus there is nothing &quot;native 22nm&quot; about the fab).  Do you disagree?

And yes I do think you were misleading your readers on the real fab capacity of AMD in 2012... perhaps I should not have punctuated it with an &quot;!&quot; and I certainly could have worded it more politely, but AMD&#039;s own foils contradict your assessment and frankly I&#039;m more inclined to trust the CEO of AMD&#039;s new foundry then your estimates.   This is not meant to be an attack, I just think AMD has a better understanding of it&#039;s capacity then you do.

They obviously could have  been wrong at the analyst day 2-3 months ago,  or plans could have been changed - but in the absence of any other data, I&#039;m not sure why AMD&#039;s presentation should be dismissed and your estimate is more accurate.  I would honestly like to hear why - do you have some knowledge, even if you can&#039;t share it, that their plans have changed since the Nov presentation?]]></description>
		<content:encoded><![CDATA[<p>OK, I&#8217;ll keep it civil (my apologies).</p>
<p>&#8220;There were significant changes in the way how a fab is being designed and case is closed there. Ecological, space-wise, construction wise. That Fab is the first APM 4.0 Fab, so we’ll see how it will go.&#8221;</p>
<p>The case is not closed &#8211; just because changes were made, doesn&#8217;t make them unique or native or in anyway tied specifically to 22nm process technology.  My question: is any of this specific to 22nm to make F4X a &#8220;native&#8221; 22nm fab?  I&#8217;m still trying to understand your original blog that the NY fab is a native 22m factory</p>
<p>Basically what I&#8217;m asking is APM 4.0 specific to 22nm technology or is it more a matter of that technology being ready to be implemented when the fab happens to be starting up? (or  in other words if F4x turned out to be a 32nm fab for whatever reasons, would APM 4.0 not be implemented?). As for ecological, again I would like to understand how the improvements are specific to 22nm, or are they merely fab improvements that just happen to intercept the timing and are ready to implement in the NY fab?</p>
<p>I&#8217;m not questioning that these improvement are real.  I&#8217;m not questioning whether they will be done in the NY fab or whether that fab will be different.  I&#8217;m questioning your characterization of the fab as &#8220;native 22nm&#8221; and implying (or perhaps I&#8217;m just misreading), that something is  somehow unique or specifically designed to 22nm.  I would propose that these are merely technologies that are ready to go when the NY fab is being built and would have been implemented regardless of what technology node that fab would be running (and thus there is nothing &#8220;native 22nm&#8221; about the fab).  Do you disagree?</p>
<p>And yes I do think you were misleading your readers on the real fab capacity of AMD in 2012&#8230; perhaps I should not have punctuated it with an &#8220;!&#8221; and I certainly could have worded it more politely, but AMD&#8217;s own foils contradict your assessment and frankly I&#8217;m more inclined to trust the CEO of AMD&#8217;s new foundry then your estimates.   This is not meant to be an attack, I just think AMD has a better understanding of it&#8217;s capacity then you do.</p>
<p>They obviously could have  been wrong at the analyst day 2-3 months ago,  or plans could have been changed &#8211; but in the absence of any other data, I&#8217;m not sure why AMD&#8217;s presentation should be dismissed and your estimate is more accurate.  I would honestly like to hear why &#8211; do you have some knowledge, even if you can&#8217;t share it, that their plans have changed since the Nov presentation?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: theovalich</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10315</link>
		<dc:creator><![CDATA[theovalich]]></dc:creator>
		<pubDate>Wed, 04 Feb 2009 03:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10315</guid>
		<description><![CDATA[RE: Daniel.

According to AMD&#039;s roadmaps, first 32nm (first 32nm is bulk, followed by SOI HKMG) chip will be Radeon GPU (tapeout in late 09, rollout in 2010).

2009 will see 2nd wave of 45nm CPUs, probably a new and improved revision (D?) and this includes chipset side (800 series should be built in 45nm instead of 55nm).

AMD&#039;s 32nm CPU&#039;s won&#039;t be ready before Computex 2010. Yes, K10 architecture will see 32nm parts, unless Bulldozer pulls a small miracle and comes out six-months to one full year early.]]></description>
		<content:encoded><![CDATA[<p>RE: Daniel.</p>
<p>According to AMD&#8217;s roadmaps, first 32nm (first 32nm is bulk, followed by SOI HKMG) chip will be Radeon GPU (tapeout in late 09, rollout in 2010).</p>
<p>2009 will see 2nd wave of 45nm CPUs, probably a new and improved revision (D?) and this includes chipset side (800 series should be built in 45nm instead of 55nm).</p>
<p>AMD&#8217;s 32nm CPU&#8217;s won&#8217;t be ready before Computex 2010. Yes, K10 architecture will see 32nm parts, unless Bulldozer pulls a small miracle and comes out six-months to one full year early.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: theovalich</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10314</link>
		<dc:creator><![CDATA[theovalich]]></dc:creator>
		<pubDate>Wed, 04 Feb 2009 03:37:46 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10314</guid>
		<description><![CDATA[Like I wrote before, writing news pieces at 2AM isn&#039;t my greatest strength. When it comes to analyst day foils, you can take them as you like, that&#039;s why I disclosed them.

Everybody is entitled to his own opinion. I listened to every AMD&#039;s quarterly since July &#039;05, and I have my notes. In those notes, AMD produced large number of discrepancies and quite honestly, wrong information. The company wasn&#039;t honest about the reasons for the 65nm delay (it wasn&#039;t technical), why 90nm was improved and what were the issues with 45nm ($$$ for tools). Can AMD pull it through on the 22nm node?

In Joe&#039;s interesting dissection of my article and comments afterwards, I was called quite interesting names, thus I&#039;ll refrain from further discussion. The fact that I did not delete his posts means I am leaving them as &quot;food for thought&quot;, but I am not going to address them until their MO is changed to a decent level of communication.

Again, I will not go into discussion with the person that stated this: &quot;Stop misleading the readers and making this sound like some novel approach to 22nm or fab design!&quot;

Without knowing what were the topics of my discussions on the subject of NY Fab were (I don&#039;t exactly recall how I mentioned or assumed that AMD is making something&quot;novel&quot;). There were significant changes in the way how a fab is being designed and case is closed there. Ecological, space-wise, construction wise. That Fab is the first APM 4.0 Fab, so we&#039;ll see how it will go.

Unless real fab architects wants to disclose building plans and provisions in a public forum or via e-mail, there is nothing to discuss. Upcoming site will feature some interesting interviews, so I&#039;ll leave the room for real experts on the subject.]]></description>
		<content:encoded><![CDATA[<p>Like I wrote before, writing news pieces at 2AM isn&#8217;t my greatest strength. When it comes to analyst day foils, you can take them as you like, that&#8217;s why I disclosed them.</p>
<p>Everybody is entitled to his own opinion. I listened to every AMD&#8217;s quarterly since July &#8217;05, and I have my notes. In those notes, AMD produced large number of discrepancies and quite honestly, wrong information. The company wasn&#8217;t honest about the reasons for the 65nm delay (it wasn&#8217;t technical), why 90nm was improved and what were the issues with 45nm ($$$ for tools). Can AMD pull it through on the 22nm node?</p>
<p>In Joe&#8217;s interesting dissection of my article and comments afterwards, I was called quite interesting names, thus I&#8217;ll refrain from further discussion. The fact that I did not delete his posts means I am leaving them as &#8220;food for thought&#8221;, but I am not going to address them until their MO is changed to a decent level of communication.</p>
<p>Again, I will not go into discussion with the person that stated this: &#8220;Stop misleading the readers and making this sound like some novel approach to 22nm or fab design!&#8221;</p>
<p>Without knowing what were the topics of my discussions on the subject of NY Fab were (I don&#8217;t exactly recall how I mentioned or assumed that AMD is making something&#8221;novel&#8221;). There were significant changes in the way how a fab is being designed and case is closed there. Ecological, space-wise, construction wise. That Fab is the first APM 4.0 Fab, so we&#8217;ll see how it will go.</p>
<p>Unless real fab architects wants to disclose building plans and provisions in a public forum or via e-mail, there is nothing to discuss. Upcoming site will feature some interesting interviews, so I&#8217;ll leave the room for real experts on the subject.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel de França MTd2</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10313</link>
		<dc:creator><![CDATA[Daniel de França MTd2]]></dc:creator>
		<pubDate>Wed, 04 Feb 2009 03:33:40 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10313</guid>
		<description><![CDATA[Hi Theo,

There are 3 different processes for 32nm, and just the low powered one is ready for an early 2010. The other 2 can just yield chips in the second semester, which is a bit late.]]></description>
		<content:encoded><![CDATA[<p>Hi Theo,</p>
<p>There are 3 different processes for 32nm, and just the low powered one is ready for an early 2010. The other 2 can just yield chips in the second semester, which is a bit late.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10312</link>
		<dc:creator><![CDATA[Frank]]></dc:creator>
		<pubDate>Wed, 04 Feb 2009 03:27:36 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10312</guid>
		<description><![CDATA[&quot;When it comes to revision numbers, don’t think that C revision is going to stay around forever&quot;

Sorry - wasn&#039;t suggesting you were responsible for the table (or brought it up)- some other commenter asked how real it might be.  I think given the table has a &quot;C4&quot; revision in Q4&#039;10 shows how authentic (or inauthentic) it is.  It appears whoever made the table just made up the revisions #&#039;s and if they made that up, along with a change in the clock scheme moving to increments of 5 in the model #, suggests the table is more about hope and extrapolation as opposed to some inside knowledge.

Theo - you didn&#039;t comment about Joe&#039;s link about the AMD analyst day foils.   It seems he brought up some reasonable information which contradict some of your comments and some of your analysis about overall AMD capacity capability in the original article.  I have to agree almost everything you assume is the absolute best case and some of your assumptions on ramp rates of a factory are not reasonable (using the ramp of a 200mm fab on a known technology nodet o project the ramp of a 300mm fab on a new technology node is not reasonable as there are significant differences)]]></description>
		<content:encoded><![CDATA[<p>&#8220;When it comes to revision numbers, don’t think that C revision is going to stay around forever&#8221;</p>
<p>Sorry &#8211; wasn&#8217;t suggesting you were responsible for the table (or brought it up)- some other commenter asked how real it might be.  I think given the table has a &#8220;C4&#8243; revision in Q4&#8217;10 shows how authentic (or inauthentic) it is.  It appears whoever made the table just made up the revisions #&#8217;s and if they made that up, along with a change in the clock scheme moving to increments of 5 in the model #, suggests the table is more about hope and extrapolation as opposed to some inside knowledge.</p>
<p>Theo &#8211; you didn&#8217;t comment about Joe&#8217;s link about the AMD analyst day foils.   It seems he brought up some reasonable information which contradict some of your comments and some of your analysis about overall AMD capacity capability in the original article.  I have to agree almost everything you assume is the absolute best case and some of your assumptions on ramp rates of a factory are not reasonable (using the ramp of a 200mm fab on a known technology nodet o project the ramp of a 300mm fab on a new technology node is not reasonable as there are significant differences)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: theovalich</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10311</link>
		<dc:creator><![CDATA[theovalich]]></dc:creator>
		<pubDate>Wed, 04 Feb 2009 03:00:57 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10311</guid>
		<description><![CDATA[That table is a rumor and I don&#039;t see a single reference in my story to it (I&#039;ve only seen it today).
Plus, I don&#039;t see AMD executing in that direction. High-end CPU introduction is tied to the platform plus marketing event such as back-to-school, Thanksgiving, Christmas etc.

When it comes to revision numbers, don&#039;t think that C revision is going to stay around forever. AMD introduced different revisions under the same product family and manufacturing process in the past.

I have given my view on 3.1/3.3 and 3.5/3.6 as maximums that AMD can reach on air. My assumption on 3.5-4.0 GHz on air in 2010 is tied to the introduction of 32nm HKMG SiGe process over at AMD, and of course, that is if K10.5 receives a die-shrink, rather than some architectural changes.

Personally, AMD needs to look somewhere else for performance boost, and that &quot;somewhere else&quot; is the fact that their CPU cores work asymmetrically to the MemCtr/L3 cache. That is the battle AMD is facing and main reason why their CPUs are not exactly... that great. Async cache is way to performance doomsday, and that was proven in the past, present and the future.

When it comes to manufacturing debate, I think I will refrain from finishing articles at 2-3AM and publishing them, since during re-read I am noticing that I wasn&#039;t as clear as I wanted to be. E.g. think one thing, write another.

To be perfectly clear, I know how manufacturing process is measured (50% of DRAM cell pitch, half-side pitch etc.), but there is certain thing called allowances. During my visit to Fab30/36 complex in 2006, we were explained that by working hard on optimizing the 90nm process, with VP of Manufacturing bragging that the engineers managed to bring the spacing close to 65nm specifications (it was explicitly mentioned what lengths were allowed by 65nm and 90nm definitiions and Fab36 was able to pull 65nm-like values on 90nm process, 13th generation transistor. 9th Gen transistor was the base for 65nm process... and again, these statements are taken out of context).

And yes, spacing doesn&#039;t dictate speed/performance. But it is interesting that discussion about Fabs turned into &quot;Phenom II kicking 3.5G this year&quot;. Kinda didn&#039;t noticed when it turned into that direction.

Well, I only have time for this blog in the evenings, given that during the day I am occupied with the preparations for the launch of the new site.]]></description>
		<content:encoded><![CDATA[<p>That table is a rumor and I don&#8217;t see a single reference in my story to it (I&#8217;ve only seen it today).<br />
Plus, I don&#8217;t see AMD executing in that direction. High-end CPU introduction is tied to the platform plus marketing event such as back-to-school, Thanksgiving, Christmas etc.</p>
<p>When it comes to revision numbers, don&#8217;t think that C revision is going to stay around forever. AMD introduced different revisions under the same product family and manufacturing process in the past.</p>
<p>I have given my view on 3.1/3.3 and 3.5/3.6 as maximums that AMD can reach on air. My assumption on 3.5-4.0 GHz on air in 2010 is tied to the introduction of 32nm HKMG SiGe process over at AMD, and of course, that is if K10.5 receives a die-shrink, rather than some architectural changes.</p>
<p>Personally, AMD needs to look somewhere else for performance boost, and that &#8220;somewhere else&#8221; is the fact that their CPU cores work asymmetrically to the MemCtr/L3 cache. That is the battle AMD is facing and main reason why their CPUs are not exactly&#8230; that great. Async cache is way to performance doomsday, and that was proven in the past, present and the future.</p>
<p>When it comes to manufacturing debate, I think I will refrain from finishing articles at 2-3AM and publishing them, since during re-read I am noticing that I wasn&#8217;t as clear as I wanted to be. E.g. think one thing, write another.</p>
<p>To be perfectly clear, I know how manufacturing process is measured (50% of DRAM cell pitch, half-side pitch etc.), but there is certain thing called allowances. During my visit to Fab30/36 complex in 2006, we were explained that by working hard on optimizing the 90nm process, with VP of Manufacturing bragging that the engineers managed to bring the spacing close to 65nm specifications (it was explicitly mentioned what lengths were allowed by 65nm and 90nm definitiions and Fab36 was able to pull 65nm-like values on 90nm process, 13th generation transistor. 9th Gen transistor was the base for 65nm process&#8230; and again, these statements are taken out of context).</p>
<p>And yes, spacing doesn&#8217;t dictate speed/performance. But it is interesting that discussion about Fabs turned into &#8220;Phenom II kicking 3.5G this year&#8221;. Kinda didn&#8217;t noticed when it turned into that direction.</p>
<p>Well, I only have time for this blog in the evenings, given that during the day I am occupied with the preparations for the launch of the new site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10310</link>
		<dc:creator><![CDATA[Frank]]></dc:creator>
		<pubDate>Wed, 04 Feb 2009 02:28:26 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10310</guid>
		<description><![CDATA[&quot;9×0 vs 9×5 is difference between AM2 and AM3.&quot;

That&#039;s my point... the table seems to have extrapolated clock speeds by seeing how many #&#039;s can we get from 940/945 to 995.  To maximize the clock gains, increments of 5 were used, which goes against AMD&#039;s current naming convention (a jump of 10 is 100MHz for the X4 PII).

And I&#039;m not doubting AMD process improvements - I&#039;m doubting the rather suspect (and I believe made up) use of  C3, C4 revisions in the table.  As even you noted, a # change on a revision is often a design change whereas a significant process improvement would likely have a revision with a letter change.  I think the table is just a made up extrapolation from someone, based on these 2 items.

The other inherent assumption is there is nothing on the architecture preventing the clock gains.  There may be critical speed paths other than the transistor, which limit speed.  Simply being able to overclock doesnot mean these speedpaths are addressable for stock products (we have seen this on Intel products as well).  So for those saying - well I can OC to 3.6-3.8GHz on reasonable voltages, therefore we should eventually see these stock parts over time, it doesn&#039;t hold.

Theo - the spacing between transistors has nothing to do with the name of the technology node (90nm doesn&#039;t mean 90nm spacing between transistors).  Nor does the spacing between transistors dictate speed/performance.]]></description>
		<content:encoded><![CDATA[<p>&#8220;9×0 vs 9×5 is difference between AM2 and AM3.&#8221;</p>
<p>That&#8217;s my point&#8230; the table seems to have extrapolated clock speeds by seeing how many #&#8217;s can we get from 940/945 to 995.  To maximize the clock gains, increments of 5 were used, which goes against AMD&#8217;s current naming convention (a jump of 10 is 100MHz for the X4 PII).</p>
<p>And I&#8217;m not doubting AMD process improvements &#8211; I&#8217;m doubting the rather suspect (and I believe made up) use of  C3, C4 revisions in the table.  As even you noted, a # change on a revision is often a design change whereas a significant process improvement would likely have a revision with a letter change.  I think the table is just a made up extrapolation from someone, based on these 2 items.</p>
<p>The other inherent assumption is there is nothing on the architecture preventing the clock gains.  There may be critical speed paths other than the transistor, which limit speed.  Simply being able to overclock doesnot mean these speedpaths are addressable for stock products (we have seen this on Intel products as well).  So for those saying &#8211; well I can OC to 3.6-3.8GHz on reasonable voltages, therefore we should eventually see these stock parts over time, it doesn&#8217;t hold.</p>
<p>Theo &#8211; the spacing between transistors has nothing to do with the name of the technology node (90nm doesn&#8217;t mean 90nm spacing between transistors).  Nor does the spacing between transistors dictate speed/performance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: theovalich</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10309</link>
		<dc:creator><![CDATA[theovalich]]></dc:creator>
		<pubDate>Wed, 04 Feb 2009 01:30:35 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10309</guid>
		<description><![CDATA[RE: Daniel de França: Hi Daniel. I&#039;ve seen the AMD roadmap for 2009 and sadly, I cannot find the document anymore. Probably was located on that RAID5 array that went bust last week.

AMD launched Dragon platform in two waves, with AM2+ and soon-to-launch AM3 processors. Dragon is combination of AM2+ or AM3 processor, 790 series chipset and 55nm GPUs (Radeon 4800). Second platform to launch in 2009 is Leo, with AM3 processors, 890 chipset and 40nm GPUs (Radeon 5800). Launch of Leo platform will be in tune with AM3 Black Edition processors of higher clocks that are planned for February.

The table clearly stated 3.2, 3.4 GHz in Q2&#039;09. With the apperance of 3.1 GHz processor, all of a sudden there is talk about 3.5 GHz. I am expecting that AMD will launch 3.1 and 3.3 GHz for Leo platform. By the end of the year, we should see 3.5 and 3.6 GHz.

Phyton platform is based on 900-series chipsets, but you won&#039;t see that before 2010. Phyton was supposed to launch in conjuction with M-SPACE processors (e.g. Bulldozer), but with Bulldozer now stuck in 2011, two-years off target, I suspect that you will see 3.5-4.0 GHz processors in 2010.

RE: Frank - Frank, AMD improves its manufacturing process in &quot;generations&quot;. For instance, 90nm process lived through four generations (and ended up with 70nm spacing between transistors), 65nm had just two &quot;generations&quot;. It is too early to say what&#039;s going on with 45nm, but I heard some promising step ups and they already went through two &quot;generations&quot;.

This should enable those miracle cores of the past (Winchester etc.), e.g. optimized design. Barcelona really wasn&#039;t a good example, since it was broken in B0, B1 and B2 silicon, so they had to fix it for B3.

9x0 vs 9x5 is difference between AM2 and AM3. IMO, that was nothing else but &quot;we have to launch Dragon at CES&quot; move, since Dragon platform (DDR3) is three months late (Oct 08 anyone?). Thus, 920 and 940 came to life.

I don&#039;t see any viable reason for those two to exist other than &quot;we could not make DDR3 platform on time&quot;, since all AM3 CPUs should be compatible with AM2/AM2+ motherboards.]]></description>
		<content:encoded><![CDATA[<p>RE: Daniel de França: Hi Daniel. I&#8217;ve seen the AMD roadmap for 2009 and sadly, I cannot find the document anymore. Probably was located on that RAID5 array that went bust last week.</p>
<p>AMD launched Dragon platform in two waves, with AM2+ and soon-to-launch AM3 processors. Dragon is combination of AM2+ or AM3 processor, 790 series chipset and 55nm GPUs (Radeon 4800). Second platform to launch in 2009 is Leo, with AM3 processors, 890 chipset and 40nm GPUs (Radeon 5800). Launch of Leo platform will be in tune with AM3 Black Edition processors of higher clocks that are planned for February.</p>
<p>The table clearly stated 3.2, 3.4 GHz in Q2&#8217;09. With the apperance of 3.1 GHz processor, all of a sudden there is talk about 3.5 GHz. I am expecting that AMD will launch 3.1 and 3.3 GHz for Leo platform. By the end of the year, we should see 3.5 and 3.6 GHz.</p>
<p>Phyton platform is based on 900-series chipsets, but you won&#8217;t see that before 2010. Phyton was supposed to launch in conjuction with M-SPACE processors (e.g. Bulldozer), but with Bulldozer now stuck in 2011, two-years off target, I suspect that you will see 3.5-4.0 GHz processors in 2010.</p>
<p>RE: Frank &#8211; Frank, AMD improves its manufacturing process in &#8220;generations&#8221;. For instance, 90nm process lived through four generations (and ended up with 70nm spacing between transistors), 65nm had just two &#8220;generations&#8221;. It is too early to say what&#8217;s going on with 45nm, but I heard some promising step ups and they already went through two &#8220;generations&#8221;.</p>
<p>This should enable those miracle cores of the past (Winchester etc.), e.g. optimized design. Barcelona really wasn&#8217;t a good example, since it was broken in B0, B1 and B2 silicon, so they had to fix it for B3.</p>
<p>9&#215;0 vs 9&#215;5 is difference between AM2 and AM3. IMO, that was nothing else but &#8220;we have to launch Dragon at CES&#8221; move, since Dragon platform (DDR3) is three months late (Oct 08 anyone?). Thus, 920 and 940 came to life.</p>
<p>I don&#8217;t see any viable reason for those two to exist other than &#8220;we could not make DDR3 platform on time&#8221;, since all AM3 CPUs should be compatible with AM2/AM2+ motherboards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10308</link>
		<dc:creator><![CDATA[Frank]]></dc:creator>
		<pubDate>Wed, 04 Feb 2009 00:59:09 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10308</guid>
		<description><![CDATA[Look at the TDP&#039;s and the revision #&#039;s - this looks more like someone simply extrapolating.   To increase 1 GHz, you will likely need some significant process improvements and would see the stepping move from C2 to Dx or Ex...  A move from C2 to C3 to C4 is more likely a minor process rev or a layout/design change (B2-B3 on Barcy).

I assume the revision #&#039;s have been put in the chart for a reason?  If they have, then making up the revision # (which appears to be the case) or putting in placeholders, calls into question the veracity of this table.

Does the perfect spacing of 0.1GHz per quarter for 5 consecutive quarters also seem a little suspect?

Finally, wasn&#039;t amd using the 9x0 vs 9x5 numbering scheme to denote AM2+ vs AM3 models for the PII X4? Or is the table just suggesting they abandon that after the 940?]]></description>
		<content:encoded><![CDATA[<p>Look at the TDP&#8217;s and the revision #&#8217;s &#8211; this looks more like someone simply extrapolating.   To increase 1 GHz, you will likely need some significant process improvements and would see the stepping move from C2 to Dx or Ex&#8230;  A move from C2 to C3 to C4 is more likely a minor process rev or a layout/design change (B2-B3 on Barcy).</p>
<p>I assume the revision #&#8217;s have been put in the chart for a reason?  If they have, then making up the revision # (which appears to be the case) or putting in placeholders, calls into question the veracity of this table.</p>
<p>Does the perfect spacing of 0.1GHz per quarter for 5 consecutive quarters also seem a little suspect?</p>
<p>Finally, wasn&#8217;t amd using the 9&#215;0 vs 9&#215;5 numbering scheme to denote AM2+ vs AM3 models for the PII X4? Or is the table just suggesting they abandon that after the 940?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel de França MTd2</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10307</link>
		<dc:creator><![CDATA[Daniel de França MTd2]]></dc:creator>
		<pubDate>Wed, 04 Feb 2009 00:02:42 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10307</guid>
		<description><![CDATA[Hi Theo, are you aware of these rumors?

I listed them in the first post of this forum.

http://www.amdzone.com/phpbb3/viewtopic.php?f=52&amp;t=136040

Both of them agree on 3.5GHz in 2009.

So, AMD&#039;s desktop CPU&#039;s are totaly lost in 2010? Or do you think they can achieve 4GHz?]]></description>
		<content:encoded><![CDATA[<p>Hi Theo, are you aware of these rumors?</p>
<p>I listed them in the first post of this forum.</p>
<p><a href="http://www.amdzone.com/phpbb3/viewtopic.php?f=52&#038;t=136040" rel="nofollow">http://www.amdzone.com/phpbb3/viewtopic.php?f=52&#038;t=136040</a></p>
<p>Both of them agree on 3.5GHz in 2009.</p>
<p>So, AMD&#8217;s desktop CPU&#8217;s are totaly lost in 2010? Or do you think they can achieve 4GHz?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10306</link>
		<dc:creator><![CDATA[Joe]]></dc:creator>
		<pubDate>Tue, 03 Feb 2009 23:27:05 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10306</guid>
		<description><![CDATA[http://www.amd.com/us-en/assets/content_type/DownloadableAssets/The_Foundry_Company_AMD_2008_Analyst_Day_Breakout_11-13-08.pdf

See page 16 from Doug Grose and the capacity plans.  Some things of note:

2012 show MINIMAL capacity from the NY fab... eyeballing it, it looks like 20-25% built out  (This debunks your myth of full build out in year if it is starting up late 2011 or early 2012)

2012 total wafer starts is ~650,000 wafers, or just over 50,000 wafers/month (This debunks your myth of 75K WSPM and your estimate was just under 1 million in 2012)

Note - this is the same presentation that contains the slides you CHOSE to present in your blog article... either you chose not to read the whole thing, were separately given some of the slides by whoever your sources are, or you deliberately omitted the stuff that conflicts with your &quot;analysis&quot;.

In any event, are things clearer now?]]></description>
		<content:encoded><![CDATA[<p><a href="http://www.amd.com/us-en/assets/content_type/DownloadableAssets/The_Foundry_Company_AMD_2008_Analyst_Day_Breakout_11-13-08.pdf" rel="nofollow">http://www.amd.com/us-en/assets/content_type/DownloadableAssets/The_Foundry_Company_AMD_2008_Analyst_Day_Breakout_11-13-08.pdf</a></p>
<p>See page 16 from Doug Grose and the capacity plans.  Some things of note:</p>
<p>2012 show MINIMAL capacity from the NY fab&#8230; eyeballing it, it looks like 20-25% built out  (This debunks your myth of full build out in year if it is starting up late 2011 or early 2012)</p>
<p>2012 total wafer starts is ~650,000 wafers, or just over 50,000 wafers/month (This debunks your myth of 75K WSPM and your estimate was just under 1 million in 2012)</p>
<p>Note &#8211; this is the same presentation that contains the slides you CHOSE to present in your blog article&#8230; either you chose not to read the whole thing, were separately given some of the slides by whoever your sources are, or you deliberately omitted the stuff that conflicts with your &#8220;analysis&#8221;.</p>
<p>In any event, are things clearer now?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10305</link>
		<dc:creator><![CDATA[Joe]]></dc:creator>
		<pubDate>Tue, 03 Feb 2009 23:12:01 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10305</guid>
		<description><![CDATA[&quot;Thus, NY Fab has provisions for optional usage of SOI - SiGE - High-K dielectrics, and this requires more fab space. At least, that’s how it was explained to me. NY Fab is a customer fab.&quot;

You need to stop interpreting things... a fab is not &#039;natively&#039; designed to handle SiGe or HIGH K or whatever... this merely means different tools, chemical are used in the fab.  Whoever &quot;explained it to you&quot; is exploiting your lack of knowledge.  The fab is a fab.... it can accept a high K tool or a SiO2 or a tool that can handle SOI wafers (which by the way is any 300mm tool).

What you are essentially saying is they are reserving some &#039;swing&#039; space (sorry this is an industry term essentially meaning fungible or extra space)....  there is nothing &quot;designed&quot; into the fab.  This is simply basic fab and capacity planning that goes on at TSMC, Intel or any other fab in the world.  Stop misleading the readers and making this sound like some novel approach to 22nm or fab design!

And for you to simply count # of fabs saying intel needs 14 to supply 80% and AMD needs 1 for 20% is completely insane.  Does AMD produce chipsets in house?  Do they produce wireless chips?  Do they produce memory (NOR)?  Are the fab sizes all equivalent in terms of capacity and wafer sizes? (No)  Do you consider Chartered contribution to capacity for AMD?  Have you factored in relative die size of the products? How about the relative mix of quad core vs dual core vs single core?

Me thinks you are simply trying to justify AMD, not present any sort of knowledgeable or objective form of analysis.  If I want that I&#039;ll go to AMDzone.

&quot;It happened before (Fab30), it can happen again.&quot;

Fab 30 was 200mm, those tools install quicker, qualify quicker and oh by the way that was done on a process that was already qualified and certified (where as the NY fab apparently will be the first 22nm process startup for AMD).  Additionally the cycle time on lots for that process flow is different from today (meaning today they take longer to move through the fab, which lengthens tool qualification time, process certification times and thue ramp speed).  You using F30 as justification for a &lt;1 year ramp is all anyone needs to know about your level of knowledge of this industry.

I appreciate your sources and don&#039;t doubt them, but honestly you do not appear to have the background to analyze them correctly and are producing wrong or flawed conclusions.

Finally your designed for 20K got tro 30K is nice, but that is clearly taken from the AMD analyst days and I&#039;m not sure if you understand how they did it.  The move from 20K to 25 K was real and very good (though a 25% increase in capacit is not unheard for a factory over it&#039;s lifetime as tools get improved over time and run faster, have better availability/utilization, etc.  The final move from ~25K to 30K was largely done by stuffing support equipment into the F36 shell.  While I applaud AMD for doing this and it was a very creative and highly useful solution, it is not something &quot;special&quot; or even sustainable - they were able to do it because F36 was not built out, not because of some remarkable design or F30.  If AMD built an annex onto the side of the fab they could accomplish a similar thing - though I probably wouldn&#039;t call it soemthing special about the original Fab, I&#039;d call it using additional space.]]></description>
		<content:encoded><![CDATA[<p>&#8220;Thus, NY Fab has provisions for optional usage of SOI &#8211; SiGE &#8211; High-K dielectrics, and this requires more fab space. At least, that’s how it was explained to me. NY Fab is a customer fab.&#8221;</p>
<p>You need to stop interpreting things&#8230; a fab is not &#8216;natively&#8217; designed to handle SiGe or HIGH K or whatever&#8230; this merely means different tools, chemical are used in the fab.  Whoever &#8220;explained it to you&#8221; is exploiting your lack of knowledge.  The fab is a fab&#8230;. it can accept a high K tool or a SiO2 or a tool that can handle SOI wafers (which by the way is any 300mm tool).</p>
<p>What you are essentially saying is they are reserving some &#8216;swing&#8217; space (sorry this is an industry term essentially meaning fungible or extra space)&#8230;.  there is nothing &#8220;designed&#8221; into the fab.  This is simply basic fab and capacity planning that goes on at TSMC, Intel or any other fab in the world.  Stop misleading the readers and making this sound like some novel approach to 22nm or fab design!</p>
<p>And for you to simply count # of fabs saying intel needs 14 to supply 80% and AMD needs 1 for 20% is completely insane.  Does AMD produce chipsets in house?  Do they produce wireless chips?  Do they produce memory (NOR)?  Are the fab sizes all equivalent in terms of capacity and wafer sizes? (No)  Do you consider Chartered contribution to capacity for AMD?  Have you factored in relative die size of the products? How about the relative mix of quad core vs dual core vs single core?</p>
<p>Me thinks you are simply trying to justify AMD, not present any sort of knowledgeable or objective form of analysis.  If I want that I&#8217;ll go to AMDzone.</p>
<p>&#8220;It happened before (Fab30), it can happen again.&#8221;</p>
<p>Fab 30 was 200mm, those tools install quicker, qualify quicker and oh by the way that was done on a process that was already qualified and certified (where as the NY fab apparently will be the first 22nm process startup for AMD).  Additionally the cycle time on lots for that process flow is different from today (meaning today they take longer to move through the fab, which lengthens tool qualification time, process certification times and thue ramp speed).  You using F30 as justification for a &lt;1 year ramp is all anyone needs to know about your level of knowledge of this industry.</p>
<p>I appreciate your sources and don&#8217;t doubt them, but honestly you do not appear to have the background to analyze them correctly and are producing wrong or flawed conclusions.</p>
<p>Finally your designed for 20K got tro 30K is nice, but that is clearly taken from the AMD analyst days and I&#8217;m not sure if you understand how they did it.  The move from 20K to 25 K was real and very good (though a 25% increase in capacit is not unheard for a factory over it&#8217;s lifetime as tools get improved over time and run faster, have better availability/utilization, etc.  The final move from ~25K to 30K was largely done by stuffing support equipment into the F36 shell.  While I applaud AMD for doing this and it was a very creative and highly useful solution, it is not something &#8220;special&#8221; or even sustainable &#8211; they were able to do it because F36 was not built out, not because of some remarkable design or F30.  If AMD built an annex onto the side of the fab they could accomplish a similar thing &#8211; though I probably wouldn&#8217;t call it soemthing special about the original Fab, I&#8217;d call it using additional space.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: theovalich</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10304</link>
		<dc:creator><![CDATA[theovalich]]></dc:creator>
		<pubDate>Tue, 03 Feb 2009 22:14:38 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10304</guid>
		<description><![CDATA[Pardon for not being clear enough - my fault. I can&#039;t see AMD releasing ONLY 3.5 GHz model, but a set of processors working at different clockspeeds.

But in all honesty, when 32nm Westmere comes along, AMD will have a tough time.

The company management made their architectural decisions, they were wrong and they now need to live until K11 comes along with completely new architecture. So, Sandy Bridge vs. Bulldozer and Bobcat.]]></description>
		<content:encoded><![CDATA[<p>Pardon for not being clear enough &#8211; my fault. I can&#8217;t see AMD releasing ONLY 3.5 GHz model, but a set of processors working at different clockspeeds.</p>
<p>But in all honesty, when 32nm Westmere comes along, AMD will have a tough time.</p>
<p>The company management made their architectural decisions, they were wrong and they now need to live until K11 comes along with completely new architecture. So, Sandy Bridge vs. Bulldozer and Bobcat.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel de França MTd2</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10303</link>
		<dc:creator><![CDATA[Daniel de França MTd2]]></dc:creator>
		<pubDate>Tue, 03 Feb 2009 18:27:31 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10303</guid>
		<description><![CDATA[I don&#039;t get it. You say you can&#039;t see it AMD releasing AMD at 3.5 GHz but say it is logical to say to estimate that they release at that frequency... What do you mean?]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t get it. You say you can&#8217;t see it AMD releasing AMD at 3.5 GHz but say it is logical to say to estimate that they release at that frequency&#8230; What do you mean?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Theo Valich</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10302</link>
		<dc:creator><![CDATA[Theo Valich]]></dc:creator>
		<pubDate>Tue, 03 Feb 2009 17:48:18 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10302</guid>
		<description><![CDATA[Well, I don&#039;t see AMD releasing PII at 3.5 GHz. It is logical to estimate that AMD will release 3.1 GHz, 3.2, 3.3, 3.4, 3.5 and 3.6 GHz models.

Not sure what sense it will make, but AMD is definitely planning to launch higher-clocked CPUs. They will introduce new models as they improve the manufacturing process, and keep the higher clocks in their 95/125W TDP envelopes.]]></description>
		<content:encoded><![CDATA[<p>Well, I don&#8217;t see AMD releasing PII at 3.5 GHz. It is logical to estimate that AMD will release 3.1 GHz, 3.2, 3.3, 3.4, 3.5 and 3.6 GHz models.</p>
<p>Not sure what sense it will make, but AMD is definitely planning to launch higher-clocked CPUs. They will introduce new models as they improve the manufacturing process, and keep the higher clocks in their 95/125W TDP envelopes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel de França MTd2</title>
		<link>http://www.vrworld.com/2009/02/02/amds-fab38-and-new-york-fab4x-are-22nm/#comment-10301</link>
		<dc:creator><![CDATA[Daniel de França MTd2]]></dc:creator>
		<pubDate>Tue, 03 Feb 2009 17:01:21 +0000</pubDate>
		<guid isPermaLink="false">http://theovalich.wordpress.com/?p=1020#comment-10301</guid>
		<description><![CDATA[Do you think releasing PhII @ 3.5GHz is enough to compete against Intel in the CPU market until 2011?]]></description>
		<content:encoded><![CDATA[<p>Do you think releasing PhII @ 3.5GHz is enough to compete against Intel in the CPU market until 2011?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Content Delivery Network via Amazon Web Services: CloudFront: cdn.vrworld.com

 Served from: www.vrworld.com @ 2015-04-10 14:46:02 by W3 Total Cache -->