- announce - mailman3.cels.anl.gov

Announcing the availability of MPICH 3.3.1
by Raffenetti, Kenneth J. 07 Jun '19

07 Jun '19

A new stable of MPICH, 3.3.1, is now available for download. This is the first bug-fix release in the 3.3.x series. All production environments are encouraged to upgrade. The MPICH 3.3.x series contains a new (non-default) device layer implementation – CH4. CH4 is designed for low software overheads to better exploit next-generation hardware. CH4 supports the OFI (http://libfabric.org) and UCX (http://openucx.org) libraries for network communication. Building support for both can be done as follows: ./configure --with-device=ch4:ofi,ucx An environment variable is used for runtime netmod selection. MPIR_CVAR_CH4_NETMOD=ofi or MPIR_CVAR_CH4_NETMOD=ucx CH4 is experimental, meaning there are known build issues and bugs, but most tests and common benchmarks will complete on 64-bit Linux systems. You can find the release on our downloads page (www.mpich.org/downloads) Regards, The MPICH team =============================================================================== Changes in 3.3.1 =============================================================================== # Fix bug in MPI_Testany/MPI_Waitany that could cause deadlock # Add missing functionality in Argobots library support # Fix configure-time detection for thread local storage support # Better support for reproducible builds. Thanks to Bernhard Wiedemann for the report and fixes # Fix support for XL compiler toolchain # Add support for -static-intel linking option # Fix building on systems without weak symbols # Fix several static analysis and compiler warnings A full list of changes is available at the following link: http://git.mpich.org/mpich.git/shortlog/v3.3..v3.3.1

1 0

Announcing the availability of MPICH 3.3
by Raffenetti, Kenneth J. 21 Nov '18

21 Nov '18

A new stable of MPICH, 3.3, is now available for download. This is the first stable release in the 3.3 series. All production environments are encouraged to upgrade. MPICH 3.3 contains a new (non-default) device layer implementation – CH4. CH4 is designed for low software overheads to better exploit next-generation hardware. CH4 supports the OFI (http://libfabric.org) and UCX (http://openucx.org) libraries for network communication. Building support for both can be done as follows: ./configure --with-device=ch4:ofi,ucx An environment variable is used for runtime netmod selection. MPIR_CVAR_CH4_NETMOD=ofi or MPIR_CVAR_CH4_NETMOD=ucx CH4 is experimental, meaning there are known build issues and bugs, but most tests and common benchmarks will complete on 64-bit Linux systems. You can find the release on our downloads page (www.mpich.org/downloads) Regards, The MPICH team =============================================================================== Changes in 3.3 =============================================================================== # CH4 Device: A new device layer implementation designed for low software overheads. CH4 has experimental support for OFI and UCX network libraries, and POSIX shared memory. Thanks to Intel, Mellanox, and RIKEN AICS for participating in the CH4 coding effort. # Fixed SLURM integration in Hydra for new node list format. # Added support for PMIx (https://pmix.github.io/pmix/) client library in CH4 netmods. Note that you must use a compatible PMIx server in this configuration. # Better organization of collectives in the MPI layer. The new scheme, which de-couples implementation from selection logic, enables easier integration of additional algorithms. # TSP collectives framework: A C++-template style framework for collective algorithms is added to allow single collective implementation to move data over generic or device-specific transport functions. # Improvements to derived datatype testing (DTPools - https://wiki.mpich.org/mpich/index.php/DTPools) # Added new "non-catastrophic" error codes to expose internal resource exhaustion. # Added info hints to MPI_Comm_split_type to support splitting communicators by machine topology. Both on-node (socket, core, etc.) and off-node (switch-level) hints are defined. # Improvements to MPI_THREAD_MULTIPLE in CH4 through new thread safety models at the Virtual Network Interface (VNI) level. This introduces two new models that leverage work-queues to offload operations and improve scalability under contention. # Message Driven Thread Activation (MDTA). An alternative locking model is defined for MPI_THREAD_MULTIPLE in CH4. # Added PMI usage optimizations for business card exchange in CH4 netmods. # Improvements on MPI_Abort. MPI_Abort invoked on subcommunicators will only abort the connected processes within that communicator. # Cleanup of whitespace (ch3 excluded) using the maint/code-cleanup.sh script. For instructions on how to update PRs/branches based on MPICH before the cleanup, see https://github.com/pmodels/mpich/wiki/Code-Cleanup-Procedure. # Removed the PAMI device and poe PMI client. # C99 compiler support is now required to build MPICH. # Several other minor bug fixes, memory leak fixes, and code cleanup. A full list of changes is available at the following link: http://git.mpich.org/mpich.git/shortlog/v3.2..v3.3 A list of bugs that have been fixed is available at the following link: https://github.com/pmodels/mpich/milestone/25?closed=1

1 0

Announcing the availability of OSHMPI 2.0b1
by Si, Min 11 Nov '18

11 Nov '18

We are pleased to announce the beta release of OSHMPI-2.0 (version 2.0b1), a portable OpenSHMEM implementation on top of MPI. It contains several key features. http://www.mcs.anl.gov/project/oshmpi/downloads/ A list of features: - Full support of OpenSHMEM 1.4 specification. - Function inline for all OSHMPI internal routines. - Caching internal MPI communicators for collective operations with PE active set. - OpenSHMEM multithreading safety support. - Active message support of OpenSHMEM atomic operations. MPI accumulates cannot be directly used because MPI does not guarantee atomicity between different reduce operations. - Optional asynchronous progress thread support for active message based atomic. Details of each feature can be found in CHANGES (https://github.com/pmodels/oshmpi/blob/master/CHANGES) Regards, The OSHMPI Team

1 0

Announcing the availability of MPICH 3.3rc1
by Raffenetti, Kenneth J. 09 Nov '18

09 Nov '18

A new release candidate of MPICH, 3.3rc1, is now available for download. MPICH 3.3 contains a new (non-default) device layer implementation – CH4. CH4 is designed for low software overheads to better exploit next-generation hardware. An OFI (http://libfabric.org) or UCX (http://openucx.org) library is required to build CH4. Example configure lines: ./configure --with-device=ch4:ofi --with-libfabric=<path/to/ofi/install> ./configure --with-device=ch4:ucx --with-ucx=<path/to/ucx/install> CH4 is still experimental, meaning there are known build issues and bugs, but most tests and common benchmarks will complete on 64-bit Linux systems. Since 3.3b3, there have been more stability improvements, bug fixes, and code cleanup. Also new are improvements to MPI_THREAD_MULTIPLE in CH4 through new thread safety models at the Virtual Network Interface (VNI) level. This introduces two new models that leverage work-queues to offload operations and improve scalability under contention. You can find the release on our downloads page (www.mpich.org/downloads) Regards, The MPICH team =============================================================================== Changes in 3.3 =============================================================================== # CH4 Device: A new device layer implementation designed for low software overheads. CH4 has experimental support for OFI and UCX network libraries, and POSIX shared memory. Thanks to Intel, Mellanox, and RIKEN AICS for participating in the CH4 coding effort. # Fixed SLURM integration in Hydra for new node list format. # Added support for PMIx (https://pmix.github.io/pmix/) client library in CH4 netmods. Note that you must use a compatible PMIx server in this configuration. # Better organization of collectives in the MPI layer. The new scheme, which de-couples implementation from selection logic, enables easier integration of additional algorithms. # TSP collectives framework: A C++-template style framework for collective algorithms is added to allow single collective implementation to move data over generic or device-specific transport functions. # Improvements to derived datatype testing (DTPools - https://wiki.mpich.org/mpich/index.php/DTPools) # Added new "non-catastrophic" error codes to expose internal resource exhaustion. # Added info hints to MPI_Comm_split_type to support splitting communicators by machine topology. Both on-node (socket, core, etc.) and off-node (switch-level) hints are defined. # Improvements to MPI_THREAD_MULTIPLE in CH4 through new thread safety models at the Virtual Network Interface (VNI) level. This introduces two new models that leverage work-queues to offload operations and improve scalability under contention. # Message Driven Thread Activation (MDTA). An alternative locking model is defined for MPI_THREAD_MULTIPLE in CH4. # Added PMI usage optimizations for business card exchange in CH4 netmods. # Improvements on MPI_Abort. MPI_Abort invoked on subcommunicators will only abort the connected processes within that communicator. # Cleanup of whitespace (ch3 excluded) using the maint/code-cleanup.sh script. For instructions on how to update PRs/branches based on MPICH before the cleanup, see https://github.com/pmodels/mpich/wiki/Code-Cleanup-Procedure. # Removed the PAMI device and poe PMI client. # C99 compiler support is now required to build MPICH. # Several other minor bug fixes, memory leak fixes, and code cleanup. A full list of changes is available at the following link: http://git.mpich.org/mpich.git/shortlog/v3.2..v3.3rc1 A list of bugs that have been fixed is available at the following link: https://github.com/pmodels/mpich/milestone/25?closed=1

1 0

Announcing the availability of MPICH 3.3b3
by Kenneth Raffenetti 29 Jun '18

29 Jun '18

A new preview release of MPICH, 3.3b3, is now available for download. MPICH 3.3 contains a new (non-default) device layer implementation – CH4. CH4 is designed for low software overheads to better exploit next-generation hardware. An OFI (http://libfabric.org) or UCX (http://openucx.org) library is required to build CH4. Example configure lines: ./configure --with-device=ch4:ofi --with-libfabric=<path/to/ofi/install> ./configure --with-device=ch4:ucx --with-ucx=<path/to/ucx/install> CH4 is still in beta stages, meaning there are known build issues and bugs, but most tests and common benchmarks will complete on 64-bit Linux systems. Since 3.3b2, there have been more stability improvements, bug fixes, and code cleanup. PMIx client library support is added in CH4 to support launching with a compatible PMIx server. Also in this release is a reorganization of MPI collectives to make it easier to integrate new algorithms. A new framework is added to enable collective algorithms on either generic or device-specific functionality using a C++-template style system. Support is added for creating communicators based on hardware and network topology hints, and SLURM integration in Hydra is updated to work with the latest node list format. You can find the release on our downloads page (www.mpich.org/downloads) Regards, The MPICH team =============================================================================== Changes in 3.3 =============================================================================== # CH4 Device: A new device layer implementation designed for low software overheads. CH4 has experimental support for OFI and UCX network libraries, and POSIX shared memory. Thanks to Intel, Mellanox, and RIKEN AICS for participating in the CH4 coding effort. # Added support for splitting communicators based on hardware topology using info hints. # Fixed SLURM integration in Hydra for new node list format. # Added support for PMIx (https://pmix.github.io/pmix/) client library in CH4 netmods. Note that you must use a compatible PMIx server in this configuration. # Better organization of collectives in the MPI layer. The new scheme, which de-couples implementation from selection logic, enables easier integration of additional algorithms. # TSP collectives framework: A C++-template style framework for collective algorithms is added to allow single collective implementation to move data over generic or device-specific transport functions. # Improvements to derived datatype testing (DTPools - https://wiki.mpich.org/mpich/index.php/DTPools) # Added new "non-catastrophic" error codes to expose internal resource exhaustion. # Added info hints to MPI_Comm_split_type to support splitting communicators by machine topology. Both on-node (socket, core, etc.) and off-node (switch-level) hints are defined. # Message Driven Thread Activation (MDTA). An alternative locking model is defined for MPI_THREAD_MULTIPLE in CH4. # Added PMI usage optimizations for business card exchange in CH4 netmods. # Improvements on MPI_Abort. MPI_Abort invoked on subcommunicators will only abort the connected processes within that communicator. ` # Cleanup of whitespace (ch3 excluded) using the maint/code-cleanup.sh script. For instructions on how to update PRs/branches based on MPICH before the cleanup, see https://github.com/pmodels/mpich/wiki/Code-Cleanup-Procedure. # Removed the PAMI device and poe PMI client. # Several other minor bug fixes, memory leak fixes, and code cleanup. A full list of changes is available at the following link: http://git.mpich.org/mpich.git/shortlog/v3.2..v3.3b3 A list of bugs that have been fixed is available at the following link: https://github.com/pmodels/mpich/milestone/25?closed=1

1 0

Argonne Spam Quarantine Notification
by Argonne Anti Spam Quarantine 19 Apr '18

19 Apr '18

++ Note: This message has been sent by a notification only system. Please do not reply ++ IronPort Spam Quarantine Notification If a spam message was missed, or if a message was incorrectly flagged as spam, you can add the sender to a personal safelist or blocklist via the quarantine. Senders on the safelist will not be flagged as spam, and senders on the blocklist will be automatically quarantined. For more information, visit: https://wiki.inside.anl.gov/inside/Ironport_Anti-Spam_Appliances/Documentat… The message(s) below have been quarantined by the Argonne National Laboratory spam filtering system. There are 1 new messages in your Email Quarantine since you received your last Spam Quarantine Notification. If the messages below are spam, you do not need to take any action. Messages will be automatically deleted from the quarantine after 28 day(s). If any of the messages below are not spam, click the 'Release' link to have them sent to your Inbox. Messages that have been correctly flagged as spam do not need to be reported. ----------- New Quarantine Messages --------------- Message 1 From: christine.scott(a)gsuitebox.com Subject: *****SPAM*****Microsoft Azure Accounts Install Base. Date: 18 Apr 2018 Release: http://mailgateway.anl.gov:8080/Message?action=Release&mid=186313858&h=85bc… --------------------------------------------------- To manage your quarantine please visit the URL below: http://mailgateway.anl.gov:8080/Search?h=aacab4ab8a12e5980c61ca5dc10eded7&e… If you have any questions regarding the Laboratory spam filtering product, please contact the CIS helpdesk at help(a)anl.gov or x-9999 option 2.

1 0

Re: [mpich-announce] Announcing the availability of MPICH 3.3b2
by Kenneth Raffenetti 10 Apr '18

10 Apr '18

Correction: the original subject line stated the wrong version number. Today's release is 3.3b2. On 04/10/2018 09:45 AM, Kenneth Raffenetti wrote: > A new preview release of MPICH, 3.3b2, is now available for download. > MPICH 3.3 contains a new (non-default) device layer implementation – > CH4. CH4 is designed for low software overheads to better exploit > next-generation hardware. An OFI (http://libfabric.org) or UCX > (http://openucx.org) library is required to build CH4. Example configure > lines: > > ./configure --with-device=ch4:ofi --with-libfabric=<path/to/ofi/install> > ./configure --with-device=ch4:ucx --with-ucx=<path/to/ucx/install> > > CH4 is still in beta stages, meaning there are known build issues and > bugs, but most tests and common benchmarks will complete on 64-bit Linux > systems. Since 3.3b1, there have been more stability improvements, bug > fixes, and code cleanup. PMIx client library support is added in CH4 to > support launching with a compatible PMIx server. > > Also in this release is a reorganization of MPI collectives to make it > easier to integrate new algorithms. A new framework is added to enable > collective algorithms on either generic or device-specific functionality > using a C++-template style system. Support is added for creating > communicators based on hardware topology hints, and SLURM integration in > Hydra is updated to work with the latest node list format. You can find > the release on our downloads page (www.mpich.org/downloads) > > Regards, > The MPICH team > > =============================================================================== > > Changes in 3.3 > =============================================================================== > > > # CH4 Device: A new device layer implementation designed for low software > overheads. CH4 has experimental support for OFI and UCX network > libraries, > and POSIX shared memory. Thanks to Intel, Mellanox, and RIKEN AICS for > participating in the CH4 coding effort. > > # Added support for splitting communicators based on hardware > topology using info hints. > > # Fixed SLURM integration in Hydra for new node list format. > > # Added support for PMIx (https://pmix.github.io/pmix/) client > library in CH4 netmods. Note that you must use a compatible PMIx > server in this configuration. > > # Better organization of collectives in the MPI layer. The new > scheme, which de-couples implementation from selection logic, > enables easier integration of additional algorithms. > > # TSP collectives framework: A C++-template style framework for > collective algorithms is added to allow single collective > implementation to move data over generic or device-specific > transport functions. > > # Improvements to derived datatype testing (DTPools - > https://wiki.mpich.org/mpich/index.php/DTPools) > > # Added new "non-catastrophic" error codes to expose internal > resource exhaustion. > > # Cleanup of whitespace (ch3 excluded) using the > maint/code-cleanup.sh script. For instructions on how to update > PRs/branches based on MPICH before the cleanup, see > https://github.com/pmodels/mpich/wiki/Code-Cleanup-Procedure. > > # Removed the PAMI device and poe PMI client. > > # Several other minor bug fixes, memory leak fixes, and code cleanup. > > A full list of changes is available at the following link: > > http://git.mpich.org/mpich.git/shortlog/v3.2..v3.3b2 > > A list of bugs that have been fixed is available at the following > link: > > https://github.com/pmodels/mpich/milestone/32?closed=1 > > _______________________________________________ > announce mailing list announce(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/announce

1 0

Announcing the availability of MPICH 3.3b1
by Kenneth Raffenetti 10 Apr '18

10 Apr '18

A new preview release of MPICH, 3.3b2, is now available for download. MPICH 3.3 contains a new (non-default) device layer implementation – CH4. CH4 is designed for low software overheads to better exploit next-generation hardware. An OFI (http://libfabric.org) or UCX (http://openucx.org) library is required to build CH4. Example configure lines: ./configure --with-device=ch4:ofi --with-libfabric=<path/to/ofi/install> ./configure --with-device=ch4:ucx --with-ucx=<path/to/ucx/install> CH4 is still in beta stages, meaning there are known build issues and bugs, but most tests and common benchmarks will complete on 64-bit Linux systems. Since 3.3b1, there have been more stability improvements, bug fixes, and code cleanup. PMIx client library support is added in CH4 to support launching with a compatible PMIx server. Also in this release is a reorganization of MPI collectives to make it easier to integrate new algorithms. A new framework is added to enable collective algorithms on either generic or device-specific functionality using a C++-template style system. Support is added for creating communicators based on hardware topology hints, and SLURM integration in Hydra is updated to work with the latest node list format. You can find the release on our downloads page (www.mpich.org/downloads) Regards, The MPICH team =============================================================================== Changes in 3.3 =============================================================================== # CH4 Device: A new device layer implementation designed for low software overheads. CH4 has experimental support for OFI and UCX network libraries, and POSIX shared memory. Thanks to Intel, Mellanox, and RIKEN AICS for participating in the CH4 coding effort. # Added support for splitting communicators based on hardware topology using info hints. # Fixed SLURM integration in Hydra for new node list format. # Added support for PMIx (https://pmix.github.io/pmix/) client library in CH4 netmods. Note that you must use a compatible PMIx server in this configuration. # Better organization of collectives in the MPI layer. The new scheme, which de-couples implementation from selection logic, enables easier integration of additional algorithms. # TSP collectives framework: A C++-template style framework for collective algorithms is added to allow single collective implementation to move data over generic or device-specific transport functions. # Improvements to derived datatype testing (DTPools - https://wiki.mpich.org/mpich/index.php/DTPools) # Added new "non-catastrophic" error codes to expose internal resource exhaustion. # Cleanup of whitespace (ch3 excluded) using the maint/code-cleanup.sh script. For instructions on how to update PRs/branches based on MPICH before the cleanup, see https://github.com/pmodels/mpich/wiki/Code-Cleanup-Procedure. # Removed the PAMI device and poe PMI client. # Several other minor bug fixes, memory leak fixes, and code cleanup. A full list of changes is available at the following link: http://git.mpich.org/mpich.git/shortlog/v3.2..v3.3b2 A list of bugs that have been fixed is available at the following link: https://github.com/pmodels/mpich/milestone/32?closed=1

1 0

Announcing the availability of MPICH 3.3b1
by Kenneth Raffenetti 05 Feb '18

05 Feb '18

A new preview release of MPICH, 3.3b1, is now available for download. MPICH 3.3 contains a new (non-default) device layer implementation – CH4. CH4 is designed for low software overheads to better exploit next-generation hardware. An OFI (http://libfabric.org) or UCX (http://openucx.org) library is required to build CH4. Example configure lines: ./configure --with-device=ch4:ofi --with-libfabric=<path/to/ofi/install> ./configure --with-device=ch4:ucx --with-ucx=<path/to/ucx/install> CH4 is still in beta stages, meaning there are known build issues and bugs, but most tests and common benchmarks will complete on 64-bit Linux systems. Since 3.3a3, there have been more stability improvements, bug fixes, and code cleanup. Also in this release is a reorganization of MPI collectives to make it easier to integrate new algorithms. A new framework is added to enable collective algorithms on either generic or device-specific functionality using a C++-template style system. Support is added for creating communicators based on hardware topology hints, and SLURM integration in Hydra is updated to work with the latest node list format. You can find the release on our downloads page (www.mpich.org/downloads) Regards, The MPICH team =============================================================================== Changes in 3.3 =============================================================================== # CH4 Device: A new device layer implementation designed for low software overheads. CH4 has experimental support for OFI and UCX network libraries, and POSIX shared memory. Thanks to Intel, Mellanox, and RIKEN AICS for participating in the CH4 coding effort. # Added support for splitting communicators based on hardware topology using info hints. # Fixed SLURM integration in Hydra for new node list format. # Better organization of collectives in the MPI layer. The new scheme, which de-couples implementation from selection logic, enables easier integration of additional algorithms. # TSP collectives framework: A C++-template style framework for collective algorithms is added to allow single collective implementation to move data over generic or device-specific transport functions. # Cleanup of whitespace (ch3 excluded) using the maint/code-cleanup.sh script. For instructions on how to update PRs/branches based on MPICH before the cleanup, see https://github.com/pmodels/mpich/wiki/Code-Cleanup-Procedure. # Removed the PAMI device and poe PMI client. # Several other minor bug fixes, memory leak fixes, and code cleanup. A full list of changes is available at the following link: http://git.mpich.org/mpich.git/shortlog/v3.2..v3.3b1 A list of bugs that have been fixed is available at the following link: https://github.com/pmodels/mpich/milestone/25?closed=1

1 0

Announcing the availability of MPICH 3.3a3
by Kenneth Raffenetti 21 Dec '17

21 Dec '17

A new preview release of MPICH, 3.3a3, is now available for download. MPICH 3.3 contains a new (non-default) device layer implementation – CH4. CH4 is designed for low software overheads to better exploit next-generation hardware. An OFI (http://libfabric.org) or UCX (http://openucx.org) library is required to build CH4. Example configure lines: ./configure --with-device=ch4:ofi --with-libfabric=<path/to/ofi/install> ./configure --with-device=ch4:ucx --with-ucx=<path/to/ucx/install> CH4 is still in alpha stages, meaning there are known build issues and bugs, but most tests and common benchmarks will complete on 64-bit Linux systems. Since 3.3a2, there have been more stability improvements, bug fixes, and code cleanup. Also in this release is a reorganization of MPI collectives to make it easier to integrate new algorithms. Support is added for creating communicators based on hardware topology hints, and SLURM support in Hydra is updated to work with the latest node list format. You can find the release on our downloads page. Regards, The MPICH team =============================================================================== Changes in 3.3 =============================================================================== # CH4 Device: A new device layer implementation designed for low software overheads. CH4 has experimental support for OFI and UCX network libraries, and POSIX shared memory. Thanks to Intel, Mellanox, and RIKEN AICS for participating in the CH4 coding effort. # Added support for splitting communicators based on hardware topology using info hints. # Fixed SLURM integration in Hydra for new node list format. # Better organization of collectives in the MPI layer. The new scheme, which decouples implementation from selection logic, enables easier integration of additional algorithms. # Removed the PAMI device and poe PMI client. # Several other minor bug fixes, memory leak fixes, and code cleanup. A full list of changes is available at the following link: http://git.mpich.org/mpich.git/shortlog/v3.2..v3.3a3 A list of bugs that have been fixed is available at the following link: https://github.com/pmodels/mpich/milestone/25?closed=1

1 0