Integration is already in the 2.x branch. The problem is the way we handle the
info key is a bit of a hack. We currently pull out one info key and pass it
down to the mpool as a string. Ideally we want to just pass the info object so
each mpool can define its own info keys. That requires the inf
Hi Jeff,
I don't think it was the use of memkind itself, but a need to refactor the
way Open MPI is using info objects
that was the issue. I don't recall the details.
Howard
2016-11-22 16:27 GMT-07:00 Jeff Hammond :
>
>>
>>1. MPI_ALLOC_MEM integration with memkind
>>
>> It would sense to
>
>
>
>1. MPI_ALLOC_MEM integration with memkind
>
> It would sense to prototype this as a standalone project that is
integrated with any MPI library via PMPI. It's probably a day or two of
work to get that going.
Jeff
--
Jeff Hammond
jeff.scie...@gmail.com
http://jeffhammond.github.io/
___
Hello Folks,
This is a followup to the question posed at the SC’16 Open MPI BOF: Would
the community prefer to have a v2.2.x limited feature but backwards
compatible release sometime in 2017, or would the community prefer a v3.x
(not backwards compatible but potentially more features) sometime in
