<?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: The processor works</title>
	<atom:link href="http://mitsuba-renderer.org/~wenzel/blog/2007/06/the-processor-works/feed/" rel="self" type="application/rss+xml" />
	<link>http://mitsuba-renderer.org/~wenzel/blog/2007/06/the-processor-works/</link>
	<description></description>
	<lastBuildDate>Sat, 22 Oct 2011 02:52:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=393</generator>
	<item>
		<title>By: Wenzel Jakob</title>
		<link>http://mitsuba-renderer.org/~wenzel/blog/2007/06/the-processor-works/#comment-69</link>
		<dc:creator><![CDATA[Wenzel Jakob]]></dc:creator>
		<pubDate>Sun, 17 Jun 2007 07:11:25 +0000</pubDate>
		<guid isPermaLink="false">http://wazlaf.org/wordpress/?p=97#comment-69</guid>
		<description><![CDATA[The cause is the built-in cache: Before a kd-Tree-Node or Triangle can be used by the intersection processor, it first has to be loaded from DDR memory into the 1024-line direct mapped cache (48 KB). This takes several cycles and the intersection processor uses a special mechanism so that it doesn&#039;t wait for the data but instead continues with the next thread at once (The cache can be simultaneously acessed by multiple readers/writers). Later, it checks again whether the data has been loaded. The problem occurred when the 3D scene was larger than the cache and a cache line had to be replaced. In this case, the cache generated invalid signals for several cycles which put the intersection hardware into an invalid state.]]></description>
		<content:encoded><![CDATA[<p>The cause is the built-in cache: Before a kd-Tree-Node or Triangle can be used by the intersection processor, it first has to be loaded from DDR memory into the 1024-line direct mapped cache (48 KB). This takes several cycles and the intersection processor uses a special mechanism so that it doesn&#8217;t wait for the data but instead continues with the next thread at once (The cache can be simultaneously acessed by multiple readers/writers). Later, it checks again whether the data has been loaded. The problem occurred when the 3D scene was larger than the cache and a cache line had to be replaced. In this case, the cache generated invalid signals for several cycles which put the intersection hardware into an invalid state.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joachim Breitner</title>
		<link>http://mitsuba-renderer.org/~wenzel/blog/2007/06/the-processor-works/#comment-66</link>
		<dc:creator><![CDATA[Joachim Breitner]]></dc:creator>
		<pubDate>Sat, 16 Jun 2007 21:38:34 +0000</pubDate>
		<guid isPermaLink="false">http://wazlaf.org/wordpress/?p=97#comment-66</guid>
		<description><![CDATA[Can you explain the cause of the error, or is it not understandable by the general geek public?]]></description>
		<content:encoded><![CDATA[<p>Can you explain the cause of the error, or is it not understandable by the general geek public?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
