[OMPI devel] Updated prrte submodule on "main" branch

https://github.com/open-mpi/ompi/pull/12449 has just been merged, meaning that the PRRTE git submodule on Open MPI's main branch now points to the Open MPI fork of PRRTE, not the upstream/community PRRTE. You will either need to get a new github clone to pick up the new submodule change, or

Re: [OMPI devel] Github Action to auto-close stale/abandoned Github Issues

_____ From: Jeff Squyres (jsquyres) Sent: Tuesday, February 13, 2024 12:15 PM To: Open MPI Developers Subject: Github Action to auto-close stale/abandoned Github Issues Looking for feedback on auto-closing Github Issues: https://github.com/open-mpi/ompi/pull/12329. The rough idea is: 1. OMPI

[OMPI devel] Github Action to auto-close stale/abandoned Github Issues

Looking for feedback on auto-closing Github Issues: https://github.com/open-mpi/ompi/pull/12329. The rough idea is: 1. OMPI community member puts the "State: Awaiting User Information" label on a Github Issue (this does not apply to PRs) 2. If there's no reply in X=14 days, the bot will

[OMPI devel] Tuesday Webex meeting schedule

Here's the schedule for our next few weekly Webex meetings: * December 26, 2023: canceled (happy holidays!) * January 2, 2024: canceled (happy holidays!) * January 9, 2024: first meeting of 2024 There is a new Webex link for the 2024 meetings; it has been published the developer

[OMPI devel] Open MPI BOF at SC'23

We're excited to see everyone next week in Denver, Colorado, USA at SC23! Open MPI will be hosting our usual State of the Union Birds of a Feather (BOF) session on Wednesday, 15, November, 2023, from 12:15-1:15pm US Mountain

[OMPI devel] Fw: MPI 4.1 Published

FYI. From: mpi-forum on behalf of Martin Schulz via mpi-forum Sent: Friday, November 3, 2023 7:26 AM To: Pritchard Jr., Howard via mpi-forum Subject: [Mpi-forum] MPI 4.1 Published Dear MPI Forum Community, For all of you who could not join us yesterday, I

Re: [OMPI devel] Question about the future of C++ API support

The C++ bindings were removed from the MPI-3.0 standard in 2012 -- they've been officially deleted for 12 years. The MPI Forum talked extensively with users about this before removing them. We held on to the C++ bindings here in Open MPI for a long time, but finally deleted them in 5.0.0. Do

Re: [OMPI devel] Asking for a letter of support

I see that you also emailed MPICH with the same question. I'll reply with more-or-less the same response: I am not a lawyer, and this is not legal advice, but Open MPI has a very permissive license (see the LICENSE file); you should be able to use it in your research without any letter of

Re: [OMPI devel] MPI ABI effort

To: Open MPI Developers Cc: Jeff Squyres (jsquyres) Subject: Re: [OMPI devel] MPI ABI effort LANL would be interested in supporting this feature as well. Howard On Mon, Aug 28, 2023 at 9:58 AM Jeff Squyres (jsquyres) via devel mailto:devel@lists.open-mpi.org>> wrote: We got a presentatio

Re: [OMPI devel] MPI ABI effort

We got a presentation from the ABI WG (proxied via Quincey from AWS) a few months ago. The proposal looked reasonable. No one has signed up to do the work yet, but based on what we saw in that presentation, the general consensus was "sure, we could probably get on board with that." There's

[OMPI devel] Open MPI 4.1.6rc1 release candidate posted

There have been enough minor fixes to warrant a 4.1.6 release. We've posted 4.1.6rc1 tarballs in the usual location: https://www.open-mpi.org/software/ompi/v4.1/ Changes since v4.1.5: * Update to properly handle PMIx v>=4.2.3. Thanks to Bruno Chareyre, Github user @sukanka, and

Re: [OMPI devel] 32 bit issues (was: 32 bit support needs a maintainer)

support. From: Jeff Squyres (jsquyres) Sent: Tuesday, February 7, 2023 4:07 PM To: Yatindra Vaishnav ; Open MPI Developers Subject: 32 bit issues (was: 32 bit support needs a maintainer) Just try to build Open PMIx -- by itself, not as embedded in Open MPI -- in 32

Re: [OMPI devel] 5.0.x bug release blockers hard stop

