Regarding having jemalloc sources inside memkind, we do not think that disabling such behavoiur is a good idea. Memkind is using unstable jemalloc's API, so we cannot guarentee how memkind libary would behave in case of changes of jemalloc. Also, we are testing memkind with specific jemalloc version (currently 5.0) and we cannot guarantee performance results with different version of jemalloc. Would it be possible to treat memkind as exception?
Since memkind 1.7 was recently released, could this request be updated to enable memkind 1.7 in 18.04? /github. com/memkind/ memkind/ releases/ tag/v1. 7.0
Memkind 1.7 can be found at https:/
Regarding having jemalloc sources inside memkind, we do not think that disabling such behavoiur is a good idea. Memkind is using unstable jemalloc's API, so we cannot guarentee how memkind libary would behave in case of changes of jemalloc. Also, we are testing memkind with specific jemalloc version (currently 5.0) and we cannot guarantee performance results with different version of jemalloc. Would it be possible to treat memkind as exception?