<?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: MPI_Ibarrier: Crazy?</title>
	<atom:link href="http://blogs.cisco.com/performance/mpi_ibarrier-crazy/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.cisco.com/performance/mpi_ibarrier-crazy/</link>
	<description></description>
	<lastBuildDate>Fri, 24 May 2013 19:28:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Jeff Squyres</title>
		<link>http://blogs.cisco.com/performance/mpi_ibarrier-crazy/#comment-661447</link>
		<dc:creator>Jeff Squyres</dc:creator>
		<pubDate>Mon, 17 Sep 2012 16:44:55 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.cisco.com/?p=83073#comment-661447</guid>
		<description><![CDATA[Possibly.  But that somewhat assumes a tightly-coupled MPI application.  

What if the load is non-uniform across the MPI processes?  Having such a &quot;fuzzy&quot; barrier would still allow other processes to do useful things while the slow process is still chunking away, trying to reach the milestone that everyone else has already reached.

Don&#039;t get me wrong -- I&#039;m not saying that a fuzzy barrier is useful everywhere.  Heck, barriers aren&#039;t *needed* in many places (the class of MPI applications that *need* a blocking barrier for correctness is very small).  

But fuzzy barriers are a different animal. If you think of them as milestone markers -- especially in applications with lots of milestones, each of which have varying degrees of dependence on others (ranging from wholly dependent to fully independent) -- then they can be a useful tool to extract more communication / computation overlap.]]></description>
		<content:encoded><![CDATA[<p>Possibly.  But that somewhat assumes a tightly-coupled MPI application.  </p>
<p>What if the load is non-uniform across the MPI processes?  Having such a &#8220;fuzzy&#8221; barrier would still allow other processes to do useful things while the slow process is still chunking away, trying to reach the milestone that everyone else has already reached.</p>
<p>Don&#8217;t get me wrong &#8212; I&#8217;m not saying that a fuzzy barrier is useful everywhere.  Heck, barriers aren&#8217;t *needed* in many places (the class of MPI applications that *need* a blocking barrier for correctness is very small).  </p>
<p>But fuzzy barriers are a different animal. If you think of them as milestone markers &#8212; especially in applications with lots of milestones, each of which have varying degrees of dependence on others (ranging from wholly dependent to fully independent) &#8212; then they can be a useful tool to extract more communication / computation overlap.
<p class="comment-like"><img class="comment-like-btn" title="Vote" onclick="cl_like_this('http://blogs.cisco.com/wp-admin/admin-ajax.php',661447)" src="http://blogs.cisco.com/wp-content/plugins/comments-likes/images/like.png" />&nbsp;&nbsp;&nbsp;<span id="comment-like-cnt-661447">0</span> likes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bibrak</title>
		<link>http://blogs.cisco.com/performance/mpi_ibarrier-crazy/#comment-660507</link>
		<dc:creator>Bibrak</dc:creator>
		<pubDate>Sun, 16 Sep 2012 09:46:04 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.cisco.com/?p=83073#comment-660507</guid>
		<description><![CDATA[The new feature seems a good utility but won&#039;t a process which is slow (the 15 late guy) impact the overall parallelism of the application. 

The parallelism of the entire application will then de dependant on that slow process making the entire application run slower.]]></description>
		<content:encoded><![CDATA[<p>The new feature seems a good utility but won&#8217;t a process which is slow (the 15 late guy) impact the overall parallelism of the application. </p>
<p>The parallelism of the entire application will then de dependant on that slow process making the entire application run slower.
<p class="comment-like"><img class="comment-like-btn" title="Vote" onclick="cl_like_this('http://blogs.cisco.com/wp-admin/admin-ajax.php',660507)" src="http://blogs.cisco.com/wp-content/plugins/comments-likes/images/like.png" />&nbsp;&nbsp;&nbsp;<span id="comment-like-cnt-660507">0</span> likes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Squyres: Is the MPI-3 Non-Blocking Barriers a Crazy Idea? &#124; insideHPC.com</title>
		<link>http://blogs.cisco.com/performance/mpi_ibarrier-crazy/#comment-660489</link>
		<dc:creator>Squyres: Is the MPI-3 Non-Blocking Barriers a Crazy Idea? &#124; insideHPC.com</dc:creator>
		<pubDate>Sun, 16 Sep 2012 09:17:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.cisco.com/?p=83073#comment-660489</guid>
		<description><![CDATA[[...] the Full Story.AKPC_IDS += &quot;31620,&quot;;     Posted in HPC, HPC Software by Rich Brueckner  0 [...]]]></description>
		<content:encoded><![CDATA[<p>[...] the Full Story.AKPC_IDS += &quot;31620,&quot;;     Posted in HPC, HPC Software by Rich Brueckner  0 [...]
<p class="comment-like"><img class="comment-like-btn" title="Vote" onclick="cl_like_this('http://blogs.cisco.com/wp-admin/admin-ajax.php',660489)" src="http://blogs.cisco.com/wp-content/plugins/comments-likes/images/like.png" />&nbsp;&nbsp;&nbsp;<span id="comment-like-cnt-660489">0</span> likes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoffrey Irving</title>
		<link>http://blogs.cisco.com/performance/mpi_ibarrier-crazy/#comment-659765</link>
		<dc:creator>Geoffrey Irving</dc:creator>
		<pubDate>Sat, 15 Sep 2012 17:12:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.cisco.com/?p=83073#comment-659765</guid>
		<description><![CDATA[Yep, this routine comes in very handy in cases where the pattern of messages is unknown.  I asked for it explicitly a while ago without knowing it existed, then had to implement one myself:

    http://scicomp.stackexchange.com/questions/2876/nonblocking-version-of-mpi-barrier-in-mpi-2]]></description>
		<content:encoded><![CDATA[<p>Yep, this routine comes in very handy in cases where the pattern of messages is unknown.  I asked for it explicitly a while ago without knowing it existed, then had to implement one myself:</p>
<p>    <a href="http://scicomp.stackexchange.com/questions/2876/nonblocking-version-of-mpi-barrier-in-mpi-2" rel="nofollow">http://scicomp.stackexchange.com/questions/2876/nonblocking-version-of-mpi-barrier-in-mpi-2</a>
<p class="comment-like"><img class="comment-like-btn" title="Vote" onclick="cl_like_this('http://blogs.cisco.com/wp-admin/admin-ajax.php',659765)" src="http://blogs.cisco.com/wp-content/plugins/comments-likes/images/like.png" />&nbsp;&nbsp;&nbsp;<span id="comment-like-cnt-659765">0</span> likes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jed Brown</title>
		<link>http://blogs.cisco.com/performance/mpi_ibarrier-crazy/#comment-659744</link>
		<dc:creator>Jed Brown</dc:creator>
		<pubDate>Sat, 15 Sep 2012 16:36:52 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.cisco.com/?p=83073#comment-659744</guid>
		<description><![CDATA[See Algorithm 2 of this paper for a practical and communication-optimal use of nonblocking barrier to set up sparse communication.
http://unixer.de/publications/img/hoefler-dsde-protocols.pdf]]></description>
		<content:encoded><![CDATA[<p>See Algorithm 2 of this paper for a practical and communication-optimal use of nonblocking barrier to set up sparse communication.<br />
<a href="http://unixer.de/publications/img/hoefler-dsde-protocols.pdf" rel="nofollow">http://unixer.de/publications/img/hoefler-dsde-protocols.pdf</a>
<p class="comment-like"><img class="comment-like-btn" title="Vote" onclick="cl_like_this('http://blogs.cisco.com/wp-admin/admin-ajax.php',659744)" src="http://blogs.cisco.com/wp-content/plugins/comments-likes/images/like.png" />&nbsp;&nbsp;&nbsp;<span id="comment-like-cnt-659744">0</span> likes</p>
]]></content:encoded>
	</item>
</channel>
</rss>
