- mpiwg-tools - mailman3.cels.anl.gov

Meeting reminder: Mar 5, 2020 (today)
by Marc-André Hermanns 05 Mar '20

05 Mar '20

Hi everyone, This is a reminder of our regularly scheduled call: March 5 at 8 am Pacific / 11 am Eastern / 5pm CET. Webex Info: https://github.com/mpiwg-tools/mpi-standard/wiki *NOTE*: The WebEx information moved to to a non-public wiki. You have to be logged into Github *and* have to have access to the private Tools WG repositories. If you need access contact me. Agenda: ------- - Errata: Handling of invalid binding arguments https://github.com/mpi-forum/mpi-issues/issues/160 Pending feature discussions: - Next steps for QMPI - Next steps for unique names for MPI_T variables Cheers, Marc-Andre -- Dr. rer. nat. Marc-André Hermanns IT Center Group: High Performance Computing Division: Computational Science and Engineering RWTH Aachen University Seffenter Weg 23 52074 Aachen Phone: +49 241 80-24381 hermanns(a)itc.rwth-aachen.de www.itc.rwth-aachen.de -- Dr. rer. nat. Marc-André Hermanns IT Center Group: High Performance Computing Division: Computational Science and Engineering RWTH Aachen University Seffenter Weg 23 52074 Aachen Phone: +49 241 80-24381 hermanns(a)itc.rwth-aachen.de www.itc.rwth-aachen.de

1 0

Meeting reminder: Feb 27, 2020 (tomorrow)
by Marc-André Hermanns 26 Feb '20

26 Feb '20

Hi everyone, This is a reminder of our regularly scheduled call: February 27 at 8 am Pacific / 11 am Eastern / 5pm CET. Webex Info: https://github.com/mpiwg-tools/mpi-standard/wiki *NOTE*: The WebEx information moved to to a non-public wiki. You have to be logged into Github *and* have to have access to the private Tools WG repositories. If you need access contact me. After a successful face-to-face meeting for the events proposal (passed final vote), we got new topics on our agenda. Agenda: ------- - Errata: MPI_T Session Impact on other sessions https://github.com/mpi-forum/mpi-issues/issues/268 - Errata: Handling of invalid binding arguments https://github.com/mpi-forum/mpi-issues/issues/160 Pending feature discussions: - Next steps for QMPI - Next steps for unique names for MPI_T variables Cheers, Marc-Andre -- Dr. rer. nat. Marc-André Hermanns IT Center Group: High Performance Computing Division: Computational Science and Engineering RWTH Aachen University Seffenter Weg 23 52074 Aachen Phone: +49 241 80-24381 hermanns(a)itc.rwth-aachen.de www.itc.rwth-aachen.de -- Dr. rer. nat. Marc-André Hermanns IT Center Group: High Performance Computing Division: Computational Science and Engineering RWTH Aachen University Seffenter Weg 23 52074 Aachen Phone: +49 241 80-24381 hermanns(a)itc.rwth-aachen.de www.itc.rwth-aachen.de

1 0

MPI Cleanup item for the tools group
by schulzm＠in.tum.de 22 Feb '20

22 Feb '20

Hi Marc-Andre, all, As mentioned in Wesley’s email from a few days ago, Bill went through the entire standard and marked inconsistencies or possible errors. One of them is relevant for tools: https://github.com/mpi-forum/mpi-issues/issues/268 <https://github.com/mpi-forum/mpi-issues/issues/268> Marc-Andre, I assigned you to this ticket (lucky you :) ), but I think we should go though this on an upcoming tools call, as this wording can have larger consequences. Thanks, Martin — Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ) Email: schulzm(a)in.tum.de

1 0

No call today: Feb 13, 2020
by Marc-André Hermanns 13 Feb '20

13 Feb '20

Dear all, as we don't have anything substantial to discuss before the4 face-to-face meeting, we'll skip the meeting today. Cheers Marc-Andre -- Dr. rer. nat. Marc-André Hermanns IT Center Group: High Performance Computing Division: Computational Science and Engineering RWTH Aachen University Seffenter Weg 23 52074 Aachen Phone: +49 241 80-24381 hermanns(a)itc.rwth-aachen.de www.itc.rwth-aachen.de

