<?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: Q&amp;A with SiCortex co-founder Matt Reilly on what happened, and what it means for HPC</title>
	<atom:link href="http://insidehpc.com/2009/06/05/qa-with-sicortex-co-founder-matt-reilly-on-what-happened-and-what-it-means-for-hpc/feed/" rel="self" type="application/rss+xml" />
	<link>http://insidehpc.com/2009/06/05/qa-with-sicortex-co-founder-matt-reilly-on-what-happened-and-what-it-means-for-hpc/</link>
	<description>HPC News Without the Noise for Supercomputing Professionals &#124; insideHPC</description>
	<lastBuildDate>Sun, 19 May 2013 10:46:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Sicortex: two mysteries. &#171; US Patent Appl. 12213303: Comentarios.</title>
		<link>http://insidehpc.com/2009/06/05/qa-with-sicortex-co-founder-matt-reilly-on-what-happened-and-what-it-means-for-hpc/#comment-289580</link>
		<dc:creator>Sicortex: two mysteries. &#171; US Patent Appl. 12213303: Comentarios.</dc:creator>
		<pubDate>Mon, 03 Jan 2011 12:40:18 +0000</pubDate>
		<guid isPermaLink="false">http://insidehpc.com/?p=5418#comment-289580</guid>
		<description>[...] and growing), they had to shutdown  operations middle 2009. More data about Sicortex shutdown at: http://insidehpc.com/2009/06/05/qa-with-sicortex-co-founder-matt-reilly-on-what-happened-and-what-it... and http://www.theregister.co.uk/2009/05/28/sicortex_assets/ and [...]</description>
		<content:encoded><![CDATA[<p>[...] and growing), they had to shutdown  operations middle 2009. More data about Sicortex shutdown at: <a href="http://insidehpc.com/2009/06/05/qa-with-sicortex-co-founder-matt-reilly-on-what-happened-and-what-it... and" rel="nofollow">http://insidehpc.com/2009/06/05/qa-with-sicortex-co-founder-matt-reilly-on-what-happened-and-what-it&#8230; and</a> <a href="http://www.theregister.co.uk/2009/05/28/sicortex_assets/ and" rel="nofollow">http://www.theregister.co.uk/2009/05/28/sicortex_assets/ and</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Parallel computing / Supercomputing IV. Global Industrial Organization. &#171; US Patent Appl. 12213303: Comentarios.</title>
		<link>http://insidehpc.com/2009/06/05/qa-with-sicortex-co-founder-matt-reilly-on-what-happened-and-what-it-means-for-hpc/#comment-289323</link>
		<dc:creator>Parallel computing / Supercomputing IV. Global Industrial Organization. &#171; US Patent Appl. 12213303: Comentarios.</dc:creator>
		<pubDate>Sun, 02 Jan 2011 22:14:22 +0000</pubDate>
		<guid isPermaLink="false">http://insidehpc.com/?p=5418#comment-289323</guid>
		<description>[...] More data at: http://insidehpc.com/2009/06/05/qa-with-sicortex-co-founder-matt-reilly-on-what-happened-and-what-it... and http://www.theregister.co.uk/2009/05/28/sicortex_assets/.  Very interesting, the interview at [...]</description>
		<content:encoded><![CDATA[<p>[...] More data at: <a href="http://insidehpc.com/2009/06/05/qa-with-sicortex-co-founder-matt-reilly-on-what-happened-and-what-it... and" rel="nofollow">http://insidehpc.com/2009/06/05/qa-with-sicortex-co-founder-matt-reilly-on-what-happened-and-what-it&#8230; and</a> <a href="http://www.theregister.co.uk/2009/05/28/sicortex_assets/. " rel="nofollow">http://www.theregister.co.uk/2009/05/28/sicortex_assets/. </a> Very interesting, the interview at [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John West</title>
		<link>http://insidehpc.com/2009/06/05/qa-with-sicortex-co-founder-matt-reilly-on-what-happened-and-what-it-means-for-hpc/#comment-168474</link>
		<dc:creator>John West</dc:creator>
		<pubDate>Fri, 05 Jun 2009 14:42:35 +0000</pubDate>
		<guid isPermaLink="false">http://insidehpc.com/?p=5418#comment-168474</guid>
		<description>Jim - yes, you and several people made great observations on that LinkedIn thread I started that were most helpful in gauging the general sentiment about SiCortex. I&#039;m very grateful for your insight.</description>
		<content:encoded><![CDATA[<p>Jim &#8211; yes, you and several people made great observations on that LinkedIn thread I started that were most helpful in gauging the general sentiment about SiCortex. I&#8217;m very grateful for your insight.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Tuccillo</title>
		<link>http://insidehpc.com/2009/06/05/qa-with-sicortex-co-founder-matt-reilly-on-what-happened-and-what-it-means-for-hpc/#comment-168470</link>
		<dc:creator>Jim Tuccillo</dc:creator>
		<pubDate>Fri, 05 Jun 2009 13:40:58 +0000</pubDate>
		<guid isPermaLink="false">http://insidehpc.com/?p=5418#comment-168470</guid>
		<description>I think you may have quoted a few of my comments from LinkedIn. You make a good point about comparing Intel 5400 series processors instead of 5500 series (aka Nehalem). In that case the difference is only about 4x on the per core STREAM number assuming you have the right chip set - there are some slower Intel chip sets. The SiCortex clock crank may have shrunk that number. Clearly, stride-1 access isn&#039;t the only issue but I don&#039;t have a feel for the memory latency so I can&#039;t comment on that. The issue with design cycles really comes down to the fact that Intel/AMD seem to have something significant to release every 2 years. The same time frame applies, by and large, to IB fabrics, perhaps 3 years for DDR to QDR?</description>
		<content:encoded><![CDATA[<p>I think you may have quoted a few of my comments from LinkedIn. You make a good point about comparing Intel 5400 series processors instead of 5500 series (aka Nehalem). In that case the difference is only about 4x on the per core STREAM number assuming you have the right chip set &#8211; there are some slower Intel chip sets. The SiCortex clock crank may have shrunk that number. Clearly, stride-1 access isn&#8217;t the only issue but I don&#8217;t have a feel for the memory latency so I can&#8217;t comment on that. The issue with design cycles really comes down to the fact that Intel/AMD seem to have something significant to release every 2 years. The same time frame applies, by and large, to IB fabrics, perhaps 3 years for DDR to QDR?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
