- mpiwg-rma - mailman3.cels.anl.gov

[Mpi3-rma] FW: Telecon
by Rajeev Thakur 15 Jun '10

15 Jun '10

We are again having a working group meeting if anyone wants to call in... -----Original Message----- From: mpi3-rma-bounces(a)lists.mpi-forum.org [mailto:[email protected]] On Behalf Of Rajeev Thakur Sent: Tuesday, June 15, 2010 11:22 AM To: 'MPI 3.0 Remote Memory Access working group' Subject: [Mpi3-rma] FW: Telecon If anyone wants to join in, we are having the working group meeting now. Dialing info attached. -----Original Message----- From: mpi3-rma-bounces(a)lists.mpi-forum.org [mailto:[email protected]] On Behalf Of Rajeev Thakur Sent: Saturday, June 12, 2010 9:30 PM To: 'MPI 3.0 Remote Memory Access working group' Subject: [Mpi3-rma] (no subject) Jeff has set up Webex telecons for the RMA working group meetings on Tue and Wed next week during the Forum meeting. Attached is the dialing info. Rajeev

1 0

[Mpi3-rma] FW: Telecon
by Rajeev Thakur 15 Jun '10

15 Jun '10

If anyone wants to join in, we are having the working group meeting now. Dialing info attached. -----Original Message----- From: mpi3-rma-bounces(a)lists.mpi-forum.org [mailto:[email protected]] On Behalf Of Rajeev Thakur Sent: Saturday, June 12, 2010 9:30 PM To: 'MPI 3.0 Remote Memory Access working group' Subject: [Mpi3-rma] (no subject) Jeff has set up Webex telecons for the RMA working group meetings on Tue and Wed next week during the Forum meeting. Attached is the dialing info. Rajeev

1 0

Re: [Mpi3-rma] (no subject)
by Pavan Balaji 14 Jun '10

14 Jun '10

On 06/14/2010 08:14 AM, Douglas Miller wrote: > Then maybe that's the reason it has to be in MPI_Info instead of asserts, > and that these become reserved keys in the MPI spec. Or are you referring > to something other than the added parameter 'asserts'. I was referring to the asserts. MPI_Info is only a hint (the application is allowed to lie about it). It cannot be used as an assertion from the program. -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji

1 0

Re: [Mpi3-rma] (no subject)
by Douglas Miller 14 Jun '10

14 Jun '10