This seems like an odd stance to take. You're basically saying "Damn the torpedoes, full speed ahead." Or, put differently, "I don't care what the bug is, unless it's data corruption, we're not calling it a blocker." Technically, that means that I could merge a PR that removes configure.ac,

Re: [OMPI devel] 32 bit issues (was: 32 bit support needs a maintainer)

ink/?LinkId=550986> for Windows From: Jeff Squyres (jsquyres)<mailto:jsquy...@cisco.com> Sent: Monday, February 13, 2023 10:21 AM To: Yatindra Vaishnav<mailto:yatindr...@hotmail.com>; Open MPI Developers<mailto:devel@lists.open-mpi.org> Subject: Re: 32 bit issues (w

Re: [OMPI devel] 32 bit issues (was: 32 bit support needs a maintainer)

, 2023 11:58 AM To: Open MPI Developers ; Jeff Squyres (jsquyres) Subject: RE: 32 bit issues (was: 32 bit support needs a maintainer) Hi Jeff, Did you get a chance to look at the issue I shared? Is it the same issue? I fixed all compilation issues in PMIx. Once you let me know I’ll do

Re: [OMPI devel] 32 bit issues (was: 32 bit support needs a maintainer)

Be sure to see https://github.com/open-mpi/ompi/pull/11282#issuecomment-1421523518. From: Jeff Squyres (jsquyres) Sent: Tuesday, February 7, 2023 4:07 PM To: Yatindra Vaishnav ; Open MPI Developers Subject: 32 bit issues (was: 32 bit support needs a maintainer

[OMPI devel] 32 bit issues (was: 32 bit support needs a maintainer)

will need to remove that check in order to be able to compile Open PMIx in 32 bit mode. From: Yatindra Vaishnav Sent: Tuesday, February 7, 2023 4:02 PM To: Open MPI Developers ; Jeff Squyres (jsquyres) Subject: RE: [OMPI devel] 32 bit support needs a maintainer Hi Je

Re: [OMPI devel] 32 bit support needs a maintainer

to get Open MPI v5.0.0 out for quite a while, and seem to actually be getting closer to getting over the finish line. So getting these fixes in sooner rather than later would be better. From: Yatindra Vaishnav Sent: Monday, February 6, 2023 2:56 PM To: Jeff S

Re: [OMPI devel] 32 bit support needs a maintainer

VMs to do bug fixes and testing. I already have a server machine which I can help with. Get Outlook for iOS<https://aka.ms/o0ukef> From: Jeff Squyres (jsquyres) Sent: Monday, February 6, 2023 7:45 AM To: devel@lists.open-mpi.org Cc: Yatindra Vaishnav S

Re: [OMPI devel] 32 bit support needs a maintainer

Greetings Yatindra; thanks for responding. Just curious: are you replying in response to the discussion that just came up a few days ago on https://github.com/open-mpi/ompi/pull/11282, where we set the upcoming Open MPI v5.0's configure script to abort in 32-bit environments? I.e., are you

[OMPI devel] 32 bit support needs a maintainer

OMPI Developers -- Per https://github.com/open-mpi/ompi/pull/11282, the plan for Open MPI v5.0.x is to no longer support 32-bit builds. configure will abort the build if it detects that sizeof(void*)==4. The reason for this is that there is no one maintaining (or testing) 32 bit builds.

Re: [OMPI devel] How do you generate your FAQ pages?

Are you asking about the old FAQ at https://www.open-mpi.org/faq/? Or are you asking about the new docs for the upcoming v5.0.x (and beyond) at https://docs.open-mpi.org/? The old FAQ is basically hand-written PHP. When we started the FAQ, we couldn't find any suitable tools/libraries to do a

[OMPI devel] No Tuesday meeting on 22 Nov

Due to the US Thanksgiving holiday week, we will not have the regular weekly Tuesday Open MPI webex next Tuesday (22 Nov). -- Jeff Squyres jsquy...@cisco.com

[OMPI devel] Regularly scheduled Open MPI webex next Tuesday

Gentle reminder: even though SC is occurring next week, we'll still have the regular Tuesday Open MPI webex on 15 Nov (at the regular time -- 11am US Eastern -- and with the regular Webex link). -- Jeff Squyres jsquy...@cisco.com

Re: [OMPI devel] Fwd: --mca btl_base_verbose 30 not working in version 5.0

Sorry; I missed that this email came in a week ago.  The "btl_base_verbose" MCA param only works on the BTL components. The Linux "hostname(1)" command is not an MPI application, and therefore does not utilize any of the BTL components. Hence, you can set btl_base_verbose to whatever you

[OMPI devel] Github CI change on "main"

We made a change to the github actions CI on "main" this morning. If your PR is stuck waiting for the "Check Commits" CI to run (i.e., it just shows a yellow dot and doesn't change), please rebase your PR to the HEAD of main, and then that CI should run. Sorry for the hassle! -- Jeff Squyres

Re: [OMPI devel] Component configure change proposal

My vote: yes, let's remove this functionality. -- Jeff Squyres jsquy...@cisco.com From: devel on behalf of Barrett, Brian via devel Sent: Tuesday, September 6, 2022 2:25 PM To: Open MPI Developers Cc: Barrett, Brian Subject: [OMPI devel] Component configure

[OMPI devel] Open MPI Java MPI bindings

During a planning meeting for Open MPI v5.0.0 today, the question came up: is anyone using the Open MPI Java bindings? These bindings are not​ official MPI Forum bindings -- they are an Open MPI-specific extension. They were added a few years ago as a result of a research project. We ask

Re: [OMPI devel] How to progress MPI_Recv using custom BTL for NIC under development

x protocol (not sure which kind of network connection they are using in that phase), receiving "local" data instead of the remote ones, but I just started debugging this, maybe I could open a new thread specific on this. Michele Il 03/08/22 15:43, Jeff Squyres (jsquyres) ha scrit

Re: [OMPI devel] How to progress MPI_Recv using custom BTL for NIC under development

Sorry for the huge delay in replies -- it's summer / vacation season, and I think we (as a community) are a little behind in answering some of these emails. :-( It's been quite a while since I have been in the depths of BTL internals; I'm afraid I don't remember the details offhand. When I

Re: [OMPI devel] Rationale behind memcpy chunk size (in smsc/xpmem)

Sorry for the delay in replies -- it's summer / vacation season, and I think we (as a community) are a little behind in answering some of these emails. :-( It's hard to say for any given machine, but a bunch of different hardware factors can come into play, such as: - L1, L2, L3 cache sizes -

[OMPI devel] Passing of an MPI luminary: Rusty Lusk

In case you had not heard, Dr. Ewing "Rusty" Lusk passed away at age 78 last week. Rusty was one of the founders and prime movers of the entire MPI ecosystem: the MPI Forum, the MPI standard, and MPICH. Without Rusty, our community would not exist. In addition to all of that, he was an

Re: [OMPI devel] What PMIx version(s) does v5.0.0 and main support?

To: Jeff Squyres (jsquyres) via devel Cc: Austen W Lauria Subject: [OMPI devel] What PMIx version(s) does v5.0.0 and main support? There is a question as to what PMIx versions OMPI supports, specifically with respect to v5.0.0 and main. This came to our attention where a user tried to build OMPI v5

Re: [OMPI devel] RDMA and OMPI implementation

In UCX's case, the choice is almost entirely driven by the UCX library. You'll need to look at the UCX code and/or ask NVIDIA. -- Jeff Squyres jsquy...@cisco.com From: Masoud Hemmatpour Sent: Thursday, April 21, 2022 7:57 AM To: Jeff Squyres (jsquyres

Re: [OMPI devel] RDMA and OMPI implementation

that will drive the choice of whether any individual network transfer actually uses RDMA or not. -- Jeff Squyres jsquy...@cisco.com From: Masoud Hemmatpour Sent: Thursday, April 21, 2022 2:38 AM To: Open MPI Developers Cc: Jeff Squyres (jsquyres) Subject

Re: [OMPI devel] RDMA and OMPI implementation

Let me add a little more color to William's response. The general theme is: it depends on what the underlying network provides. Some underlying networks natively support one-sided operations like PUT / WRITE and GET / READ (e.g., IB/RDMA, RoCE/RDMA, ... etc.). Some don't (like TCP). Open MPI

Re: [OMPI devel] Open MPI source RPM / specfile

lf Of Jeff Squyres (jsquyres) via devel Sent: Friday, April 1, 2022 11:29 AM To: Open MPI Developers Cc: Jeff Squyres (jsquyres) Subject: [OMPI devel] Open MPI source RPM / specfile Open question to the developer community: is anyone using the Open MPI SRPM that we release?

[OMPI devel] Open MPI source RPM / specfile

Open question to the developer community: is anyone using the Open MPI SRPM that we release? Related question: is anyone using the RPM specfile and/or scripts in contrib for building Open MPI RPMs? I ask for a specific reason: we just realized we broke the RPM stuff when updating the v5.0.x

Re: [OMPI devel] Renaming Open MPI's git "master" branch

has been created: https://www.open-mpi.org/nightly/main/ Please let us know if you have any questions or problems. -- Jeff Squyres jsquy...@cisco.com From: Jeff Squyres (jsquyres) Sent: Friday, March 25, 2022 10:46 AM To: Open MPI Developers Subject: Re:

Re: [OMPI devel] Renaming Open MPI's git "master" branch

Gentle reminder that Brian and I will start this change in about 15 minutes. -- Jeff Squyres jsquy...@cisco.com From: Jeff Squyres (jsquyres) Sent: Tuesday, March 22, 2022 12:30 PM To: Open MPI Developers Subject: Re: Renaming Open MPI's git "m

Re: [OMPI devel] Script-based wrapper compilers

Gilles -- Do you know if anyone is actually cross compiling? I agree that this is in the "nice to have" category, but it is costing Brian time -- if no one is using this functionality, it's not worth the time. If people are using this functionality, then it's potentially worth the time. --

Re: [OMPI devel] Renaming Open MPI's git "master" branch

folder, however -- we're not going to maintain the old name for very long. In general, we don't plan to support many behind-the-scenes master --> main remappings to allow people to continue to use the old "master" name. We'd rather people actually updated to the new name. Please let

[OMPI devel] Renaming Open MPI's git "master" branch

This is a bit overdue, but we're finally getting to this. We are planning to rename Open MPI's git "master" branch to "main" one week from today: Friday, 25 Mar, 2022. Brian and I will handle most of the logistics of this change, but there will likely be a little disruption for developers.

[OMPI devel] First Open MPI v5.0.x docs have been merged

Our first cut of the ReStructured Text (RST)/Sphinx HTML docs and man pages have been committed to master -- woo hoo! There's a few things the developer community needs to know. Web site The docs are now live on https://docs.open-mpi.org (hosted by readthedocs.io). Right now, there's just

Re: [OMPI devel] install from source

<https://drive.google.com/file/d/13893ncYRx7j0jxrchkXnpWzF-VinuFkF/view?usp=sharing> Thanks! On Mon, Nov 15, 2021 at 5:26 PM Jeff Squyres (jsquyres) mailto:jsquy...@cisco.com>> wrote: Sorry for the delay -- I was out late last week. Unfortunately, this tarball contains

Re: [OMPI devel] install from source

sp=sharing> Thank you again, On Fri, Nov 5, 2021 at 5:59 PM Jeff Squyres (jsquyres) mailto:jsquy...@cisco.com>> wrote: Can you send all the information listed here: https://www.open-mpi.org/community/help/ On Nov 5, 2021, at 12:33 PM, Masoud Hemmatpour via devel mailto:dev

Re: [OMPI devel] install from source

Can you send all the information listed here: https://www.open-mpi.org/community/help/ On Nov 5, 2021, at 12:33 PM, Masoud Hemmatpour via devel mailto:devel@lists.open-mpi.org>> wrote: Sorry, This is my configure: ./configure --prefix=/home/me/src_cx/ompi/install-debug/

[OMPI devel] Coverity run from last night

We finally fixed the Coverity run yesterday, and it ran last night for the first time in a little while. As usual, a bunch of useless items came up, but some legit-looking issues also came up. The following component owners should probably look at the Coverity report from last night: -

[OMPI devel] Open MPI 5.0.0: drop support for gcc 4.4.7?

All -- Unless someone has a strong reason for keeping support for GCC 4.4.7 (i.e., the default GCC compiler that shipped in RHEL 6), Open MPI is going to drop support for it in v5.0.0. The reason for this is that PRTE and PMIX no longer compile successfully with GCC 4.4.7 (and Open MPI gets a

[OMPI devel] Annual Open MPI repo access audit

The following organizations need to respond to the annual Open MPI access audit ASAP: • AWS • HPE • Intel • NVIDIA • RIST Please see Slack or contact me for the URL where to complete your section of the audit. Thanks. -- Jeff Squyres jsquy...@cisco.com

Re: [OMPI devel] Help us find good times for design discussions.

To close the loop on this for the mail archives: we settled in dates/times. Please see the wiki for more details, and to add your own items to the agenda: https://github.com/open-mpi/ompi/wiki/Meeting-2021-07 On Jul 5, 2021, at 11:58 AM, Geoffrey Paulsen via devel

Re: [OMPI devel] C style rules / reformatting

ncrustify/issues/3173 [3] https://github.com/uncrustify/uncrustify/issues/3174 On 5/17/21 9:59 PM, Jeff Squyres (jsquyres) via devel wrote: FYI: It was decided last week that we will abandon the current effort to reformat master / v5.0.x according to style rules. SHORT VERSION We have already reforma

Re: [OMPI devel] [jonathan...@systex.com: A question about Open MPI logo]

Greetings Chris! Thanks for bringing this to our attention. The short version is that we're pretty permissive with our logo -- e.g., follow the same terms as our code license (BSD), and everything should be fine. I'll reply directly to the original author. I believe that Brian Barrett and I

Re: [OMPI devel] C style rules / reformatting

d a few different “sets” of defaults depending on what you prefer. Let me know if you have any questions. I’d be happy to provide any pointers. Thanks, Wes On May 17, 2021, at 2:59 PM, Jeff Squyres (jsquyres) via devel mailto:devel@lists.open-mpi.org>> wrote: FYI: It was decided last week that we w

[OMPI devel] C style rules / reformatting

FYI: It was decided last week that we will abandon the current effort to reformat master / v5.0.x according to style rules. SHORT VERSION We have already reformatted opal/ and tests/. But the two PRs for reformatting ompi/ brought up a whole bunch of issues that do not seem resolvable via

Re: [OMPI devel] NVIDIA 'nvfortran' cannot link libmpi_usempif08.la

Filed https://github.com/open-mpi/ompi/issues/8919. FWIW, Open MPI is on GitHub, not GitLab. On May 4, 2021, at 9:55 AM, Paul Kapinos via devel mailto:devel@lists.open-mpi.org>> wrote: JFYI: the sane issue is also in Open MPI 4.1.1. I cannot open an Gitlab issue due to lack of account(*) so I

Re: [OMPI devel] inconsistency of behaviour and description of "openmpi-4.1.0$ ./configure --with-pmix=external ... "

Yes, that does feel weird. I've filed https://github.com/open-mpi/ompi/issues/8829 to track the issue. On Apr 19, 2021, at 6:42 AM, Paul Kapinos via devel mailto:devel@lists.open-mpi.org>> wrote: Dear Open MPI developer, The help for ./configure in openmpi-4.1.0 says (see also below): >

Re: [OMPI devel] Remove stale OPAL dss and opal_tree code

On Feb 18, 2021, at 10:55 AM, Ralph Castain via devel mailto:devel@lists.open-mpi.org>> wrote: I'm planning on removing the OPAL dss (pack/unpack) code as part of my work to reduce the code base I historically supported. The pack/unpack functionality is now in PMIx (has been since v3.0 was

Re: [OMPI devel] Support for AMD M100?

other side of the PCI bus. On Feb 11, 2021, at 1:02 PM, Heinz, Michael William mailto:michael.william.he...@cornelisnetworks.com>> wrote: Pretty much, yeah. From: Jeff Squyres (jsquyres) mailto:jsquy...@cisco.com>> Sent: Thursday, February 11, 2021 12:58 PM To: Open MPI Developers List m

Re: [OMPI devel] Support for AMD M100?

On Feb 11, 2021, at 12:23 PM, Heinz, Michael William via devel mailto:devel@lists.open-mpi.org>> wrote: Has the subject of supporting AMD’s new GPUs come up? We’re discussing supporting it in PSM2 but it occurred to me that that won’t help much if higher-level APIs don’t support it, too… You

[OMPI devel] Github Actions: cherry-pick commit message checker

I talked about this PR on the webex today: https://github.com/open-mpi/ompi/pull/8431 Comments / feedback would be welcome. Unless I hear objections, I plan to merge this on master COB tomorrow (10 Feb 2021). Thanks! -- Jeff Squyres jsquy...@cisco.com

Re: [OMPI devel] configure problem on master

Which library? On Feb 5, 2021, at 4:46 PM, Gabriel, Edgar via devel mailto:devel@lists.open-mpi.org>> wrote: I just noticed another ‘new’ aspect of configure on master. The sharedfp/sm component is now not compiled anymore, I double checked that it is still correctly detected and handled on

Re: [OMPI devel] How to build Open MPI so the UCX used can be changed at runtime?

On Jan 27, 2021, at 7:19 PM, Gilles Gouaillardet wrote: > > What I meant is the default Linux behavior is to first lookup dependencies in > the rpath, and then fallback to LD_LIBRARY_PATH > *unless* -Wl,--enable-new-dtags was used at link time. > > In the case of Open MPI,

Re: [OMPI devel] How to build Open MPI so the UCX used can be changed at runtime?

On Jan 27, 2021, at 2:00 AM, Gilles Gouaillardet via devel mailto:devel@lists.open-mpi.org>> wrote: Tim, a simple option is to configure ... LDFLAGS="-Wl,--enable-new-dtags" If Open MPI is built with this option, then LD_LIBRARY_PATH takes precedence over rpath (the default is the opposite

[OMPI devel] Open MPI 4.1.0rc4

We're getting close: 4.1.0rc4 is now available. https://www.open-mpi.org/software/ompi/v4.1/ The list of things left before v4.1.0 is final is getting very, very short. Changes since rc3: - Configury fixes for macOS Big Sur - Minor one-sided RDMA performance improvements - Fix OSHMEM

[OMPI devel] Open MPI documentation

Over the past few months, I've been musing about Open MPI's documentation. Short version = For v5.0.0, I propose: 1. Move the README to reStructured Text ("RST"), and split it up into multiple pages. * Use Sphinx (https://www.sphinx-doc.org/en/master/) to render this RST into

[OMPI devel] Continued Open MPI mailing lists instability

Over the past month or so, you may have noticed that sometimes mails you sent to the Open MPI mailing lists were delayed, sometimes by multiple days. Our mailing list provider has been experiencing technical difficulties in keeping the Open MPI mailing lists flowing. They tell us that they had

[OMPI devel] Change in OMPI component build behavior on master (i.e., what will become v5.0)

Folks -- It's worth pointing out https://github.com/open-mpi/ompi/pull/8132. This PR will change Open MPI's behavior from building all components as DSOs to including them in the core Open MPI libraries. The motivation for this change is to decrease filesystem activity upon job start. Dlopen

[OMPI devel] Delays in Open MPI mailing list

FYI: We've been having some problems with our mailing list provider over the past few weeks. No mails have been lost, but sometimes mails queue up endlessly at our mailing list provider until a human IT staffer goes in, fixes a problem, and effectively releases all the mails that have queued

Re: [OMPI devel] UCX and older hardwre

Looks like Yossi replied: https://github.com/open-mpi/ompi/issues/7968#issuecomment-713738841 He said the fix has been included in the UCX 1.9.0 release. On Oct 21, 2020, at 10:38 AM, Barrett, Brian via devel mailto:devel@lists.open-mpi.org>> wrote: UCX folks - As part of

[OMPI devel] Hwloc debug output in default mpirun on master

On master, it looks like there's somehow some default hwloc debugging information enabled by default. For example: - $ hostname mpi002 $ mpirun hostname hwloc verbose debug enabled, may be disabled with HWLOC_DEBUG_VERBOSE=0 in the environment. CPU phase discovery... CPU phase discovery in

Re: [OMPI devel] [EXTERNAL] Which compiler versions to test?

On Oct 8, 2020, at 9:59 PM, Baker, Lawrence M wrote: > > The PGI/nVidia compiler suite is free now and could become more significant > in the ARM world, now that nVidia has acquired ARM. We use PGI on our > cluster, along with the others you support. Yes, quite probably true. NVIDIA is

Re: [OMPI devel] Which compiler versions to test?

On Oct 8, 2020, at 9:40 PM, Gilles Gouaillardet via devel wrote: > > On RHEL 8.x, the default gcc compiler is 8.3.1, so I think it is worth > testing. Excellent point. > Containers could be used to setup a RHEL 8.x environment (so not only > gcc but also third party libs such as libevent and

[OMPI devel] Which compiler versions to test?

Open question to the Open MPI dev community... Over time, the size of my MTT cluster has been growing smaller (due to hardware failure, power budget restrictions, etc.). This means that I have far fewer CPU cycles available for testing various compilers and configure CLI options than I used

[OMPI devel] New public Open MPI test repo

One of the topics we discussed today was having a public git repo for Open MPI community tests. A few community members wanted to have tests that were written with public funding to be public. A very fair point. (Recall: we have a private repo that is only available to Open MPI core

[OMPI devel] August virtual developer meeting

The dates/times for the August 2020 developer virtual meeting have been decided: Monday-Tuesday, August 10-11, 2020 • 8am-11am US Pacific time • 11am-2pm US Eastern time • 3-6pm UTC • 5-8pm CEST More information is on the wiki. Please start adding agenda items:

[OMPI devel] The ABCs of Open MPI (parts 1 and 2): slides + videos posted

The slides and videos for parts 1 and 2 of the online seminar presentation "The ABCs of Open MPI" have been posted on both the Open MPI web site and the EasyBuild wiki: https://www.open-mpi.org/video/?category=general

Re: [OMPI devel] [Open MPI Announce] Online presentation: the ABCs of Open MPI

ild-Tech-Talks-I:-Open-MPI Anyone is free to join either / both parts. Hope to see you this Wednesday! On Jun 14, 2020, at 2:05 PM, Jeff Squyres (jsquyres) via announce mailto:annou...@lists.open-mpi.org>> wrote: In conjunction with the EasyBuild community, Ralph Castain (Intel, Open

Re: [OMPI devel] [Open MPI Announce] Online presentation: the ABCs of Open MPI

! > On Jun 14, 2020, at 2:05 PM, Jeff Squyres (jsquyres) via announce > wrote: > > In conjunction with the EasyBuild community, Ralph Castain (Intel, Open MPI, > PMIx) and Jeff Squyres (Cisco, Open MPI) will host an online presentation > about Open MPI on **Wednesday June 24th 2020

[OMPI devel] Online presentation: the ABCs of Open MPI

In conjunction with the EasyBuild community, Ralph Castain (Intel, Open MPI, PMIx) and Jeff Squyres (Cisco, Open MPI) will host an online presentation about Open MPI on **Wednesday June 24th 2020** at: - 11am US Eastern time - 8am US Pacific time - 3pm UTC - 5pm CEST The general scope of the

Re: [OMPI devel] Running data collection for collectives tuning (slurm option included)

I tweaked your scripts a bunch so that I could run a bunch of different variations on my cluster. I have lots of jobs queued up (I have 29 nodes in my cluster -- 3 have died over time); they'll take a bunch of time to execute. JOBID PARTITION NAME USER ST TIME NODES

Re: [OMPI devel] MPI_Info args to spawn - resolving deprecated values?

On Apr 8, 2020, at 9:51 AM, Ralph Castain via devel wrote: > > We have deprecated a number of cmd line options (e.g., bynode, npernode, > npersocket) - what do we want to do about their MPI_Info equivalents when > calling comm_spawn? > > Do I silently convert them? Should we output a

[OMPI devel] Threads MCA framework

If anyone wants to comment on the new threads MCA framework, now's the time: https://github.com/open-mpi/ompi/pull/6578 I.e., functionality-wise, it looks ready to merge (to me). -- Jeff Squyres jsquy...@cisco.com

Re: [OMPI devel] Adding a new RAS module

Some logistics for you: - As Ralph mentioned, the ORTE code effectively moved to GitHub.com/openpmix/prrte - That code is now referenced in the Open MPI code base via a git submodule in the top-level "prrte" directory - This is on master only (which is the best

[OMPI devel] Github reviews now required on master

As we discussed last week in the face-to-face Portland meeting, and we re-affirmed this morning on the Webex, reviews are now required on master pull requests. We used to only require reviews on release branches, but in an effort to spread some knowledge about the code base around, we're now

Re: [OMPI devel] Deprecated configure options in OMPI v5

On Feb 19, 2020, at 1:31 PM, Ralph Castain via devel wrote: > > What do we want to do with the following options? These have either been > renamed (changing from "orte..." to a "prrte" equivalent) or are no longer > valid: > > --enable-orterun-prefix-by-default >

Re: [OMPI devel] ORTE has been removed!

On Feb 8, 2020, at 3:30 PM, Ralph Castain via devel wrote: > > FYI: pursuant to the objectives outline last year, I have committed PR #7202 > and removed ORTE from the OMPI repository. It has been replaced with a PRRTE > submodule pointed at the PRRTE master branch. At the same tie, we

Re: [OMPI devel] Fix your MTT scripts!

On Feb 9, 2020, at 10:14 AM, Ralph Castain via devel wrote: > > We are seeing many failures on MTT because of errors on the cmd line. Note > that by request of the OMPI community, PRRTE is strictly enforcing the Posix > "dash" syntax: > > * a single-dash must be used only for

Re: [OMPI devel] Git submodules are coming

On Feb 7, 2020, at 4:27 AM, Brice Goglin via devel wrote: > > PR#7367 was initially on top of PR #7366. When Jeff merged PR#7366, I rebased > my #7367 with git prrs and got this error: > > $ git prrs origin master > From > https://github.com/open-mpi/ompi > > * branch

[OMPI devel] 3.1.6rc2: Cygwin fifo warning (was: v3.0.6rc2 and v3.1.6rc2 available for testing)

On Feb 2, 2020, at 2:17 AM, Marco Atzeri via devel wrote: > > not a new issue as it was also in 3.1.5. what is causing the > last line of warning ? > And why a simple run should try to run a debugger ? > > $ mpirun -n 4 ./hello_c > ... > Hello, world, I am 3 of 4, (Open MPI v3.1.6rc2, package:

[OMPI devel] v3.0.6rc2 and v3.1.6rc2 available for testing

Minor updates since rc1: 3.0.6rc2 and 3.1.6rc2: - Fix run-time linker issues with OMPIO on newer Linux distros. 3.1.6rc2 only: - Fix issue with zero-length blockLength in MPI_TYPE_INDEXED. Please test: https://www.open-mpi.org/software/ompi/v3.0/

[OMPI devel] Open MPI v3.1.6rc1 released

(I know you just got a very similar email -- but that was for ***3.0.6rc1*** -- this email is for ***3.1.6rc1***) This may well be the end of the line for the v3.1.x series. Please test v3.1.6rc1: https://www.open-mpi.org/software/ompi/v3.1/ Changes since v3.1.5: - Fix PMIX dstore

[OMPI devel] Open MPI v3.0.6rc1 released

We keep threatening to have a last release in the v3.0.x series. v3.0.6 may well be it! Please test v3.0.6rc1: https://www.open-mpi.org/software/ompi/v3.0/ Changes since v3.0.5: - Allow the user to override modulefile_path in the Open MPI SRPM, even if install_in_opt is set to 1. -

Re: [OMPI devel] [EXTERNAL] Git submodules are coming

--tjn _ Thomas Naughton naught...@ornl.gov<mailto:naught...@ornl.gov> Research Associate (865) 576-4184 On Tue, 7 Jan 2020, Jeff Squyres (jsquyres) via devel wrote: We now have two

Re: [OMPI devel] Git submodules are coming

d the second will replace ORTE with PRRTE. On Jan 7, 2020, at 9:02 AM, Jeff Squyres (jsquyres) via devel mailto:devel@lists.open-mpi.org>> wrote: We now have two PRs pending that will introduce the use of Git submodules (and there are probably more such PRs on the way). At last one of th

Re: [OMPI devel] Git submodules are coming

directory name? By the way, in https://github.com/open-mpi/ompi/wiki/GitSubmodules#updating-the-commit-that-a-submodule-refers-to you may want to rename hwloc201 into hwloc2 to avoid confusion and match the current PR. Brice (who cannot edit the wiki :)) Le 07/01/2020 à 18:02, Jeff Squyres

[OMPI devel] Git submodules are coming

We now have two PRs pending that will introduce the use of Git submodules (and there are probably more such PRs on the way). At last one of these first two PRs will likely be merged "Real Soon Now". We've been talking about using Git submodules forever. Now we're just about ready.

Re: [OMPI devel] PMIX ERROR: INIT spurious message on 3.1.5

file (the pmix one - should be named >> pmix-mca-params.conf). >> Artem - any advice here? >>> On Dec 25, 2019, at 9:56 AM, Marco Atzeri via devel >>> wrote: >>> >>> I have no multinode around for testing >>> >>> I will need

Re: [OMPI devel] PMIX ERROR: INIT spurious message on 3.1.5

That actually looks like a legit error -- it's failing to initialize a shared mutex. I'm not sure what the consequence is of this failure, though, since the job seemed to run ok. Are you able to run multi-node jobs ok? > On Dec 22, 2019, at 1:20 AM, Marco Atzeri via devel > wrote: > > Hi

[OMPI devel] Cisco's MTT testing to be shut down for the holidays

Cisco will be disabling its MTT testing this evening for our holiday company-wide shutdown. I'll resume our MTT testing in January. -- Jeff Squyres jsquy...@cisco.com

  1   2   3   4   5   6   7   8   9   10   >