<div class="gmail_quote">On Fri, Nov 25, 2011 at 20:06, Mark F. Adams <span dir="ltr"><<a href="mailto:mark.adams@columbia.edu">mark.adams@columbia.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><blockquote type="cite"><div>MIS is straightforward. To define the parallel graph, let's say that ghosting processes have (owner rank, index) of neighbors. An owned point is only a candidate for selection if all neighbors have the same rank or smaller (according to Rule 2 of your paper).</div>
<div><br></div><div>while (candidates remain):</div><div> forall v in owned_candidates with neighbor ranks smaller than p:</div></blockquote><div><br></div></div><div>This is not quite right, and I want to see how complex or cumbersome this one sided model will get when you get all the details in.</div>
<div><br></div><div>You could say loop:</div><div><br></div><div>for all owned_candidates v</div><div> for all neighbors q of v </div><div> if q is selected</div><div> delete v</div><div> skip v</div><div> else if q.proc > myproc and q is not deleted</div>
<div> skip v</div><div> endif</div><div> end for</div><div> if not skip v then </div><div> select v</div><div> delete all q</div><div> broadcast v status ????</div></blockquote><div><br></div><div>Why broadcast the single value immediately? I figured that we would just store the status until we are done with what we can do locally, then we'll do reduce-and-broadcast and move on to the next round.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div> endif</div><div>end for</div><div>reduce all status to owners ???</div></blockquote><div><br></div><div>
Yeah, we reduce the status from the local spaces (which may have marked a point as deleted), then broadcast. The communication graph is stored on the local side.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><br></div><div>I thought in your one-sided model you could not broadcast, or push data. You can only pull data and only want to pull data. But you have a broadcast???</div></blockquote></div><br><div>Remember that my first primitive was "broadcast", which is essentially global-to-local. The map is as a local-to-global map and the "get" is initiated at the local space.</div>