<?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"
	>
<channel>
	<title>Comments for The Official RapidMind Blog</title>
	<atom:link href="http://blogs.rapidmind.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.rapidmind.com</link>
	<description>The vision of parallel programming for multi-core architectures.</description>
	<pubDate>Wed, 23 Jul 2008 19:20:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>Comment on Multi-Threading: The Nitrogen Narcosis of Programming by Stefanus Du Toit</title>
		<link>http://blogs.rapidmind.com/2008/06/05/multi-threading-the-nitrogen-narcosis-of-programming/#comment-104</link>
		<dc:creator>Stefanus Du Toit</dc:creator>
		<pubDate>Mon, 16 Jun 2008 15:43:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rapidmind.com/?p=19#comment-104</guid>
		<description>Hi Dmitriy,

Your best bet is to contact sales@rapidmind.com -- they'll work with you to figure out if RapidMind meets your needs.

Thanks,

Stefanus</description>
		<content:encoded><![CDATA[<p>Hi Dmitriy,</p>
<p>Your best bet is to contact <a href="mailto:sales@rapidmind.com">sales@rapidmind.com</a> &#8212; they&#8217;ll work with you to figure out if RapidMind meets your needs.</p>
<p>Thanks,</p>
<p>Stefanus</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Multi-Threading: The Nitrogen Narcosis of Programming by DMITRIY V'jukov</title>
		<link>http://blogs.rapidmind.com/2008/06/05/multi-threading-the-nitrogen-narcosis-of-programming/#comment-100</link>
		<dc:creator>DMITRIY V'jukov</dc:creator>
		<pubDate>Thu, 12 Jun 2008 23:05:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rapidmind.com/?p=19#comment-100</guid>
		<description>Currently I am developing multi-threaded network routing server. Yeah, it's multi-threaded. And I am doing parallelization and memory management manually. I am curious whether RapidMind can help me to eliminate multi-threading, manual parallelization amd memory management from my server?</description>
		<content:encoded><![CDATA[<p>Currently I am developing multi-threaded network routing server. Yeah, it&#8217;s multi-threaded. And I am doing parallelization and memory management manually. I am curious whether RapidMind can help me to eliminate multi-threading, manual parallelization amd memory management from my server?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The difference between multi-core and multi-processing by Stefanus Du Toit</title>
		<link>http://blogs.rapidmind.com/2008/04/17/the-difference-between-multi-core-and-multi-processing/#comment-82</link>
		<dc:creator>Stefanus Du Toit</dc:creator>
		<pubDate>Mon, 02 Jun 2008 20:02:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rapidmind.com/?p=16#comment-82</guid>
		<description>Anonymous: Absolutely - I didn't mean to imply anything at all about heterogeneous vs homogeneous architectures in my posting (apart from pointing out that the "S" in "SMP" implies homogeneous processors at some level). Heterogeneous processor designs are an interesting alternative to homogeneous designs, and we're likely to see more of them in the future. Exactly what kind of processor architecture will "win out" in the next decade isn't clear yet.

All of my points apply to heterogeneous computing, maybe even moreso. Software must adapt to multi-core to keep scaling in performance. If heterogeneous cores become commonplace, software will have to adopt to these as well. Our platform already targets heterogeneous designs such as the Cell Broadband Engine and combinations of CPUs and GPUs today, and our aim is to make it possible to write code that scales well "no matter what crazy hardware you throw at it" :) - multi-core, many-core, homogeneous, heterogeneous, you name it.</description>
		<content:encoded><![CDATA[<p>Anonymous: Absolutely - I didn&#8217;t mean to imply anything at all about heterogeneous vs homogeneous architectures in my posting (apart from pointing out that the &#8220;S&#8221; in &#8220;SMP&#8221; implies homogeneous processors at some level). Heterogeneous processor designs are an interesting alternative to homogeneous designs, and we&#8217;re likely to see more of them in the future. Exactly what kind of processor architecture will &#8220;win out&#8221; in the next decade isn&#8217;t clear yet.</p>
<p>All of my points apply to heterogeneous computing, maybe even moreso. Software must adapt to multi-core to keep scaling in performance. If heterogeneous cores become commonplace, software will have to adopt to these as well. Our platform already targets heterogeneous designs such as the Cell Broadband Engine and combinations of CPUs and GPUs today, and our aim is to make it possible to write code that scales well &#8220;no matter what crazy hardware you throw at it&#8221; :) - multi-core, many-core, homogeneous, heterogeneous, you name it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The difference between multi-core and multi-processing by Anonymous</title>
		<link>http://blogs.rapidmind.com/2008/04/17/the-difference-between-multi-core-and-multi-processing/#comment-79</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 30 May 2008 15:57:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rapidmind.com/?p=16#comment-79</guid>
		<description>I agree with you on the basic idea of your post: today's performance gains only through multi-core computing. However, the idea of having 100-1000 identical cores in the future seems to be highly improbable. Let's analyse it: In the year X set in future, let there be a processor with 1000 identical cores. Now let's replace e.g. 10 of these cores with specialized cores. Why? Because let us suppose that it gives certain applications (call them 'A') used in the year X a big speed boost. Other applications now have to run at most at 99% of their original speed [= (1000-10)/1000]. Who cares that those other applications run at 99% speed when applications 'A' run let's say 5% faster? Nobody. Therefore, homogeneous multi-core systems are in fact a transitory stage in the evolution of computing, the final stage being processors and systems with the right mixture of *computing blocks*. Complexity will win.</description>
		<content:encoded><![CDATA[<p>I agree with you on the basic idea of your post: today&#8217;s performance gains only through multi-core computing. However, the idea of having 100-1000 identical cores in the future seems to be highly improbable. Let&#8217;s analyse it: In the year X set in future, let there be a processor with 1000 identical cores. Now let&#8217;s replace e.g. 10 of these cores with specialized cores. Why? Because let us suppose that it gives certain applications (call them &#8216;A&#8217;) used in the year X a big speed boost. Other applications now have to run at most at 99% of their original speed [= (1000-10)/1000]. Who cares that those other applications run at 99% speed when applications &#8216;A&#8217; run let&#8217;s say 5% faster? Nobody. Therefore, homogeneous multi-core systems are in fact a transitory stage in the evolution of computing, the final stage being processors and systems with the right mixture of *computing blocks*. Complexity will win.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why the Future isn&#8217;t Flat by dmitriy v'jukov</title>
		<link>http://blogs.rapidmind.com/2008/04/23/why-the-future-isnt-flat/#comment-9</link>
		<dc:creator>dmitriy v'jukov</dc:creator>
		<pubDate>Wed, 30 Apr 2008 21:05:27 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rapidmind.com/?p=17#comment-9</guid>
		<description>Interesting post. Looking forward to other similar posts. I've already bookmarked the page ;)</description>
		<content:encoded><![CDATA[<p>Interesting post. Looking forward to other similar posts. I&#8217;ve already bookmarked the page ;)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
