<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.ecapple-style-span
{mso-style-name:ec_apple-style-span;}
span.ecapple-converted-space
{mso-style-name:ec_apple-converted-space;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Bill’s proposal was for a persistent handle for transmit
operations that included things like target rank. I think there is some
merit in that, though we need to evaluate the trade-offs. Unfortunately,
that does not really do anything for the random communication
scenario. In the non-random communication scenarios, I’m a
lot less worried about things like random lookups of local data structures
getting in the way. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><br>
Bill’s proposal was nothing like MDBind in Portals, and MDBind does
nothing to help the issue I was concerned about. Specifically, MDBind
only associates local options and a local memory region with a handle. It
says nothing about the target node or the target memory region. It is the
lookup of information associated with the target node and target memory region
that I am worried about and that is addressed by Bill’s proposal for the
non-random access case.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Keith<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> mpi3-rma-bounces@lists.mpi-forum.org
[mailto:mpi3-rma-bounces@lists.mpi-forum.org] <b>On Behalf Of </b>Vinod
tipparaju<br>
<b>Sent:</b> Thursday, September 03, 2009 10:39 PM<br>
<b>To:</b> MPI 3.0 Remote Memory Access working group<br>
<b>Subject:</b> Re: [Mpi3-rma] MPI3 RMA Design Goals<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'>I forgot to include an important parameter
(communicator) in the psuedo interface below:<br>
</span><span class=ecapple-style-span><span style='font-size:10.0pt;font-family:
"Verdana","sans-serif";color:black'>Create_memobj_collective(IN user_ptr, IN
size, IN communicator, OUT mem_obj)</span></span><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
<br>
<span class=ecapple-style-span>In addition to this Bill suggested Bind
interface (something similar to MDBind in portals) that would help reduce
latency for commonly re-used RMAs.</span><br>
<br>
<br>
</span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Vinod
Tipparaju ^ http://ft.ornl.gov/~vinod ^ 1-865-241-1802<br>
<br>
<br>
<o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>
<hr size=2 width="100%" align=center id=stopSpelling>
</span></div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>From:
wgropp@illinois.edu<br>
To: mpi3-rma@lists.mpi-forum.org<br>
Date: Thu, 3 Sep 2009 13:20:38 -0500<br>
Subject: Re: [Mpi3-rma] MPI3 RMA Design Goals<br>
<br>
Design goal one allows collective creation of objects; its there because many
important algorithms don't have collective (over MPI_COMM_WORLD) allocation
semantics, and a design that *requires* collective creation of memory objects
will also limit the use of the interface.<o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Bill<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>On
Sep 3, 2009, at 10:49 AM, Underwood, Keith D wrote:<o:p></o:p></span></p>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>My commentary was on the design goals… if we<span
class=ecapple-converted-space> </span><b><i>allow</i></b><span
class=ecapple-converted-space> </span>collective creation of memory
objects, and design goal #1 simply says we don’t<span
class=ecapple-converted-space> </span><b><i>require</i></b><span
class=ecapple-converted-space> </span>it, that may be ok. Design
goal #1 could be interpreted to mean that you wouldn’t have collective
creation in the semantic at all. Do you really anticipate one data type
for an object that is either collectively or non-collectively created? </span><span
style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I strongly disagree with your assertion that you can communicate
with no cache misses for the non-collectively allocated memory object. In
a non-collectively allocated case, you will have to keep an array of these on
every process, right? i.e. one for every process you are communicating
with? Randomly indexing that array is going to pound on your cache.</span><span
style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>We need to make sure that we don’t ignore the overhead
having multiple communicators and heterogeneity. Yes, I think there are
ways around this, but we should at least consider what is practical and likely
rather than just what is possible.</span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Keith</span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<div>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>From:</span></b><span class=ecapple-converted-space><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'> </span></span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><a
href="mailto:mpi3-rma-bounces@lists.mpi-forum.org">mpi3-rma-bounces@lists.mpi-forum.org</a><span
class=ecapple-converted-space> </span>[<a
href="mailto:mpi3-rma-bounces@lists.mpi-forum.org">mailto:mpi3-rma-bounces@lists.mpi-forum.org</a>]<span
class=ecapple-converted-space> </span><b>On Behalf Of<span
class=ecapple-converted-space> </span></b>Vinod tipparaju<br>
<b>Sent:</b><span class=ecapple-converted-space> </span>Tuesday, September
01, 2009 10:15 AM<br>
<b>To:</b><span class=ecapple-converted-space> </span>MPI 3.0 Remote
Memory Access working group<br>
<b>Subject:</b><span class=ecapple-converted-space> </span>Re: [Mpi3-rma]
MPI3 RMA Design Goals</span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>You are correct in trying to look at the best possible case and
estimating cache-misses/performance-bottlenecks. However, personally don't
see any difference between this and shmem. When you cannot really allocate
symmetric memory underneath, the amount of bookkeeping is same in both cases.
When there is no heterogeneity, the check for this can be disabled at MPI
startup. When there is heterogeneity we cannot compare with shmem.</span><span
style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>I cannot imagine not having symmetric/collective memory object
creation to support these RMA interfaces, I think it is a must-have. Sorry I
have only been saying we should have these interfaces but haven't given any
example for this yet. Given how many times this same issue is coming up, I will
do it now.</span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>Consider the creation interfaces:</span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>Create_memobj(IN user_ptr, IN size, OUT mem_obj)</span><span
style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>Create_memobj_collective(user_ptr, size, OUT mem_obj)</span><span
style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>Assign_memobj(IN/OUT mem_obj, IN user_address, IN size) </span><span
style='color:black'><o:p></o:p></span></p>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>There will be more details on how a mem object which is a result
of create_memobj on process A will be exchanged with process B. When it is
exchanged explicitly, the heterogeneity information can be created at process
B. </span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>Now take the example with symmetric object:</span><span
style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>Process A
</span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>myptr = allocate(mysize);</span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>Create_memobj_collective(myptr,mysize, all_obj);</span><span
style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>Do all kinds of RMA_Xfers</span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>and an example without symmetric object:</span><span
style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>myptr = allocate(mysize);</span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>Create_memobj(myptr,mysize,my_obj);</span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> ----exchange objects here----</span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>do all kinds of RAM_Xfers</span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>In both cases, I can see being able to communicate without any
cache misses for mem_obj.</span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
Vinod Tipparaju ^<span class=ecapple-converted-space> </span><a
href="http://ft.ornl.gov/%7Evinod">http://ft.ornl.gov/~vinod</a><span
class=ecapple-converted-space> </span>^ 1-865-241-1802<br>
<br>
</span><span style='color:black'><o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>From:<span
class=ecapple-converted-space> </span><a
href="mailto:keith.d.underwood@intel.com">keith.d.underwood@intel.com</a><br>
To:<span class=ecapple-converted-space> </span><a
href="mailto:mpi3-rma@lists.mpi-forum.org">mpi3-rma@lists.mpi-forum.org</a><br>
Date: Tue, 1 Sep 2009 09:07:41 -0600<br>
Subject: Re: [Mpi3-rma] MPI3 RMA Design Goals</span><span style='color:black'><o:p></o:p></span></p>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If we take the SINGLE_RMA_INTERFACE_DRAFT_PROPOSAL as an
example, and combine it with the draft design goal #1:<span
class=ecapple-converted-space> </span></span><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>In order to support RMA to
arbitrary locations, no constraints on memory, such as symmetric allocation or
collective window creation, can be required</span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>We get an interesting view on how difficult it can be to get
“close to the metal”. So, for MPI_RMA_xfer, we have to assume
that the user has some array of target_mem data items. That means the
sequence of steps in user space is:</span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>target_mem = ranks[dest];</span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>MPI_RMA_xfer(… target_mem, dest…);</span><span
style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>If we assume that the message sizes are small and the destinations
randomly selected and the machine is large… every access to ranks is a
cache miss, and we cannot prevent that by providing fancy hardware. This
actually leads me to believe that we may need to reconsider design goal #1, or
at least clarify what it means in a way that makes the access more efficient.</span><span
style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>MPI_RMA_xfer itself is no picnic either. If we take the
draft design goal #5: The RMA model must support non-cache-coherent and
heterogeneous environments, then MPI is required to maintain a data structure
for every rank (ok, it has to do this anyway, but we are trying to get close to
the metal) and do a lookup into that data structure with every MPI_RMA_xfer to
find out if the target is heterogeneous relative to the target rank –
another cache miss. Now, nominally, since this is inside MPI, a lower
layer could absorb that check… or, a given MPI could refuse to support
heterogeneity or… but, you get the idea. </span><span
style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>So, we’ve got two cache line loads for every transfer.
One in the application and one in the MPI library. One is impossible to
move to the hardware and the other is simply very difficult to move. </span><span
style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>For a contrast, look at SHMEM. Assume homogeneous, only one
communicator context, and hardware mapping of ranks to physical
locations. A shmem_put() of a short item could literally be turned into a
few instructions and a processor store (on machines that supported such
things). Personally, I think we will have done well if we can get to the
point that a reasonable hardware implementation can get MPI RMA to within 2x of
a reasonable SHMEM implementation. I think we have a long way to go to
get there.</span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>Keith</span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<div>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>From:</span></b><span class=ecapple-converted-space><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'> </span></span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><a
href="mailto:mpi3-rma-bounces@lists.mpi-forum.org">mpi3-rma-bounces@lists.mpi-forum.org</a><span
class=ecapple-converted-space> </span>[<a
href="mailto:mpi3-rma-bounces@lists.mpi-forum.org">mailto:mpi3-rma-bounces@lists.mpi-forum.org</a>]<span
class=ecapple-converted-space> </span><b>On Behalf Of<span
class=ecapple-converted-space> </span></b>Vinod tipparaju<br>
<b>Sent:</b><span class=ecapple-converted-space> </span>Tuesday, September
01, 2009 5:23 AM<br>
<b>To:</b><span class=ecapple-converted-space> </span>MPI 3.0 Remote
Memory Access working group<br>
<b>Subject:</b><span class=ecapple-converted-space> </span>Re: [Mpi3-rma]
MPI3 RMA Design Goals</span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>Good points! RMA interfaces should do nothing to prevent utilizing
a high message rate (or low overhead communication) that the underlying hardware
may offer. To ensure this happens, there should always be a unrestricted path
(lets call it this for now, people have called it a "thin layer",
"direct access") to the network. </span><span style='color:black'><o:p></o:p></span></p>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>This means, despite the fact the the RMA interface has features
that abstract out complexity by providing useful characteristics such as
ordering and atomicity, it (the RMA interface) should always have this
unrestricted, close to the heart of the hardware, path. To achieve this, the
unrestricted path should not require any book keeping (from implementation
perspective) in relation to the feature-rich path or vice-versa. </span><span
style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>I believe this is what we have demonstrated with the example
interfaces hence the null set isn't the case here :-). I will distribute an
example implementation very soon so people can get a feel.</span><span
style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'> </span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>---</span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>Vinod Tipparaju ^<span class=ecapple-converted-space> </span><a
href="http://ft.ornl.gov/%7Evinod">http://ft.ornl.gov/~vinod</a><span
class=ecapple-converted-space> </span>^ 1-865-241-1802<br>
<br>
<br>
<br>
> From:<span class=ecapple-converted-space> </span><a
href="mailto:keith.d.underwood@intel.com">keith.d.underwood@intel.com</a><br>
> To:<span class=ecapple-converted-space> </span><a
href="mailto:mpi3-rma@lists.mpi-forum.org">mpi3-rma@lists.mpi-forum.org</a><br>
> Date: Mon, 31 Aug 2009 16:17:28 -0600<br>
> Subject: Re: [Mpi3-rma] MPI3 RMA Design Goals<br>
><span class=ecapple-converted-space> </span><br>
> There has been stunning silence since this email, so I will go ahead and
toss out a thought...<br>
><span class=ecapple-converted-space> </span><br>
> In the draft design goals, I don't see two issues that I see as key. The
first is "support for high message rate/low overhead communications to
random targets". As best I can tell, this is one of the key places were
the existing one-sided operations are perceived as falling down for existing
customers of SHMEM/PGAS. The second is "elimination of the access epoch
requirement". This one may be, um, more controversial, but I believe it is
part and parcel with the first one. That is, the first one is not that valuable
if the programming model requires an excessive amount of access epoch opens and
closes just to force the global visibility of the operations. Unfortunately,
the intersection of this solution space with the solution space for the current
draft design goal #5 (support non-cache-coherent and heterogeneous
environments) may be the null set... I will hold out hope that this isn't the
case ;-)<br>
><span class=ecapple-converted-space> </span><br>
> Keith<span class=ecapple-converted-space> </span><br>
><span class=ecapple-converted-space> </span><br>
> > -----Original Message-----<br>
> > From: <a href="mailto:mpi3-rma-bounces@lists.mpi-forum.org">mpi3-rma-bounces@lists.mpi-forum.org</a>
[<a href="mailto:mpi3-rma-">mailto:mpi3-rma-</a><br>
> ><span class=ecapple-converted-space> </span><a
href="mailto:bounces@lists.mpi-forum.org">bounces@lists.mpi-forum.org</a>] On
Behalf Of William Gropp<br>
> > Sent: Wednesday, August 05, 2009 12:37 PM<br>
> > To:<span class=ecapple-converted-space> </span><a
href="mailto:mpi3-rma@lists.mpi-forum.org">mpi3-rma@lists.mpi-forum.org</a><br>
> > Subject: [Mpi3-rma] MPI3 RMA Design Goals<br>
> ><span class=ecapple-converted-space> </span><br>
> > I've added versions of the RMA design goals that we discussed at the<br>
> > Forum meeting last week to the wiki page for our group (<br>
> ><span class=ecapple-converted-space> </span><a
href="https://svn.mpi-forum.org/trac/mpi-forum-web/wiki/RmaWikiPage">https://svn.mpi-forum.org/trac/mpi-forum-web/wiki/RmaWikiPage</a><br>
> > ). This is a draft; lets discuss these. Also, feel free to add to<br>
> > the discussion, particularly in the background section.<br>
> ><span class=ecapple-converted-space> </span><br>
> > Bill<br>
> ><span class=ecapple-converted-space> </span><br>
> > William Gropp<br>
> > Deputy Director for Research<br>
> > Institute for Advanced Computing Applications and Technologies<br>
> > Paul and Cynthia Saylor Professor of Computer Science<br>
> > University of Illinois Urbana-Champaign<br>
> ><span class=ecapple-converted-space> </span><br>
> ><span class=ecapple-converted-space> </span><br>
> ><span class=ecapple-converted-space> </span><br>
> ><span class=ecapple-converted-space> </span><br>
> > _______________________________________________<br>
> > mpi3-rma mailing list<br>
> ><span class=ecapple-converted-space> </span><a
href="mailto:mpi3-rma@lists.mpi-forum.org">mpi3-rma@lists.mpi-forum.org</a><br>
> ><span class=ecapple-converted-space> </span><a
href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-rma">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-rma</a><br>
><span class=ecapple-converted-space> </span><br>
> _______________________________________________<br>
> mpi3-rma mailing list<br>
><span class=ecapple-converted-space> </span><a
href="mailto:mpi3-rma@lists.mpi-forum.org">mpi3-rma@lists.mpi-forum.org</a><br>
><span class=ecapple-converted-space> </span><a
href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-rma">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-rma</a></span><span
style='color:black'><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";
color:black'><ATT00001.txt><o:p></o:p></span></p>
</div>
</div>
</blockquote>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
<div>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'>William Gropp<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'>Deputy Director for Research<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'>Institute for Advanced Computing Applications and Technologies<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'>Paul and Cynthia Saylor Professor of Computer Science<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'>University of Illinois Urbana-Champaign<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
</div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'><br>
<br>
<o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
</div>
</div>
</div>
</body>
</html>