Re: [OMPI devel] Patcher on MacOS
I didn't start working on a patch -- all I did was open #5671. > On Sep 28, 2018, at 5:51 PM, Nathan Hjelm via devel > wrote: > > Nope. We just never bothered to disable it on osx. I think Jeff was working > on a patch. > > -Nathan > >> On Sep 28, 2018, at 3:21 PM, Barrett, Brian via devel >> wrote: >> >> Is there any practical reason to have the memory patcher component enabled >> for MacOS? As far as I know, we don’t have any transports which require >> memory hooks on MacOS, and with the recent deprecation of the syscall >> interface, it emits a couple of warnings. It would be nice to crush said >> warnings and the easiest way would be to not build the component. >> >> Thoughts? >> >> Brian >> ___ >> devel mailing list >> devel@lists.open-mpi.org >> https://lists.open-mpi.org/mailman/listinfo/devel > ___ > devel mailing list > devel@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/devel -- Jeff Squyres jsquy...@cisco.com ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
Re: [OMPI devel] Patcher on MacOS
I asked a similar question recently: https://github.com/open-mpi/ompi/issues/5671 > On Sep 28, 2018, at 5:21 PM, Barrett, Brian via devel > wrote: > > Is there any practical reason to have the memory patcher component enabled > for MacOS? As far as I know, we don’t have any transports which require > memory hooks on MacOS, and with the recent deprecation of the syscall > interface, it emits a couple of warnings. It would be nice to crush said > warnings and the easiest way would be to not build the component. > > Thoughts? > > Brian > ___ > devel mailing list > devel@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/devel -- Jeff Squyres jsquy...@cisco.com ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
Re: [OMPI devel] Patcher on MacOS
Nope. We just never bothered to disable it on osx. I think Jeff was working on a patch. -Nathan > On Sep 28, 2018, at 3:21 PM, Barrett, Brian via devel > wrote: > > Is there any practical reason to have the memory patcher component enabled > for MacOS? As far as I know, we don’t have any transports which require > memory hooks on MacOS, and with the recent deprecation of the syscall > interface, it emits a couple of warnings. It would be nice to crush said > warnings and the easiest way would be to not build the component. > > Thoughts? > > Brian > ___ > devel mailing list > devel@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/devel ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
[OMPI devel] Patcher on MacOS
Is there any practical reason to have the memory patcher component enabled for MacOS? As far as I know, we don’t have any transports which require memory hooks on MacOS, and with the recent deprecation of the syscall interface, it emits a couple of warnings. It would be nice to crush said warnings and the easiest way would be to not build the component. Thoughts? Brian ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
[OMPI devel] Announcing Open MPI v4.0.0rc3
The Third release candidate for Open MPI v4.0.0 (rc3) has been built and is available at: https://www.open-mpi.org/software/ompi/v4.0/ Only one News worth difference from v4.0.0rc2:- Fix a problem with ORTE not reporting error messages if an application terminated normally but exited with non-zero error code. Thanks to Emre Brookes for reporting - OSHMEM updated to the OpenSHMEM 1.4 API.- Do not build Open SHMEM layer when there are no SPMLs available. Currently, this means the Open SHMEM layer will only build if a MXM or UCX library is found.- A UCX BTL was added for enhanced MPI RMA support using UCX- With this release, OpenIB BTL now only supports iWarp and RoCE by default.- Updated internal HWLOC to 2.0.1- Updated internal PMIx to 3.0.1- Change the priority for selecting external verses internal HWLOC and PMIx packages to build. Starting with this release, configure by default selects available external HWLOC and PMIx packages over the internal ones.- Updated internal ROMIO to 3.2.1.- Removed support for the MXM MTL.- Removed support for SCIF.- Improved CUDA support when using UCX.- Enable use of CUDA allocated buffers for OMPIO.- Improved support for two phase MPI I/O operations when using OMPIO.- Added support for Software-based Performance Counters, see https://github.com/davideberius/ompi/wiki/How-to-Use-Software-Based-Performance-Counters-(SPCs)-in-Open-MPI- Various improvements to MPI RMA performance when using RDMA capable interconnects.- Update memkind component to use the memkind 1.6 public API.- Fix problems with use of newer map-by mpirun options. Thanks to Tony Reina for reporting.- Fix rank-by algorithms to properly rank by object and span- Allow for running as root of two environment variables are set. Requested by Axel Huebl.- Fix a problem with building the Java bindings when using Java 10. Thanks to Bryce Glover for reporting.- Fix a problem with ORTE not reporting error messages if an application terminated normally but exited with non-zero error code. Thanks to Emre Brookes for reporting. ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
Re: [OMPI devel] Mac OS X 10.4.x users?
Even *I* don't attempt to support OS X that old. :wink: -Paul On Fri, Sep 28, 2018 at 11:41 AM Jeff Squyres (jsquyres) via devel < devel@lists.open-mpi.org> wrote: > Fun fact: we cause configure to fail for OS X <= 10.4 anyway: > > https://github.com/open-mpi/ompi/blob/master/configure.ac#L328-L347 > > According to the comment, we do this because of a known-bad implementation > of pty in the OS X kernel that causes kernel panics. > > So I think we're definitely safe removing a OS X 10.4.x workaround. > > > > On Sep 28, 2018, at 2:18 PM, Ralph H Castain wrote: > > > > Good lord - break away!! > > > >> On Sep 28, 2018, at 11:11 AM, Barrett, Brian via devel < > devel@lists.open-mpi.org> wrote: > >> > >> All - > >> > >> In trying to clean up some warnings, I noticed one (around pack/unpack > in net/if.h) that is due to a workaround of a bug in MacOS X 10.4.x and > earlier. The simple way to remove the warning would be to remove the > workaround, which would break the next major version of Open MPI on 10.4.x > and earlier on 64 bit systems. 10.5.x was released 11 years ago and didn’t > drop support for any 64 bit systems. I posted a PR which removes support > for 10.4.x and earlier (through the README) and removes the warning > generated workaround (https://github.com/open-mpi/ompi/pull/5803). > >> > >> Does anyone object to breaking 10.4.x and earlier? > >> > >> Brian > >> ___ > >> devel mailing list > >> devel@lists.open-mpi.org > >> https://lists.open-mpi.org/mailman/listinfo/devel > > > > ___ > > devel mailing list > > devel@lists.open-mpi.org > > https://lists.open-mpi.org/mailman/listinfo/devel > > > -- > Jeff Squyres > jsquy...@cisco.com > > ___ > devel mailing list > devel@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/devel -- Paul H. Hargrove Computer Languages & Systems Software (CLaSS) Group Computer Science Department Lawrence Berkeley National Laboratory ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
Re: [OMPI devel] Mac OS X 10.4.x users?
Fun fact: we cause configure to fail for OS X <= 10.4 anyway: https://github.com/open-mpi/ompi/blob/master/configure.ac#L328-L347 According to the comment, we do this because of a known-bad implementation of pty in the OS X kernel that causes kernel panics. So I think we're definitely safe removing a OS X 10.4.x workaround. > On Sep 28, 2018, at 2:18 PM, Ralph H Castain wrote: > > Good lord - break away!! > >> On Sep 28, 2018, at 11:11 AM, Barrett, Brian via devel >> wrote: >> >> All - >> >> In trying to clean up some warnings, I noticed one (around pack/unpack in >> net/if.h) that is due to a workaround of a bug in MacOS X 10.4.x and >> earlier. The simple way to remove the warning would be to remove the >> workaround, which would break the next major version of Open MPI on 10.4.x >> and earlier on 64 bit systems. 10.5.x was released 11 years ago and didn’t >> drop support for any 64 bit systems. I posted a PR which removes support >> for 10.4.x and earlier (through the README) and removes the warning >> generated workaround (https://github.com/open-mpi/ompi/pull/5803). >> >> Does anyone object to breaking 10.4.x and earlier? >> >> Brian >> ___ >> devel mailing list >> devel@lists.open-mpi.org >> https://lists.open-mpi.org/mailman/listinfo/devel > > ___ > devel mailing list > devel@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/devel -- Jeff Squyres jsquy...@cisco.com ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
Re: [OMPI devel] Mac OS X 10.4.x users?
Good lord - break away!! > On Sep 28, 2018, at 11:11 AM, Barrett, Brian via devel > wrote: > > All - > > In trying to clean up some warnings, I noticed one (around pack/unpack in > net/if.h) that is due to a workaround of a bug in MacOS X 10.4.x and earlier. > The simple way to remove the warning would be to remove the workaround, > which would break the next major version of Open MPI on 10.4.x and earlier on > 64 bit systems. 10.5.x was released 11 years ago and didn’t drop support for > any 64 bit systems. I posted a PR which removes support for 10.4.x and > earlier (through the README) and removes the warning generated workaround > (https://github.com/open-mpi/ompi/pull/5803). > > Does anyone object to breaking 10.4.x and earlier? > > Brian > ___ > devel mailing list > devel@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/devel ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
[OMPI devel] Mac OS X 10.4.x users?
All - In trying to clean up some warnings, I noticed one (around pack/unpack in net/if.h) that is due to a workaround of a bug in MacOS X 10.4.x and earlier. The simple way to remove the warning would be to remove the workaround, which would break the next major version of Open MPI on 10.4.x and earlier on 64 bit systems. 10.5.x was released 11 years ago and didn’t drop support for any 64 bit systems. I posted a PR which removes support for 10.4.x and earlier (through the README) and removes the warning generated workaround (https://github.com/open-mpi/ompi/pull/5803). Does anyone object to breaking 10.4.x and earlier? Brian ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
