<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: The Multicore Kerfuffle and a Dose of Reality</title>
	<link>http://marknelson.us/2007/07/30/multicore-panic/</link>
	<description>Programming, mostly.</description>
	<pubDate>Tue, 09 Mar 2010 22:27:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: GuB</title>
		<link>http://marknelson.us/2007/07/30/multicore-panic/#comment-310256</link>
		<dc:creator>GuB</dc:creator>
		<pubDate>Fri, 17 Jul 2009 17:49:08 +0000</pubDate>
		<guid>http://marknelson.us/2007/07/30/multicore-panic/#comment-310256</guid>
		<description>The bottleneck of parallel computing is usually IO, including memory access. It cannot be solved by just adding cores.
And for computationally intensive tasks, the massively parallel approach is already there, see GPUs...</description>
		<content:encoded><![CDATA[<p>The bottleneck of parallel computing is usually IO, including memory access. It cannot be solved by just adding cores.<br />
And for computationally intensive tasks, the massively parallel approach is already there, see GPUs&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ernst</title>
		<link>http://marknelson.us/2007/07/30/multicore-panic/#comment-278591</link>
		<dc:creator>Ernst</dc:creator>
		<pubDate>Sun, 22 Feb 2009 11:05:48 +0000</pubDate>
		<guid>http://marknelson.us/2007/07/30/multicore-panic/#comment-278591</guid>
		<description>That was an interesting read.  My first time reading this thread.

 As a man that has worked with C I'm finding my AMD Quad core very nice.
 Nice to task and not worry; however, writing C programs that access all that the system can spare isn't straight forward.
 I'll be giving this topic thought as I see programming for multi-core  CPU's is in my direct future.
 I am in favor of Multi-core it's just that 50 GHZ cores are what I dream of today.
 
 Hey when I was a boy the idea of VHS was a dream.  What Movies at home?  LOL
 SO where are those 10 GHZ cores I read about a while back; some place?

Ernst</description>
		<content:encoded><![CDATA[<p>That was an interesting read.  My first time reading this thread.</p>
<p> As a man that has worked with C I&#8217;m finding my AMD Quad core very nice.<br />
 Nice to task and not worry; however, writing C programs that access all that the system can spare isn&#8217;t straight forward.<br />
 I&#8217;ll be giving this topic thought as I see programming for multi-core  CPU&#8217;s is in my direct future.<br />
 I am in favor of Multi-core it&#8217;s just that 50 GHZ cores are what I dream of today.</p>
<p> Hey when I was a boy the idea of VHS was a dream.  What Movies at home?  LOL<br />
 SO where are those 10 GHZ cores I read about a while back; some place?</p>
<p>Ernst</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Random Walk of Life &#187; Blog Archive &#187; I highly recommend this one</title>
		<link>http://marknelson.us/2007/07/30/multicore-panic/#comment-264245</link>
		<dc:creator>Random Walk of Life &#187; Blog Archive &#187; I highly recommend this one</dc:creator>
		<pubDate>Sat, 17 Jan 2009 14:36:16 +0000</pubDate>
		<guid>http://marknelson.us/2007/07/30/multicore-panic/#comment-264245</guid>
		<description>[...] a flaw in vain, I am kind of exhausted. And very impressed. RCU is twisted, yet so simple. I read elsewhere, that maybe the human mind wasn&#8217;t cut out for designing parallel algorithms. We tend to think [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] a flaw in vain, I am kind of exhausted. And very impressed. RCU is twisted, yet so simple. I read elsewhere, that maybe the human mind wasn&#8217;t cut out for designing parallel algorithms. We tend to think [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Intel® Software Network Blogs &#187; A Multi-Core Future – Two view from the community.</title>
		<link>http://marknelson.us/2007/07/30/multicore-panic/#comment-52103</link>
		<dc:creator>Intel® Software Network Blogs &#187; A Multi-Core Future – Two view from the community.</dc:creator>
		<pubDate>Tue, 11 Dec 2007 18:55:22 +0000</pubDate>
		<guid>http://marknelson.us/2007/07/30/multicore-panic/#comment-52103</guid>
		<description>[...] does not appear that everyone is developing applications that take advantage of multi-core systems. Mark Nelson wrote a great analysis of the current state of the multi-core revolutions. He has some interesting views of Intel and AMDs [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] does not appear that everyone is developing applications that take advantage of multi-core systems. Mark Nelson wrote a great analysis of the current state of the multi-core revolutions. He has some interesting views of Intel and AMDs [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Observations from Uppsala &#187; Blog Archive &#187; Mark Nelson&#8217;s Multicore Non-Panic and Embedded Systems</title>
		<link>http://marknelson.us/2007/07/30/multicore-panic/#comment-50925</link>
		<dc:creator>Observations from Uppsala &#187; Blog Archive &#187; Mark Nelson&#8217;s Multicore Non-Panic and Embedded Systems</dc:creator>
		<pubDate>Fri, 07 Dec 2007 20:44:50 +0000</pubDate>
		<guid>http://marknelson.us/2007/07/30/multicore-panic/#comment-50925</guid>
		<description>[...] about the actual non-imminence of the end of the computing world as we know it due to multicore.  Written by Mark Nelson, the article makes some relevant and mostly correct claims, as long as we keep to the desktop land that he knows best.  So here is a look at these claims in [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] about the actual non-imminence of the end of the computing world as we know it due to multicore.  Written by Mark Nelson, the article makes some relevant and mostly correct claims, as long as we keep to the desktop land that he knows best.  So here is a look at these claims in [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xupaxupa</title>
		<link>http://marknelson.us/2007/07/30/multicore-panic/#comment-47667</link>
		<dc:creator>Xupaxupa</dc:creator>
		<pubDate>Thu, 22 Nov 2007 10:08:35 +0000</pubDate>
		<guid>http://marknelson.us/2007/07/30/multicore-panic/#comment-47667</guid>
		<description>@Mark:

Ok, I understand your point. Let me just add that my problem with the article was that reading it, the feeling one gets is that instead of panic, we should not worry at all, and that eventually the problem will sort out by itself (when both are untrue). By "we", I mean the people who work in the software industry.

(as a side-note, I'm running right now a VHDL synthesis that's already occupied 14 hours of CPU time and I don't know when will it finish. And I'm still waiting for multi-core support for these tools.)</description>
		<content:encoded><![CDATA[<p>@Mark:</p>
<p>Ok, I understand your point. Let me just add that my problem with the article was that reading it, the feeling one gets is that instead of panic, we should not worry at all, and that eventually the problem will sort out by itself (when both are untrue). By &#8220;we&#8221;, I mean the people who work in the software industry.</p>
<p>(as a side-note, I&#8217;m running right now a VHDL synthesis that&#8217;s already occupied 14 hours of CPU time and I don&#8217;t know when will it finish. And I&#8217;m still waiting for multi-core support for these tools.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://marknelson.us/2007/07/30/multicore-panic/#comment-47380</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Wed, 21 Nov 2007 15:07:43 +0000</pubDate>
		<guid>http://marknelson.us/2007/07/30/multicore-panic/#comment-47380</guid>
		<description>@Xupaxupa:

No argument with what you say, my article is trying to distinguish between the words &lt;i&gt;panic&lt;/i&gt; and &lt;i&gt;problem&lt;/i&gt;. I just think we should be using the latter, not the former.</description>
		<content:encoded><![CDATA[<p>@Xupaxupa:</p>
<p>No argument with what you say, my article is trying to distinguish between the words <i>panic</i> and <i>problem</i>. I just think we should be using the latter, not the former.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xupaxupa</title>
		<link>http://marknelson.us/2007/07/30/multicore-panic/#comment-47377</link>
		<dc:creator>Xupaxupa</dc:creator>
		<pubDate>Wed, 21 Nov 2007 14:59:42 +0000</pubDate>
		<guid>http://marknelson.us/2007/07/30/multicore-panic/#comment-47377</guid>
		<description>Hey,

the panic about multi-core is all about single program performance: before, you knew your program would execute faster in a new processor. Now, that hardly is true.

Even if your point is about desktop users, and how more cores will bring a better experience, the truth is that a 3Ghz single-core play games faster than a newer dual-core. Because game designers didn't make it to work multi-core? Undoubtedly, but also because it is HARD to parallelize code (in a safe way, at least). 

And that's it. So the panic is not about how to use the cores, is how to speed-up single programs with the cores (within reasonable effort).</description>
		<content:encoded><![CDATA[<p>Hey,</p>
<p>the panic about multi-core is all about single program performance: before, you knew your program would execute faster in a new processor. Now, that hardly is true.</p>
<p>Even if your point is about desktop users, and how more cores will bring a better experience, the truth is that a 3Ghz single-core play games faster than a newer dual-core. Because game designers didn&#8217;t make it to work multi-core? Undoubtedly, but also because it is HARD to parallelize code (in a safe way, at least). </p>
<p>And that&#8217;s it. So the panic is not about how to use the cores, is how to speed-up single programs with the cores (within reasonable effort).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fascinating Computer Science</title>
		<link>http://marknelson.us/2007/07/30/multicore-panic/#comment-37953</link>
		<dc:creator>Fascinating Computer Science</dc:creator>
		<pubDate>Fri, 05 Oct 2007 17:24:52 +0000</pubDate>
		<guid>http://marknelson.us/2007/07/30/multicore-panic/#comment-37953</guid>
		<description>&lt;strong&gt;Future Programming—Art or Engineering?...&lt;/strong&gt;

The emergence of multicore computer systems—ranging from portable and desktop computers to petascale supercomputers—is placing new demands on computer software, and is catalyzing a reexamination of the fundamental methods of computer programming.
W...</description>
		<content:encoded><![CDATA[<p><strong>Future Programming—Art or Engineering?&#8230;</strong></p>
<p>The emergence of multicore computer systems—ranging from portable and desktop computers to petascale supercomputers—is placing new demands on computer software, and is catalyzing a reexamination of the fundamental methods of computer programming.<br />
W&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Startup Signal - Today&#8217;s Top Blog Posts on Entrepreneurship - Powered by SocialRank</title>
		<link>http://marknelson.us/2007/07/30/multicore-panic/#comment-37289</link>
		<dc:creator>Startup Signal - Today&#8217;s Top Blog Posts on Entrepreneurship - Powered by SocialRank</dc:creator>
		<pubDate>Mon, 01 Oct 2007 10:23:46 +0000</pubDate>
		<guid>http://marknelson.us/2007/07/30/multicore-panic/#comment-37289</guid>
		<description>[...] The Multicore Kerfuffle and a Dose of Reality [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] The Multicore Kerfuffle and a Dose of Reality [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
