Hi Vish We talked about this on today’s telecon and people are generally supportive of the concept. However, the feeling was that this will take some thought and fair amount of work to modify mpool and the allocators properly to do this the “right way”.
So people asked if you could come to the Jan devel meeting in Dallas where we could hammer out the right way to integrate this, and maybe parcel out the work? The meeting is detailed here: https://github.com/open-mpi/ompi/wiki <https://github.com/open-mpi/ompi/wiki> Hope you can come! Hope the wedding went well! Ralph > On Nov 18, 2014, at 4:38 PM, Vishwanath Venkatesan <vvenka...@gmail.com> > wrote: > > Hello all, > > I have been working on an implementation for supporting the use of > MPI_Alloc_mem with our new allocator library called memkind > (https://github.com/memkind/ <https://github.com/memkind/>). The memkind > library allows to allocate from different kinds of memory where, kinds > implemented within the library enable the control of NUMA and page size > features. This could be leveraged conveniently with MPI_Alloc_mem. > > I was hoping to trigger the use of the memkind component by using either an > info object or an mca parameter (mpirun -np x --mca mpool memkind ). > The modules of the mpool framework are loaded from components in the btl > framework and not in the base of mpool. But in the case of my implementation, > the component can remain independent from the btl framework. Is there a way > to introduce priority for mpool component selection? > > Also, with the use of info objects in mpool_base_alloc.c, it looks like the > same code path is taken irrespective of whether the info is null or not, as > the branch conditions seem to be commented out. Could this be un-commented or > will there be a different patch for this? > > Please let me know, > Thanks, > Vish > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2014/11/16320.php