Then maybe that's the reason it has to be in MPI_Info instead of asserts, and that these become reserved keys in the MPI spec. Or are you referring to something other than the added parameter 'asserts'. _______________________________________________ Douglas Miller BlueGene Messaging Development IBM Corp., Rochester, MN USA Bldg 030-2 A410 dougmill(a)us.ibm.com Douglas Miller/Rochester/IBM Pavan Balaji <balaji(a)mcs.anl.g ov> To Sent by: "MPI 3.0 Remote Memory Access mpi3-rma-bounces@ working group" lists.mpi-forum.o <mpi3-rma(a)lists.mpi-forum.org> rg cc Subject 06/14/2010 08:05 Re: [Mpi3-rma] (no subject) AM Please respond to "MPI 3.0 Remote Memory Access working group" <mpi3-rma(a)lists.m pi-forum.org> This breaks backward compatibility. Pavan Balaji @ iPhone On Jun 14, 2010, at 8:00 AM, Douglas Miller <dougmill(a)us.ibm.com> wrote: > Hi Rajeev, > > Here's a slide regarding my proposed addition to MPI3 RMA (asserts on > MPI_WIN_CREATE to specify synchronization method). I hope we have a > chance > to discuss this. > > (See attached file: mpi3_rma_win_asserts.pdf) > > thanks, > _______________________________________________ > Douglas Miller BlueGene Messaging Development > IBM Corp., Rochester, MN USA Bldg 030-2 A410 > dougmill(a)us.ibm.com Douglas Miller/Rochester/IBM > > > > "Rajeev Thakur" > <thakur(a)mcs.anl.g > > ov> To > Sent by: "'MPI 3.0 Remote Memory Access > mpi3-rma-bounces@ working group'" > lists.mpi-forum.o <mpi3-rma(a)lists.mpi-forum.org> > > rg cc > > > Subject > 06/12/2010 09:29 [Mpi3-rma] (no subject) > PM > > > Please respond to > "MPI 3.0 Remote > Memory Access > working group" > <mpi3-rma(a)lists.m > pi-forum.org> > > > > > > > Jeff has set up Webex telecons for the RMA working group meetings on > Tue > and Wed next week during the Forum meeting. Attached is the dialing > info. > > Rajeev > > > ----- Message from "Jeff Squyres" <messenger(a)webex.com> on Fri, 28 > May 2010 > 16:54:05 -0500 ----- > > To: <thakur(a)mcs.anl.gov> > > Subject: Meeting invitation: Tuesday MPI-3 RMA WG > meeting > > > > Hello , > > Jeff Squyres invites you to attend this online meeting. > > Topic: Tuesday MPI-3 RMA WG meeting > Date: Tuesday, June 15, 2010 > Time: 12:00 pm, Eastern Daylight Time (New York, GMT-04:00) > Meeting Number: 209 841 524 > Meeting Password: mpi3 > > > ------------------------------------------------------- > To join the online meeting (Now from iPhones and other Smartphones > too!) > ------------------------------------------------------- > 1. Go to > https://cisco.webex.com/ciscosales/j.php?ED=141315682&UID=1325823482&PW=NYW… > > 2. Enter your name and email address. > 3. Enter the meeting password: mpi3 > 4. Click "Join Now". > > To view in other time zones or languages, please click the link: > https://cisco.webex.com/ciscosales/j.php?ED=141315682&UID=1325823482&PW=NYW… > > > ---------------------------------------------------------------- > ALERT:Toll-Free Dial Restrictions for (408) and (919) Area Codes > ---------------------------------------------------------------- > > The affected toll free numbers are: (866) 432-9903 for the San > Jose/Milpitas area and (866) 349-3520 for the RTP area. > > Please dial the local access number for your area from the list below: > - San Jose/Milpitas (408) area: 525-6800 > - RTP (919) area: 392-3330 > > ------------------------------------------------------- > To join the teleconference only > ------------------------------------------------------- > 1. Dial into Cisco WebEx (view all Global Access Numbers at > http://cisco.com/en/US/about/doing_business/conferencing/index.html > 2. Follow the prompts to enter the Meeting Number (listed above) or > Access > Code followed by the # sign. > > San Jose, CA: +1.408.525.6800 RTP: +1.919.392.3330 > > US/Canada: +1.866.432.9903 United Kingdom: +44.20.8824.0117 > > India: +91.80.4350.1111 Germany: +49.619.6773.9002 > > Japan: +81.3.5763.9394 China: +86.10.8515.5666 > > ------------------------------------------------------- > For assistance > ------------------------------------------------------- > 1. Go to https://cisco.webex.com/ciscosales/mc > 2. On the left navigation bar, click "Support". > > You can contact me at: > jsquyres(a)cisco.com > 1-408-525 0971 > > To add this meeting to your calendar program (for example Microsoft > Outlook), click this link: > https://cisco.webex.com/ciscosales/j.php?ED=141315682&UID=1325823482&ICS=MI… > > > The playback of UCF (Universal Communications Format) rich media files > requires appropriate players. To view this type of rich media files > in the > meeting, please check whether you have the players installed on your > computer by going to https://cisco.webex.com/ciscosales/systemdiagnosis.php > > > Sign up for a free trial of WebEx > http://www.webex.com/go/mcemfreetrial > > http://www.webex.com > > CCP:+14085256800x209841524# > > IMPORTANT NOTICE: This WebEx service includes a feature that allows > audio > and any documents and other materials exchanged or viewed during the > session to be recorded. By joining this session, you automatically > consent > to such recordings. If you do not consent to the recording, do not > join the > session. > > ----- Message from "Jeff Squyres" <messenger(a)webex.com> on Fri, 28 > May 2010 > 16:56:11 -0500 ----- > > To: <thakur(a)mcs.anl.gov> > > Subject: Meeting invitation: Wednesday MPI-3 RMA WG > meeting > > > > Hello , > > Jeff Squyres invites you to attend this online meeting. > > Topic: Wednesday MPI-3 RMA WG meeting > Date: Wednesday, June 16, 2010 > Time: 12:00 pm, Eastern Daylight Time (New York, GMT-04:00) > Meeting Number: 203 788 787 > Meeting Password: mpi3 > > > ------------------------------------------------------- > To join the online meeting (Now from iPhones and other Smartphones > too!) > ------------------------------------------------------- > 1. Go to > https://cisco.webex.com/ciscosales/j.php?ED=141316462&UID=1325823557&PW=NYT… > > 2. Enter your name and email address. > 3. Enter the meeting password: mpi3 > 4. Click "Join Now". > > To view in other time zones or languages, please click the link: > https://cisco.webex.com/ciscosales/j.php?ED=141316462&UID=1325823557&PW=NYT… > > > ---------------------------------------------------------------- > ALERT:Toll-Free Dial Restrictions for (408) and (919) Area Codes > ---------------------------------------------------------------- > > The affected toll free numbers are: (866) 432-9903 for the San > Jose/Milpitas area and (866) 349-3520 for the RTP area. > > Please dial the local access number for your area from the list below: > - San Jose/Milpitas (408) area: 525-6800 > - RTP (919) area: 392-3330 > > ------------------------------------------------------- > To join the teleconference only > ------------------------------------------------------- > 1. Dial into Cisco WebEx (view all Global Access Numbers at > http://cisco.com/en/US/about/doing_business/conferencing/index.html > 2. Follow the prompts to enter the Meeting Number (listed above) or > Access > Code followed by the # sign. > > San Jose, CA: +1.408.525.6800 RTP: +1.919.392.3330 > > US/Canada: +1.866.432.9903 United Kingdom: +44.20.8824.0117 > > India: +91.80.4350.1111 Germany: +49.619.6773.9002 > > Japan: +81.3.5763.9394 China: +86.10.8515.5666 > > ------------------------------------------------------- > For assistance > ------------------------------------------------------- > 1. Go to https://cisco.webex.com/ciscosales/mc > 2. On the left navigation bar, click "Support". > > You can contact me at: > jsquyres(a)cisco.com > 1-408-525 0971 > > To add this meeting to your calendar program (for example Microsoft > Outlook), click this link: > https://cisco.webex.com/ciscosales/j.php?ED=141316462&UID=1325823557&ICS=MI… > > > The playback of UCF (Universal Communications Format) rich media files > requires appropriate players. To view this type of rich media files > in the > meeting, please check whether you have the players installed on your > computer by going to https://cisco.webex.com/ciscosales/systemdiagnosis.php > > > Sign up for a free trial of WebEx > http://www.webex.com/go/mcemfreetrial > > http://www.webex.com > > CCP:+14085256800x203788787# > > IMPORTANT NOTICE: This WebEx service includes a feature that allows > audio > and any documents and other materials exchanged or viewed during the > session to be recorded. By joining this session, you automatically > consent > to such recordings. If you do not consent to the recording, do not > join the > session. _______________________________________________ > mpi3-rma mailing list > mpi3-rma(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-rma > <mpi3_rma_win_asserts.pdf> > _______________________________________________ > mpi3-rma mailing list > mpi3-rma(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-rma _______________________________________________ mpi3-rma mailing list mpi3-rma(a)lists.mpi-forum.org http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-rma