1 0

No call today (Feb 6, 2020)
by Marc-André Hermanns 06 Feb '20

06 Feb '20

Dear all, sorry for the late notice. As we currently don't have anything to discuss (we'll restart the big topics after the face-to-face), we'll skip the call today. Cheers, Marc-Andre -- Dr. rer. nat. Marc-André Hermanns IT Center Group: High Performance Computing Division: Computational Science and Engineering RWTH Aachen University Seffenter Weg 23 52074 Aachen Phone: +49 241 80-24381 hermanns(a)itc.rwth-aachen.de www.itc.rwth-aachen.de

1 0

Meeting reminder: Jan 30, 2020 (today)
by Marc-André Hermanns 30 Jan '20

30 Jan '20

Hi everyone, This is a reminder of our regularly scheduled call today January 30 at 8 am Pacific / 11 am Eastern / 5pm CET. Webex Info: https://github.com/mpiwg-tools/mpi-standard/wiki *NOTE*: The WebEx information for 2020 changed and is updated in the mpi-standard wiki. You have to be logged into Github *and* have to have access to the private Tools WG repositories. If you need access contact me. Agenda: ------- - What to do with Embiggened(tm) calls - Preparations for Spring meeting. Cheers, Marc-André -- Dr. rer. nat. Marc-André Hermanns IT Center Group: High Performance Computing Division: Computational Science and Engineering RWTH Aachen University Seffenter Weg 23 52074 Aachen Phone: +49 241 80-24381 hermanns(a)itc.rwth-aachen.de www.itc.rwth-aachen.de

1 0

Call cancelled: Jan 23, 2020
by Marc-André Hermanns 23 Jan '20

23 Jan '20

Dear all, sorry, but I will have to cancel for today Jan 23, 2020. The past week has been really busy, so I only got to focus on Tools Chapter issues and I didn't progress on any topic of our current discussion. Cheers, Marc-Andre -- Dr. rer. nat. Marc-André Hermanns IT Center Group: High Performance Computing Division: Computational Science and Engineering RWTH Aachen University Seffenter Weg 23 52074 Aachen Phone: +49 241 80-24381 hermanns(a)itc.rwth-aachen.de www.itc.rwth-aachen.de

1 0

Re: [mpiwg-tools] Embiggening for Tools Chapter
by schulzm＠in.tum.de 21 Jan '20

21 Jan '20

Hi Marc-Andre, Thanks for the starting the discussion - given the fact that we rarely have a variable using more than “1” in the alloc calls, I personally think MPI_Count is overkill. Also, the parameter has a bit of a different nature, as it is an out, i.e., the MPI Library sets it, which makes it IMHO less problematic. I would, therefore, vote for not embiggening MPI_T. Just my 2c, Martin — Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ) Email: schulzm(a)in.tum.de > On 21. Jan 2020, at 08:41, Marc-André Hermanns via mpiwg-tools <mpiwg-tools(a)lists.mpi-forum.org> wrote: > > Dear all, > > (let's use this mailing list for more than just announcements ;-) --- > and please keep Jeff and Martin R. in the loop, as I don't know > whether they [still] subscribe to the list) > > Sorry for being a bit late with this discussion. Today is the deadline > for the Embiggening check through all the chapters, and I finally > finished the tools chapter. > > *TL;DR:* > > The `handle_alloc` functions are the only ones being embiggened. Do > they need to be? Are these enough? > > > *Details below:* > > There we currently see two situations where we have an "Embiggening" > taking place: > > mpi_t_cvar_handle_alloc > mpi_t_pvar_handle_alloc > > With the paramter `count` being a POLYTOOLS_NUM_ELEM, leading to two > additional calls with `_l` suffix where said count is not an `int` but > an `MPI_Count`. > > The description of `count` in both calls is as follows: > "number of elements used to represent this variable > (non-negative integer)" > > I was wondering now: Is this `count` to be an `MPI_Count` necessary? I > am not against it, I just want to make sure we have a strong argument > for it. If we ever have a performance or config variable that in > itself contains more than 2,147,483,647 values (per instance), that > variable in itself might be the performance bottleneck we are trying > to uncover ;-) > > If we argue for having this `count` as an `MPI_Count`, to make things > future proof. What about the calls to > > mpi_t_cvar_get_num > mpi_t_pvar_get_num > > ? > > I do see a difference in defining a single variable with lots of > entries and defining lots of variables with single values, so I am > also not against this distinction. I just want to make sure, we don't > /miss out/ on these call, just because their parameter names are not > `count` but `num_cvars` and `num_pvars`, respectively. > > If we do change these, however, we'd have to update all the calls that > take an `index` value, too, as that `index` is between 0 and > `num_pvar` and `num_cvar`, respectively. And that's basically every > call ;-) > > > So, are we good with how things are defined at the moment? Should we > adapt? In which direction? > > Any thoughts on this? > > Cheers, > Marc-Andre > > -- > Dr. rer. nat. Marc-André Hermanns > > IT Center > Group: High Performance Computing > Division: Computational Science and Engineering > RWTH Aachen University > Seffenter Weg 23 > 52074 Aachen > Phone: +49 241 80-24381 > hermanns(a)itc.rwth-aachen.de > www.itc.rwth-aachen.de > > _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools

1 0

Embiggening for Tools Chapter
by Marc-André Hermanns 21 Jan '20

21 Jan '20

Dear all, (let's use this mailing list for more than just announcements ;-) --- and please keep Jeff and Martin R. in the loop, as I don't know whether they [still] subscribe to the list) Sorry for being a bit late with this discussion. Today is the deadline for the Embiggening check through all the chapters, and I finally finished the tools chapter. *TL;DR:* The `handle_alloc` functions are the only ones being embiggened. Do they need to be? Are these enough? *Details below:* There we currently see two situations where we have an "Embiggening" taking place: mpi_t_cvar_handle_alloc mpi_t_pvar_handle_alloc With the paramter `count` being a POLYTOOLS_NUM_ELEM, leading to two additional calls with `_l` suffix where said count is not an `int` but an `MPI_Count`. The description of `count` in both calls is as follows: "number of elements used to represent this variable (non-negative integer)" I was wondering now: Is this `count` to be an `MPI_Count` necessary? I am not against it, I just want to make sure we have a strong argument for it. If we ever have a performance or config variable that in itself contains more than 2,147,483,647 values (per instance), that variable in itself might be the performance bottleneck we are trying to uncover ;-) If we argue for having this `count` as an `MPI_Count`, to make things future proof. What about the calls to mpi_t_cvar_get_num mpi_t_pvar_get_num ? I do see a difference in defining a single variable with lots of entries and defining lots of variables with single values, so I am also not against this distinction. I just want to make sure, we don't /miss out/ on these call, just because their parameter names are not `count` but `num_cvars` and `num_pvars`, respectively. If we do change these, however, we'd have to update all the calls that take an `index` value, too, as that `index` is between 0 and `num_pvar` and `num_cvar`, respectively. And that's basically every call ;-) So, are we good with how things are defined at the moment? Should we adapt? In which direction? Any thoughts on this? Cheers, Marc-Andre -- Dr. rer. nat. Marc-André Hermanns IT Center Group: High Performance Computing Division: Computational Science and Engineering RWTH Aachen University Seffenter Weg 23 52074 Aachen Phone: +49 241 80-24381 hermanns(a)itc.rwth-aachen.de www.itc.rwth-aachen.de

1 0

No call today: Jan 16, 2020
by Marc-André Hermanns 16 Jan '20

16 Jan '20

Dear all, unfortunately I didn't get to work on specific WG topics this week, so there is no real update to talk about. Therefore, I'd cancel today's meeting. I hope to have updates for next week. Cheers, Marc-Andre -- Dr. rer. nat. Marc-André Hermanns IT Center Group: High Performance Computing Division: Computational Science and Engineering RWTH Aachen University Seffenter Weg 23 52074 Aachen Phone: +49 241 80-24381 hermanns(a)itc.rwth-aachen.de www.itc.rwth-aachen.de

1 0