Comment 18 for bug 1637546

Jeff,
As I wrote in Comment 11 (https://bugs.launchpad.net/intel/+bug/1637546/comments/11), memkind has a copy of jemalloc 5.0 in its sources. This internally used jemalloc is hidden inside memkind library (its symbols are not exported outside). Memkind is also using jemallocs unstable API, which might change or even be removed in future versions of jemalloc. Changes in jemalloc could have a big impact on performance and library stability, so we decided to have its copy inside memkind library.
Generally, memkind does not require external jemalloc and it is also not providing API to internally used jemalloc.
Regards,
Paweł