| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Merge pull request #14523 from bosilca/topic/info-create-env-pre-init info: report only the MPI_INFO_ENV fields that were populated | 3 天前 | |
docs: Note that Open MPI now requires a C11-compliant compiler Signed-off-by: Jeff Squyres <jeff@squyres.com> | 1 年前 | |
docs: Convert Open MPI docs to reStructured Text Convert several Open MPI README/text-like files into reStructured text under the docs/ subdirectory: * README.md * README.FT.ULFM.md * README.JAVA.md * HACKING * LICENSE * NEWS Also converted the Open MPI and OpenSHMEM man pages to RST. This was a lengthy process that involved a zillion intermediate commits. All this work has been squashed down to a single commit for brevity in Git history. Co-authored-by: Harumi Kuno <harumi.kuno@hpe.com> Co-authored-by: Geoffrey Paulsen <gpaulsen@us.ibm.com> Co-authored-by: Aurelien Bouteiller <bouteill@icl.utk.edu> Co-authored-by: George Bosilca <bosilca@icl.utk.edu> Co-authored-by: Joshua Hursey <jhursey@us.ibm.com> Co-authored-by: Brian Barrett <bbarrett@amazon.com> Signed-off-by: Jeff Squyres <jsquyres@cisco.com> | 4 年前 | |
docs: trivial: s/--/|mdash|/ in man pages No other text or content changes. Signed-off-by: Jeff Squyres <jeff@squyres.com> | 2 年前 | |
docs: Move "news" to "changelog" Move the list of changes for each release up under the release notes section, in a new subsection entitled "Changelog". This makes a little more sense than having a standalone "News" section, which was really just a throwback to the old standlaone NEWS text file, anyway. Signed-off-by: Jeff Squyres <jeff@squyres.com> | 2 年前 | |
docs: Convert Open MPI docs to reStructured Text Convert several Open MPI README/text-like files into reStructured text under the docs/ subdirectory: * README.md * README.FT.ULFM.md * README.JAVA.md * HACKING * LICENSE * NEWS Also converted the Open MPI and OpenSHMEM man pages to RST. This was a lengthy process that involved a zillion intermediate commits. All this work has been squashed down to a single commit for brevity in Git history. Co-authored-by: Harumi Kuno <harumi.kuno@hpe.com> Co-authored-by: Geoffrey Paulsen <gpaulsen@us.ibm.com> Co-authored-by: Aurelien Bouteiller <bouteill@icl.utk.edu> Co-authored-by: George Bosilca <bosilca@icl.utk.edu> Co-authored-by: Joshua Hursey <jhursey@us.ibm.com> Co-authored-by: Brian Barrett <bbarrett@amazon.com> Signed-off-by: Jeff Squyres <jsquyres@cisco.com> | 4 年前 | |
Document Open MPI's MPI Forum ABI support Open MPI v6.0.0 adds support for the MPI Forum (standard) ABI defined by MPI-5.0 for C applications, alongside Open MPI's own long-standing ABI. The user-facing documentation did not yet describe this new, separate binary interface: how to build against it, its current limitations, or how it relates to Open MPI's existing ABI-compatibility guarantees. This adds and reorganizes that documentation. High points of the documentation in this commit: * A new "Building MPI applications using the MPI Forum ABI" page (docs/building-apps/mpi-forum-abi.rst) explaining what the MPI Forum ABI is, that it is new in v6.0.0 and distinct from the Open MPI ABI, and its limitations: the application must be dynamically linked, run with a matching launcher, and written in C. * How to build and run standard-ABI C applications with the mpicc_abi wrapper and libmpi_abi -- the wrapper adds the standard ABI header directory ($prefix/include/standard_abi) and links libmpi_abi -- plus the --showme flags and the effect of configuring with --disable-standard-abi. * How to check ABI support at run time with MPI_Abi_get_version, which reports version 1.0 from libmpi_abi but -1, -1 from the normal libmpi, because the normal library uses Open MPI's own ABI rather than the standard ABI. * A clean separation of the two ABIs across the existing pages: the abi-compatibility.rst page is rescoped to the Open MPI ABI and cross-references the new page; version-numbering.rst distinguishes the Open MPI ABI from the MPI Forum ABI and moves its release-series ABI details into abi-compatibility.rst; and both pages state that the two ABIs are not interchangeable. * A "danger" warning that object files or libraries built against different MPI ABIs must not be mixed in one executable, with the concrete unsupported mpicc_abi / mpicc / mpifort combinations and the rule to use one ABI consistently for every MPI-using object. * The intentional decision not to ship a Fortran standard ABI yet (no mpifort_abi wrapper, no libmpifort_abi): a documented wait-and-see approach taken while no other implementation supports the Fortran ABI and the MPI Forum is still converging on it. * Reference documentation for the Open MPI MPI_Abi_* query/helper routines: man pages for MPI_Abi_get_version, MPI_Abi_get_info, MPI_Abi_{get,set}_fortran_booleans, and MPI_Abi_{get,set}_fortran_info describing their Open MPI behavior; the mpicc_abi wrapper in the wrapper-compiler man page; and the standard-ABI configure option in the configure CLI options. * Release-notes and v6.0.x changelog entries announcing MPI-5.0 standard ABI support for C applications and noting the absence of a Fortran ABI wrapper. Signed-off-by: Jeff Squyres <jeff@squyres.com> | 2 个月前 | |
docs: update Intel Omni-Path PSM2 branding to Cornelis Networks Update references to Intel Omni-Path PSM2 in docs to reflect Cornelis Networks ownership of the Omni-Path fabric and PSM2 library. Co-authored-by: Lisa Schupper <lisa.schupper@cornelisnetworks.com> Signed-off-by: Ken Raffenetti <ken.raffenetti@cornelisnetworks.com> | 3 个月前 | |
docs: Convert Open MPI docs to reStructured Text Convert several Open MPI README/text-like files into reStructured text under the docs/ subdirectory: * README.md * README.FT.ULFM.md * README.JAVA.md * HACKING * LICENSE * NEWS Also converted the Open MPI and OpenSHMEM man pages to RST. This was a lengthy process that involved a zillion intermediate commits. All this work has been squashed down to a single commit for brevity in Git history. Co-authored-by: Harumi Kuno <harumi.kuno@hpe.com> Co-authored-by: Geoffrey Paulsen <gpaulsen@us.ibm.com> Co-authored-by: Aurelien Bouteiller <bouteill@icl.utk.edu> Co-authored-by: George Bosilca <bosilca@icl.utk.edu> Co-authored-by: Joshua Hursey <jhursey@us.ibm.com> Co-authored-by: Brian Barrett <bbarrett@amazon.com> Signed-off-by: Jeff Squyres <jsquyres@cisco.com> | 4 年前 | |
Validate peer memheap layouts before remote-key state Remote keys are indexed by the receiver-local segment ordinal. When peer segment layouts differ, the receiver can associate a key with the wrong segment or read beyond the remote payload. Exchange and validate the canonical layout before allocating peer key state or unpacking remote keys, and abort initialization with a clear diagnostic when layouts differ. Signed-off-by: Nathan Bellalou <nbellalou@nvidia.com> | 25 天前 | |
docs: fill in the Platform Notes with a canonical support list The Platform Notes page carried a TODO asking for a canonical list of required 3rd-party package versions, supported run-time systems, and supported OSes/compilers/interconnects. Populate the page with the current data, verified against the build system and the embedded PRRTE: * Required support libraries with minimum versions (from config/autogen_found_items.m4): OpenPMIx >= 4.2.0, PRRTE >= 3.0.0, hwloc >= 2.1.0 and < 3.0.0, Libevent >= 2.0.21; plus the embedded hwloc 2.7.1 and Libevent 2.1.12, and the Perl 5 / Python 3.6+ build requirements. * Note that a C11 (or newer) compiler is now required (enforced by config/opal_setup_cc.m4). * Run-time systems: reorganized, and each entry now describes how PRRTE obtains the allocation and starts processes there and links to the corresponding "Launching with ..." page under docs/launching-apps/. Notably, the LSF entry points at the LSF page, which documents the known problem with the most recent LSF releases and its workaround. Added Flux, which has a PRRTE ras component but no plm, so its allocations are launched via ssh. Grid Engine support was confirmed still present (ras/gridengine); it is now described as the whole Grid Engine family, matching the wording on the Grid Engine page, rather than the stale "OGE 6.1 and 6.2" list. * Added a network-interconnect summary (shared memory, TCP, UCX for InfiniBand/RoCE, Libfabric/OFI networks, and usNIC) that points to the networking tuning pages. * Refreshed the macOS entry, which still listed 14.x/15.x. Our GitHub Actions CI runs on the macos-latest runner, which currently provisions the macos-26-arm64 image (macOS 26.x on Apple silicon), so that is what is now listed as tested. Intel/x86_64 macOS is not covered by CI, so it moves to the lightly-tested list. Also update the tested-compiler list to name the NVIDIA compilers rather than the historical "Portland". Signed-off-by: Jeff Squyres <jeff@squyres.com> | 2 个月前 | |
SQUASHME: Suggestions from Jeff Sq Signed-off-by: Jeff Squyres <jsquyres@cisco.com> | 3 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 3 天前 | ||
| 1 年前 | ||
| 4 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 4 年前 | ||
| 2 个月前 | ||
| 3 个月前 | ||
| 4 年前 | ||
| 25 天前 | ||
| 2 个月前 | ||
| 3 年前 |