1 0

Re: [Mpi3-rma] (no subject)
by Pavan Balaji 14 Jun '10

14 Jun '10

This breaks backward compatibility. Pavan Balaji @ iPhone On Jun 14, 2010, at 8:00 AM, Douglas Miller <dougmill(a)us.ibm.com> wrote: > Hi Rajeev, > > Here's a slide regarding my proposed addition to MPI3 RMA (asserts on > MPI_WIN_CREATE to specify synchronization method). I hope we have a > chance > to discuss this. > > (See attached file: mpi3_rma_win_asserts.pdf) > > thanks, > _______________________________________________ > Douglas Miller BlueGene Messaging Development > IBM Corp., Rochester, MN USA Bldg 030-2 A410 > dougmill(a)us.ibm.com Douglas Miller/Rochester/IBM > > > > "Rajeev Thakur" > <thakur(a)mcs.anl.g > > ov> To > Sent by: "'MPI 3.0 Remote Memory Access > mpi3-rma-bounces@ working group'" > lists.mpi-forum.o <mpi3-rma(a)lists.mpi-forum.org> > > rg cc > > > Subject > 06/12/2010 09:29 [Mpi3-rma] (no subject) > PM > > > Please respond to > "MPI 3.0 Remote > Memory Access > working group" > <mpi3-rma(a)lists.m > pi-forum.org> > > > > > > > Jeff has set up Webex telecons for the RMA working group meetings on > Tue > and Wed next week during the Forum meeting. Attached is the dialing > info. > > Rajeev > > > ----- Message from "Jeff Squyres" <messenger(a)webex.com> on Fri, 28 > May 2010 > 16:54:05 -0500 ----- > > To: <thakur(a)mcs.anl.gov> > > Subject: Meeting invitation: Tuesday MPI-3 RMA WG > meeting > > > > Hello , > > Jeff Squyres invites you to attend this online meeting. > > Topic: Tuesday MPI-3 RMA WG meeting > Date: Tuesday, June 15, 2010 > Time: 12:00 pm, Eastern Daylight Time (New York, GMT-04:00) > Meeting Number: 209 841 524 > Meeting Password: mpi3 > > > ------------------------------------------------------- > To join the online meeting (Now from iPhones and other Smartphones > too!) > ------------------------------------------------------- > 1. Go to > https://cisco.webex.com/ciscosales/j.php?ED=141315682&UID=1325823482&PW=NYW… > > 2. Enter your name and email address. > 3. Enter the meeting password: mpi3 > 4. Click "Join Now". > > To view in other time zones or languages, please click the link: > https://cisco.webex.com/ciscosales/j.php?ED=141315682&UID=1325823482&PW=NYW… > > > ---------------------------------------------------------------- > ALERT:Toll-Free Dial Restrictions for (408) and (919) Area Codes > ---------------------------------------------------------------- > > The affected toll free numbers are: (866) 432-9903 for the San > Jose/Milpitas area and (866) 349-3520 for the RTP area. > > Please dial the local access number for your area from the list below: > - San Jose/Milpitas (408) area: 525-6800 > - RTP (919) area: 392-3330 > > ------------------------------------------------------- > To join the teleconference only > ------------------------------------------------------- > 1. Dial into Cisco WebEx (view all Global Access Numbers at > http://cisco.com/en/US/about/doing_business/conferencing/index.html > 2. Follow the prompts to enter the Meeting Number (listed above) or > Access > Code followed by the # sign. > > San Jose, CA: +1.408.525.6800 RTP: +1.919.392.3330 > > US/Canada: +1.866.432.9903 United Kingdom: +44.20.8824.0117 > > India: +91.80.4350.1111 Germany: +49.619.6773.9002 > > Japan: +81.3.5763.9394 China: +86.10.8515.5666 > > ------------------------------------------------------- > For assistance > ------------------------------------------------------- > 1. Go to https://cisco.webex.com/ciscosales/mc > 2. On the left navigation bar, click "Support". > > You can contact me at: > jsquyres(a)cisco.com > 1-408-525 0971 > > To add this meeting to your calendar program (for example Microsoft > Outlook), click this link: > https://cisco.webex.com/ciscosales/j.php?ED=141315682&UID=1325823482&ICS=MI… > > > The playback of UCF (Universal Communications Format) rich media files > requires appropriate players. To view this type of rich media files > in the > meeting, please check whether you have the players installed on your > computer by going to https://cisco.webex.com/ciscosales/systemdiagnosis.php > > > Sign up for a free trial of WebEx > http://www.webex.com/go/mcemfreetrial > > http://www.webex.com > > CCP:+14085256800x209841524# > > IMPORTANT NOTICE: This WebEx service includes a feature that allows > audio > and any documents and other materials exchanged or viewed during the > session to be recorded. By joining this session, you automatically > consent > to such recordings. If you do not consent to the recording, do not > join the > session. > > ----- Message from "Jeff Squyres" <messenger(a)webex.com> on Fri, 28 > May 2010 > 16:56:11 -0500 ----- > > To: <thakur(a)mcs.anl.gov> > > Subject: Meeting invitation: Wednesday MPI-3 RMA WG > meeting > > > > Hello , > > Jeff Squyres invites you to attend this online meeting. > > Topic: Wednesday MPI-3 RMA WG meeting > Date: Wednesday, June 16, 2010 > Time: 12:00 pm, Eastern Daylight Time (New York, GMT-04:00) > Meeting Number: 203 788 787 > Meeting Password: mpi3 > > > ------------------------------------------------------- > To join the online meeting (Now from iPhones and other Smartphones > too!) > ------------------------------------------------------- > 1. Go to > https://cisco.webex.com/ciscosales/j.php?ED=141316462&UID=1325823557&PW=NYT… > > 2. Enter your name and email address. > 3. Enter the meeting password: mpi3 > 4. Click "Join Now". > > To view in other time zones or languages, please click the link: > https://cisco.webex.com/ciscosales/j.php?ED=141316462&UID=1325823557&PW=NYT… > > > ---------------------------------------------------------------- > ALERT:Toll-Free Dial Restrictions for (408) and (919) Area Codes > ---------------------------------------------------------------- > > The affected toll free numbers are: (866) 432-9903 for the San > Jose/Milpitas area and (866) 349-3520 for the RTP area. > > Please dial the local access number for your area from the list below: > - San Jose/Milpitas (408) area: 525-6800 > - RTP (919) area: 392-3330 > > ------------------------------------------------------- > To join the teleconference only > ------------------------------------------------------- > 1. Dial into Cisco WebEx (view all Global Access Numbers at > http://cisco.com/en/US/about/doing_business/conferencing/index.html > 2. Follow the prompts to enter the Meeting Number (listed above) or > Access > Code followed by the # sign. > > San Jose, CA: +1.408.525.6800 RTP: +1.919.392.3330 > > US/Canada: +1.866.432.9903 United Kingdom: +44.20.8824.0117 > > India: +91.80.4350.1111 Germany: +49.619.6773.9002 > > Japan: +81.3.5763.9394 China: +86.10.8515.5666 > > ------------------------------------------------------- > For assistance > ------------------------------------------------------- > 1. Go to https://cisco.webex.com/ciscosales/mc > 2. On the left navigation bar, click "Support". > > You can contact me at: > jsquyres(a)cisco.com > 1-408-525 0971 > > To add this meeting to your calendar program (for example Microsoft > Outlook), click this link: > https://cisco.webex.com/ciscosales/j.php?ED=141316462&UID=1325823557&ICS=MI… > > > The playback of UCF (Universal Communications Format) rich media files > requires appropriate players. To view this type of rich media files > in the > meeting, please check whether you have the players installed on your > computer by going to https://cisco.webex.com/ciscosales/systemdiagnosis.php > > > Sign up for a free trial of WebEx > http://www.webex.com/go/mcemfreetrial > > http://www.webex.com > > CCP:+14085256800x203788787# > > IMPORTANT NOTICE: This WebEx service includes a feature that allows > audio > and any documents and other materials exchanged or viewed during the > session to be recorded. By joining this session, you automatically > consent > to such recordings. If you do not consent to the recording, do not > join the > session. _______________________________________________ > mpi3-rma mailing list > mpi3-rma(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-rma > <mpi3_rma_win_asserts.pdf> > _______________________________________________ > mpi3-rma mailing list > mpi3-rma(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-rma

