<?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: Transactional memory pros and cons from ACM Queue</title>
	<atom:link href="http://insidehpc.com/2008/12/02/transactional-memory-pro-and-con/feed/" rel="self" type="application/rss+xml" />
	<link>http://insidehpc.com/2008/12/02/transactional-memory-pro-and-con/</link>
	<description>HPC news for supercomputing professionals</description>
	<lastBuildDate>Mon, 21 May 2012 17:48:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Chy King</title>
		<link>http://insidehpc.com/2008/12/02/transactional-memory-pro-and-con/comment-page-1/#comment-170397</link>
		<dc:creator>Chy King</dc:creator>
		<pubDate>Mon, 22 Jun 2009 16:14:07 +0000</pubDate>
		<guid isPermaLink="false">http://insidehpc.com/?p=3171#comment-170397</guid>
		<description>No James.. this is true .. I can prove you that .. Emailed you!</description>
		<content:encoded><![CDATA[<p>No James.. this is true .. I can prove you that .. Emailed you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Strutton</title>
		<link>http://insidehpc.com/2008/12/02/transactional-memory-pro-and-con/comment-page-1/#comment-167137</link>
		<dc:creator>James Strutton</dc:creator>
		<pubDate>Mon, 25 May 2009 19:42:54 +0000</pubDate>
		<guid isPermaLink="false">http://insidehpc.com/?p=3171#comment-167137</guid>
		<description>This model promises to provide the scalability of fine-grain locking, while avoiding common pitfalls of lock ......... I bet!</description>
		<content:encoded><![CDATA[<p>This model promises to provide the scalability of fine-grain locking, while avoiding common pitfalls of lock &#8230;&#8230;&#8230; I bet!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

