A reminder that the RMA working group will meet today starting at 2pm Central Time at the Forum meeting in Chicago. A link to the agenda and telecon number are below.
Rajeev
> Begin forwarded message:
>
> From: "Thakur, Rajeev" <thakur(a)mcs.anl.gov>
> Subject: [mpiwg-rma] RMA working group at Forum meeting next week
> Date: February 22, 2016 at 10:50:28 AM CST
> To: MPI WG Remote Memory Access working group <mpiwg-rma(a)lists.mpi-forum.org>
> Reply-To: MPI WG Remote Memory Access working group <mpiwg-rma(a)lists.mpi-forum.org>
>
> We have two working group slots on Monday afternoon (http://meetings.mpi-forum.org/secretary/2016/03/agenda.php)
>
> We will discuss items on the agenda page here: https://github.com/mpiwg-rma/rma-issues/wiki/Draft-Agenda-for-MPI-RMA-Worki….
>
> If you cannot attend in person, you can participate via the following telecon number.
>
> Tel: 1-218-548-7018
> Passcode: 262144
>
> Rajeev
no !
2015-10-22 20:11 GMT+02:00 Jeff Hammond <jeff.science(a)gmail.com>:
> can someone please add me to https://github.com/mpiwg-rma? i have many
> tickets to migrate...
>
> i cannot see who owns this org to request privately...
>
> thanks,
>
> jeff
>
> --
> Jeff Hammond
> jeff.science(a)gmail.com
> http://jeffhammond.github.io/
>
> _______________________________________________
> mpiwg-rma mailing list
> mpiwg-rma(a)lists.mpi-forum.org
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-rma
>
i suppose that works, but it is not visible on e.g.
https://github.com/mpiwg-large-count, which might be where someone lands.
anyways, i don't really care. i'm making myself public on all of these
orgs so in the worst case, people that don't know better will send me
inquiries and i will inform them that MapReduce is the future and to stop
using MPI ;-)
jeff
On Thu, Oct 22, 2015 at 11:30 AM, Bland, Wesley <wesley.bland(a)intel.com>
wrote:
> Or just put their name in the README.md in the rma-issues repo.
>
> On Oct 22, 2015, at 1:27 PM, Jeff Hammond <jeff.science(a)gmail.com> wrote:
>
> I would strongly recommend that the MPI WG chairs be required to be public
> members of the respective Github organization...
>
> Jeff
>
> On Thu, Oct 22, 2015 at 11:16 AM, Bland, Wesley <wesley.bland(a)intel.com>
> wrote:
>
>> Done.
>>
>> On Oct 22, 2015, at 1:11 PM, Jeff Hammond <jeff.science(a)gmail.com> wrote:
>>
>> can someone please add me to https://github.com/mpiwg-rma? i have many
>> tickets to migrate...
>>
>> i cannot see who owns this org to request privately...
>>
>> thanks,
>>
>> jeff
>>
>> --
>> Jeff Hammond
>> jeff.science(a)gmail.com
>> http://jeffhammond.github.io/
>>
>>
>>
>
>
> --
> Jeff Hammond
> jeff.science(a)gmail.com
> http://jeffhammond.github.io/
>
>
>
--
Jeff Hammond
jeff.science(a)gmail.com
http://jeffhammond.github.io/
Or just put their name in the README.md in the rma-issues repo.
On Oct 22, 2015, at 1:27 PM, Jeff Hammond <jeff.science(a)gmail.com<mailto:[email protected]>> wrote:
I would strongly recommend that the MPI WG chairs be required to be public members of the respective Github organization...
Jeff
On Thu, Oct 22, 2015 at 11:16 AM, Bland, Wesley <wesley.bland(a)intel.com<mailto:[email protected]>> wrote:
Done.
On Oct 22, 2015, at 1:11 PM, Jeff Hammond <jeff.science(a)gmail.com<mailto:[email protected]>> wrote:
can someone please add me to https://github.com/mpiwg-rma? i have many tickets to migrate...
i cannot see who owns this org to request privately...
thanks,
jeff
--
Jeff Hammond
jeff.science(a)gmail.com<mailto:[email protected]>
http://jeffhammond.github.io/
--
Jeff Hammond
jeff.science(a)gmail.com<mailto:[email protected]>
http://jeffhammond.github.io/
I would strongly recommend that the MPI WG chairs be required to be public
members of the respective Github organization...
Jeff
On Thu, Oct 22, 2015 at 11:16 AM, Bland, Wesley <wesley.bland(a)intel.com>
wrote:
> Done.
>
> On Oct 22, 2015, at 1:11 PM, Jeff Hammond <jeff.science(a)gmail.com> wrote:
>
> can someone please add me to https://github.com/mpiwg-rma? i have many
> tickets to migrate...
>
> i cannot see who owns this org to request privately...
>
> thanks,
>
> jeff
>
> --
> Jeff Hammond
> jeff.science(a)gmail.com
> http://jeffhammond.github.io/
>
>
>
--
Jeff Hammond
jeff.science(a)gmail.com
http://jeffhammond.github.io/
So Fortran 2015 (TS 18508 - section 6 in the attachment) is going to
support failed images.
The OpenCoarrays folks (who are responsible for enabling GCC 5+ Fortran
coarray support) have started looking into how to support this feature.
They currently use MPI-3 RMA and GASNet as communication runtimes, but the
need to support FT will likely push them in a new direction. The options
they have mentioned thus far are undesirable.
It would be great if there were more people who could help look at RMA FT,
particularly as it pertains to Fortran 2015. Are any of the Fortran WG
folks savvy on how those failures map to MPI concepts and whether or not
the MPI RMA FT discussion is going in the right direction?
Thanks,
Jeff
--
Jeff Hammond
jeff.science(a)gmail.com
http://jeffhammond.github.io/
https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/483
On Mon, Aug 24, 2015 at 8:03 AM, Jim Dinan <james.dinan(a)gmail.com> wrote:
> IIRC, per-window ordering was the intent of the working group and it also
> seems like the only sensible reading of the chapter, given that we allow
> each window to provide a different value for the ordering info key. This
> might just be an erratum, but it would be helpful to create a ticket for it.
>
> On Mon, Aug 10, 2015 at 10:04 AM, Jeff Hammond <jeff.science(a)gmail.com>
> wrote:
>
>> "11.7.2 Ordering" says:
>>
>> "MPI specifies ordering between accumulate operations from one process
>> to the same (or overlapping) memory locations at another process on a
>> per-datatype granularity."
>> This seems to say that ordering is required between overlapping windows,
>> which is a horrible semantic. We need to add a "per-window" caveat here.
>>
>> Later, we talk about overlapping memory regions, rather than locations,
>> which is confusing:
>>
>> "MPI does not provide any guarantees for accesses or updates from
>> different origin processes to overlapping target memory regions."
>> What is a memory region anyways? Is it a window? Is it a set of memory
>> locations?
>>
>> And to be clear, I think I know what we mean in the RMA chapter, but
>> others may not.
>>
>> Jeff
>>
>> --
>> Jeff Hammond
>> jeff.science(a)gmail.com
>> http://jeffhammond.github.io/
>>
>> _______________________________________________
>> mpiwg-rma mailing list
>> mpiwg-rma(a)lists.mpi-forum.org
>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-rma
>>
>
>
> _______________________________________________
> mpiwg-rma mailing list
> mpiwg-rma(a)lists.mpi-forum.org
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-rma
>
--
Jeff Hammond
jeff.science(a)gmail.com
http://jeffhammond.github.io/