1 0

Re: [Mpi3-rma] (no subject)
by Douglas Miller 14 Jun '10

14 Jun '10

Hi Rajeev, Here's a slide regarding my proposed addition to MPI3 RMA (asserts on MPI_WIN_CREATE to specify synchronization method). I hope we have a chance to discuss this. (See attached file: mpi3_rma_win_asserts.pdf) thanks, _______________________________________________ Douglas Miller BlueGene Messaging Development IBM Corp., Rochester, MN USA Bldg 030-2 A410 dougmill(a)us.ibm.com Douglas Miller/Rochester/IBM "Rajeev Thakur" <thakur(a)mcs.anl.g ov> To Sent by: "'MPI 3.0 Remote Memory Access mpi3-rma-bounces@ working group'" lists.mpi-forum.o <mpi3-rma(a)lists.mpi-forum.org> rg cc Subject 06/12/2010 09:29 [Mpi3-rma] (no subject) PM Please respond to "MPI 3.0 Remote Memory Access working group" <mpi3-rma(a)lists.m pi-forum.org> Jeff has set up Webex telecons for the RMA working group meetings on Tue and Wed next week during the Forum meeting. Attached is the dialing info. Rajeev ----- Message from "Jeff Squyres" <messenger(a)webex.com> on Fri, 28 May 2010 16:54:05 -0500 ----- To: <thakur(a)mcs.anl.gov> Subject: Meeting invitation: Tuesday MPI-3 RMA WG meeting Hello , Jeff Squyres invites you to attend this online meeting. Topic: Tuesday MPI-3 RMA WG meeting Date: Tuesday, June 15, 2010 Time: 12:00 pm, Eastern Daylight Time (New York, GMT-04:00) Meeting Number: 209 841 524 Meeting Password: mpi3 ------------------------------------------------------- To join the online meeting (Now from iPhones and other Smartphones too!) ------------------------------------------------------- 1. Go to https://cisco.webex.com/ciscosales/j.php?ED=141315682&UID=1325823482&PW=NYW… 2. Enter your name and email address. 3. Enter the meeting password: mpi3 4. Click "Join Now". To view in other time zones or languages, please click the link: https://cisco.webex.com/ciscosales/j.php?ED=141315682&UID=1325823482&PW=NYW… ---------------------------------------------------------------- ALERT:Toll-Free Dial Restrictions for (408) and (919) Area Codes ---------------------------------------------------------------- The affected toll free numbers are: (866) 432-9903 for the San Jose/Milpitas area and (866) 349-3520 for the RTP area. Please dial the local access number for your area from the list below: - San Jose/Milpitas (408) area: 525-6800 - RTP (919) area: 392-3330 ------------------------------------------------------- To join the teleconference only ------------------------------------------------------- 1. Dial into Cisco WebEx (view all Global Access Numbers at http://cisco.com/en/US/about/doing_business/conferencing/index.html 2. Follow the prompts to enter the Meeting Number (listed above) or Access Code followed by the # sign. San Jose, CA: +1.408.525.6800 RTP: +1.919.392.3330 US/Canada: +1.866.432.9903 United Kingdom: +44.20.8824.0117 India: +91.80.4350.1111 Germany: +49.619.6773.9002 Japan: +81.3.5763.9394 China: +86.10.8515.5666 ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://cisco.webex.com/ciscosales/mc 2. On the left navigation bar, click "Support". You can contact me at: jsquyres(a)cisco.com 1-408-525 0971 To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://cisco.webex.com/ciscosales/j.php?ED=141315682&UID=1325823482&ICS=MI… The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://cisco.webex.com/ciscosales/systemdiagnosis.php Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com CCP:+14085256800x209841524# IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, do not join the session. ----- Message from "Jeff Squyres" <messenger(a)webex.com> on Fri, 28 May 2010 16:56:11 -0500 ----- To: <thakur(a)mcs.anl.gov> Subject: Meeting invitation: Wednesday MPI-3 RMA WG meeting Hello , Jeff Squyres invites you to attend this online meeting. Topic: Wednesday MPI-3 RMA WG meeting Date: Wednesday, June 16, 2010 Time: 12:00 pm, Eastern Daylight Time (New York, GMT-04:00) Meeting Number: 203 788 787 Meeting Password: mpi3 ------------------------------------------------------- To join the online meeting (Now from iPhones and other Smartphones too!) ------------------------------------------------------- 1. Go to https://cisco.webex.com/ciscosales/j.php?ED=141316462&UID=1325823557&PW=NYT… 2. Enter your name and email address. 3. Enter the meeting password: mpi3 4. Click "Join Now". To view in other time zones or languages, please click the link: https://cisco.webex.com/ciscosales/j.php?ED=141316462&UID=1325823557&PW=NYT… ---------------------------------------------------------------- ALERT:Toll-Free Dial Restrictions for (408) and (919) Area Codes ---------------------------------------------------------------- The affected toll free numbers are: (866) 432-9903 for the San Jose/Milpitas area and (866) 349-3520 for the RTP area. Please dial the local access number for your area from the list below: - San Jose/Milpitas (408) area: 525-6800 - RTP (919) area: 392-3330 ------------------------------------------------------- To join the teleconference only ------------------------------------------------------- 1. Dial into Cisco WebEx (view all Global Access Numbers at http://cisco.com/en/US/about/doing_business/conferencing/index.html 2. Follow the prompts to enter the Meeting Number (listed above) or Access Code followed by the # sign. San Jose, CA: +1.408.525.6800 RTP: +1.919.392.3330 US/Canada: +1.866.432.9903 United Kingdom: +44.20.8824.0117 India: +91.80.4350.1111 Germany: +49.619.6773.9002 Japan: +81.3.5763.9394 China: +86.10.8515.5666 ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://cisco.webex.com/ciscosales/mc 2. On the left navigation bar, click "Support". You can contact me at: jsquyres(a)cisco.com 1-408-525 0971 To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://cisco.webex.com/ciscosales/j.php?ED=141316462&UID=1325823557&ICS=MI… The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://cisco.webex.com/ciscosales/systemdiagnosis.php Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com CCP:+14085256800x203788787# IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, do not join the session. _______________________________________________ mpi3-rma mailing list mpi3-rma(a)lists.mpi-forum.org http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-rma

