Hi Jeff,
One of my earlier replies includes the backtraces of cp2k.popt process and the problem points to MPI_ALLOC_MEM/MPI_FREE_MEM. https://mail-archive.com/users@lists.open-mpi.org/msg30587.html If that part of the code is commented out, is there another way for openmpi to find that backtrace? --Jingchao ________________________________ From: users <users-boun...@lists.open-mpi.org> on behalf of Jeff Squyres (jsquyres) <jsquy...@cisco.com> Sent: Wednesday, March 15, 2017 6:42:44 PM To: Open MPI User's List Subject: Re: [OMPI users] openib/mpi_alloc_mem pathology On Mar 15, 2017, at 8:25 PM, Jeff Hammond <jeff.scie...@gmail.com> wrote: > > I couldn't find the docs on mpool_hints, but shouldn't there be a way to > disable registration via MPI_Info rather than patching the source? Yes; that's what I was thinking, but wanted to get the data point first. Specifically: if this test works (i.e., commenting out the de/registration avoids the slowdown), there's at least two things we devs should consider: 1. Disable the entire de/registration code path for ALLOC/FREE_MEM (e.g., perhaps the lazy method is just better, anyway). 2. Provide an MCA param to disable the de/registration code path for ALLOC/FREE_MEM. Let's see how the test goes. -- Jeff Squyres jsquy...@cisco.com _______________________________________________ users mailing list users@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/users
_______________________________________________ users mailing list users@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/users
