<?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: Round Two of the OpenMP-MPI Smack-Down</title>
	<atom:link href="http://www.linux-mag.com/id/7884/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.linux-mag.com/id/7884/</link>
	<description>Open Source, Open Standards</description>
	<lastBuildDate>Sat, 05 Oct 2013 13:48:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: eborisch</title>
		<link>http://www.linux-mag.com/id/7884/#comment-8673</link>
		<dc:creator>eborisch</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7884/#comment-8673</guid>
		<description>&lt;p&gt;Did you happen to use numactl?&lt;/p&gt;
&lt;p&gt;In my testing, it pairs more naturally with MPI, as each MPI process can be bound to a particular node (-N x) and then have all memory allocations be local (-l); on the Nehalem -- and likely any NUMA -- systems this can be a big win by ensuring processes stay close to their memory. As MPI has much more explicit &#039;my&#039; memory vs. &#039;your&#039; memory than OpenMP, this type of binding is easy to implement.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Did you happen to use numactl?</p>
<p>In my testing, it pairs more naturally with MPI, as each MPI process can be bound to a particular node (-N x) and then have all memory allocations be local (-l); on the Nehalem &#8212; and likely any NUMA &#8212; systems this can be a big win by ensuring processes stay close to their memory. As MPI has much more explicit &#8216;my&#8217; memory vs. &#8216;your&#8217; memory than OpenMP, this type of binding is easy to implement.</p>
]]></content:encoded>
	</item>
</channel>
</rss>