1 0

[Mpi3-rma] (no subject)
by Rajeev Thakur 12 Jun '10

12 Jun '10

Jeff has set up Webex telecons for the RMA working group meetings on Tue and Wed next week during the Forum meeting. Attached is the dialing info. Rajeev

1 0

Re: [Mpi3-rma] mpi3-rma post from [email protected] requires approval
by Underwood, Keith D 05 Jun '10

05 Jun '10

Well, the use case isn't theoretical - my understanding is that Quadrics explicitly supported that driven by customer needs; however, as I said before, (2) is the one that I think is really critical. It is the only one I believe that you have to have to get something resembling sequential consistency from a single thread. Keith > -----Original Message----- > From: Pavan Balaji [mailto:[email protected]] > Sent: Saturday, June 05, 2010 9:33 PM > To: Underwood, Keith D > Cc: MPI 3.0 Remote Memory Access working group; bradc(a)cray.com > Subject: Re: [Mpi3-rma] mpi3-rma post from bradc(a)cray.com requires > approval > > > Guaranteeing (1) in hardware is not easy when the message is split > across two or more adapters, or two or more routes. > > Apart from a theoretical use case, is there a real need for this? > > -- Pavan > > On 06/05/2010 08:17 PM, Underwood, Keith D wrote: > > I tend to agree that (2) is what is critical, but both (1) & (2) may > be important. The problem with not having (1) is that it gets > significantly more expensive to figure out when a message has been > delivered. <shrug> that may be ok, but may be a pain. Arguably, if > not having (1) were important to a network, you could teach the users > to do finer grained accesses such that each access was unordered > relative to the others. > > > > Anyway, the one important point here is that it is MUCH harder to get > any of these back at the application level than it is to provide them > at the hardware level. If the API doesn't expose a given type of > ordering, you can't make an application "do the right thing" and count > on good hardware giving you that ordering - even if it is easy for the > hardware. > > > > I'll give a specific example: research on low-diameter networks has > indicated that you get relatively little actual reordering at the end- > points when you adaptively route through a low diameter network. Given > that, the end-point could adaptively route and still give you ordering > at the API level; however, because not all hardware will do that, an > application would have to be written as if it had to restore ordering > when it needed it. This would suck beyond words... > > > > Keith > > > >> Thanks for listing these. If we are voting for this, my vote would > be > >> to > >> have (2) and toss out (1) and (3). > >> > >> -- Pavan > >> > >> On 06/05/2010 02:40 PM, Underwood, Keith D wrote: > >>> I was only giving an example of how tightly ordering COULD be > >> defined. Ordering options include: > >>> 1) Ordering within a given replace: is the first byte guaranteed > to > >> get there before the last? > >>> 2) Ordering between replaces to a given location: but, what if two > >> replaces are overlapping? > >>> 3) Ordering among all replaces to a given node > >>> > >>> Two sided gives you something weird, in that it orders the matching > >> of the message headers and not the end of messages or data within > the > >> messages. > >>> Keith > >>> > >>>> -----Original Message----- > >>>> From: Pavan Balaji [mailto:[email protected]] > >>>> Sent: Saturday, June 05, 2010 3:30 PM > >>>> To: Underwood, Keith D > >>>> Cc: MPI 3.0 Remote Memory Access working group; bradc(a)cray.com > >>>> Subject: Re: [Mpi3-rma] mpi3-rma post from bradc(a)cray.com requires > >>>> approval > >>>> > >>>> > >>>> I see. My definition of ordering was a little bit different from > >> yours. > >>>> My definition was -- if I do two accumulates with replace on the > >> same > >>>> location, I'm guaranteed to have the second value in the location. > >> It > >>>> didn't have any definition of ordering to two different locations. > >>>> > >>>> So, I think we need to come to a consensus first on what the > actual > >>>> definition of ordering is. > >>>> > >>>> -- Pavan > >>>> > >>>> On 06/05/2010 02:22 PM, Underwood, Keith D wrote: > >>>>>>> We would need to think about whether we have to have the whole > >>>>>>> message ordered or ordered on a per target address basis. > >>>>>> Atomicity and ordering go hand-in-hand; if there's no atomicity, > >>>>>> ordering doesn't make sense. Since we have basic datatype > >> atomicity > >>>> for > >>>>>> accumulate/get_accumulate, ordering would make sense at that > >>>>>> granularity > >>>>>> as well. > >>>>>> > >>>>>> If someone wants to propose full-message atomicity, then we can > >>>>>> consider > >>>>>> ordering at that granularity too. But till then, whole message > >>>> ordering > >>>>>> is an overkill. > >>>>> Well, they aren't orthogonal, but they aren't quite that tightly > >>>> linked. A user that knew that two messages were not going to > >> overlap > >>>> might want to use a full message ordering from a single node for > >>>> completion detection. E.g. an MPI_Accumulate() with "replace" to > >> one > >>>> buffer and then an MPI_Accumulate() to another buffer to increment > a > >>>> variable and use the full message ordering to be able to use the > >> latter > >>>> for completion without the expense of a flush() between the > >> messages. > >>>> So, it has value and a usage scenario. I just don't know if we > want > >> to > >>>> go that far or not. > >>>>> Keith > >>>> -- > >>>> Pavan Balaji > >>>> http://www.mcs.anl.gov/~balaji > >> -- > >> Pavan Balaji > >> http://www.mcs.anl.gov/~balaji > > -- > Pavan Balaji > http://www.mcs.anl.gov/~balaji

