On Wed, Mar 15, 2017 at 5:44 PM Jeff Squyres (jsquyres) <jsquy...@cisco.com> wrote:
> 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. > I agree that data is good. Just don't forget that RMA codes are supposed to use alloc_mem and the benefits of registering here are quite clear, unlike the 2-sided case where eager may not need it and rendezvous is able to do on-the-fly easily enough. Ideally, for RMA, alloc_mem can also have an option to use shm, in cases where win_allocate(_shared) isn't a good fit. Jeff > -- > Jeff Squyres > jsquy...@cisco.com > > _______________________________________________ > users mailing list > users@lists.open-mpi.org > https://rfd.newmexicoconsortium.org/mailman/listinfo/users > -- Jeff Hammond jeff.scie...@gmail.com http://jeffhammond.github.io/
_______________________________________________ users mailing list users@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/users