1 0

Re: [Mpi3-rma] mpi3-rma post from [email protected] requires approval
by Vinod tipparaju 05 Jun '10

05 Jun '10

> I tend to agree that (2) is what is critical, but both (1) & (2) may be important. The problem with not having (1) is that it gets significantly more expensive to figure out when a message has been delivered. <shrug> that may be ok, but may be a pain. Seems like (2) is the most useful to support. As far as (1), is probably not safe to ever legally allow a user poll on a last byte to check for message being delivered; it also is a heavy weight process to give this guarantee when a system doesn't. Thanks,Vinod. > > > Thanks for listing these. If we are voting for this, my vote would be > > to > > have (2) and toss out (1) and (3). > > > > -- Pavan > > > > On 06/05/2010 02:40 PM, Underwood, Keith D wrote: > > > I was only giving an example of how tightly ordering COULD be > > defined. Ordering options include: > > > > > > 1) Ordering within a given replace: is the first byte guaranteed to > > get there before the last? > > > 2) Ordering between replaces to a given location: but, what if two > > replaces are overlapping? > > > 3) Ordering among all replaces to a given node > > > > > > Two sided gives you something weird, in that it orders the matching > > of the message headers and not the end of messages or data within the > > messages. > > > > > > Keith > > > > > >> -----Original Message----- > > >> From: Pavan Balaji [mailto:[email protected]] > > >> Sent: Saturday, June 05, 2010 3:30 PM > > >> To: Underwood, Keith D > > >> Cc: MPI 3.0 Remote Memory Access working group; bradc(a)cray.com > > >> Subject: Re: [Mpi3-rma] mpi3-rma post from bradc(a)cray.com requires > > >> approval > > >> > > >> > > >> I see. My definition of ordering was a little bit different from > > yours. > > >> > > >> My definition was -- if I do two accumulates with replace on the > > same > > >> location, I'm guaranteed to have the second value in the location. > > It > > >> didn't have any definition of ordering to two different locations. > > >> > > >> So, I think we need to come to a consensus first on what the actual > > >> definition of ordering is. > > >> > > >> -- Pavan > > >> > > >> On 06/05/2010 02:22 PM, Underwood, Keith D wrote: > > >>>>> We would need to think about whether we have to have the whole > > >>>>> message ordered or ordered on a per target address basis. > > >>>> Atomicity and ordering go hand-in-hand; if there's no atomicity, > > >>>> ordering doesn't make sense. Since we have basic datatype > > atomicity > > >> for > > >>>> accumulate/get_accumulate, ordering would make sense at that > > >>>> granularity > > >>>> as well. > > >>>> > > >>>> If someone wants to propose full-message atomicity, then we can > > >>>> consider > > >>>> ordering at that granularity too. But till then, whole message > > >> ordering > > >>>> is an overkill. > > >>> Well, they aren't orthogonal, but they aren't quite that tightly > > >> linked. A user that knew that two messages were not going to > > overlap > > >> might want to use a full message ordering from a single node for > > >> completion detection. E.g. an MPI_Accumulate() with "replace" to > > one > > >> buffer and then an MPI_Accumulate() to another buffer to increment a > > >> variable and use the full message ordering to be able to use the > > latter > > >> for completion without the expense of a flush() between the > > messages. > > >> So, it has value and a usage scenario. I just don't know if we want > > to > > >> go that far or not. > > >>> Keith > > >> -- > > >> Pavan Balaji > > >> http://www.mcs.anl.gov/~balaji > > > > -- > > Pavan Balaji > > http://www.mcs.anl.gov/~balaji > > _______________________________________________ > mpi3-rma mailing list > mpi3-rma(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-rma

1 0

Re: [Mpi3-rma] mpi3-rma post from [email protected] requires approval
by Pavan Balaji 05 Jun '10

05 Jun '10

Guaranteeing (1) in hardware is not easy when the message is split across two or more adapters, or two or more routes. Apart from a theoretical use case, is there a real need for this? -- Pavan On 06/05/2010 08:17 PM, Underwood, Keith D wrote: > I tend to agree that (2) is what is critical, but both (1) & (2) may be important. The problem with not having (1) is that it gets significantly more expensive to figure out when a message has been delivered. <shrug> that may be ok, but may be a pain. Arguably, if not having (1) were important to a network, you could teach the users to do finer grained accesses such that each access was unordered relative to the others. > > Anyway, the one important point here is that it is MUCH harder to get any of these back at the application level than it is to provide them at the hardware level. If the API doesn't expose a given type of ordering, you can't make an application "do the right thing" and count on good hardware giving you that ordering - even if it is easy for the hardware. > > I'll give a specific example: research on low-diameter networks has indicated that you get relatively little actual reordering at the end-points when you adaptively route through a low diameter network. Given that, the end-point could adaptively route and still give you ordering at the API level; however, because not all hardware will do that, an application would have to be written as if it had to restore ordering when it needed it. This would suck beyond words... > > Keith > >> Thanks for listing these. If we are voting for this, my vote would be >> to >> have (2) and toss out (1) and (3). >> >> -- Pavan >> >> On 06/05/2010 02:40 PM, Underwood, Keith D wrote: >>> I was only giving an example of how tightly ordering COULD be >> defined. Ordering options include: >>> 1) Ordering within a given replace: is the first byte guaranteed to >> get there before the last? >>> 2) Ordering between replaces to a given location: but, what if two >> replaces are overlapping? >>> 3) Ordering among all replaces to a given node >>> >>> Two sided gives you something weird, in that it orders the matching >> of the message headers and not the end of messages or data within the >> messages. >>> Keith >>> >>>> -----Original Message----- >>>> From: Pavan Balaji [mailto:[email protected]] >>>> Sent: Saturday, June 05, 2010 3:30 PM >>>> To: Underwood, Keith D >>>> Cc: MPI 3.0 Remote Memory Access working group; bradc(a)cray.com >>>> Subject: Re: [Mpi3-rma] mpi3-rma post from bradc(a)cray.com requires >>>> approval >>>> >>>> >>>> I see. My definition of ordering was a little bit different from >> yours. >>>> My definition was -- if I do two accumulates with replace on the >> same >>>> location, I'm guaranteed to have the second value in the location. >> It >>>> didn't have any definition of ordering to two different locations. >>>> >>>> So, I think we need to come to a consensus first on what the actual >>>> definition of ordering is. >>>> >>>> -- Pavan >>>> >>>> On 06/05/2010 02:22 PM, Underwood, Keith D wrote: >>>>>>> We would need to think about whether we have to have the whole >>>>>>> message ordered or ordered on a per target address basis. >>>>>> Atomicity and ordering go hand-in-hand; if there's no atomicity, >>>>>> ordering doesn't make sense. Since we have basic datatype >> atomicity >>>> for >>>>>> accumulate/get_accumulate, ordering would make sense at that >>>>>> granularity >>>>>> as well. >>>>>> >>>>>> If someone wants to propose full-message atomicity, then we can >>>>>> consider >>>>>> ordering at that granularity too. But till then, whole message >>>> ordering >>>>>> is an overkill. >>>>> Well, they aren't orthogonal, but they aren't quite that tightly >>>> linked. A user that knew that two messages were not going to >> overlap >>>> might want to use a full message ordering from a single node for >>>> completion detection. E.g. an MPI_Accumulate() with "replace" to >> one >>>> buffer and then an MPI_Accumulate() to another buffer to increment a >>>> variable and use the full message ordering to be able to use the >> latter >>>> for completion without the expense of a flush() between the >> messages. >>>> So, it has value and a usage scenario. I just don't know if we want >> to >>>> go that far or not. >>>>> Keith >>>> -- >>>> Pavan Balaji >>>> http://www.mcs.anl.gov/~balaji >> -- >> Pavan Balaji >> http://www.mcs.anl.gov/~balaji -- Pavan Balaji http://www.mcs.anl.gov/~balaji

1 0