[
https://issues.apache.org/jira/browse/MNEMONIC-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17560832#comment-17560832
]
Wang, Gang commented on MNEMONIC-748:
-------------------------------------
h3. libvmem
The *libvmem* library turns a pool of persistent memory into a volatile memory
pool, similar to the system heap but kept separate and with its own
malloc-style API.
See the [libvmem page|https://pmem.io/vmem/libvmem] for updates
{quote}*Note:* Since persistent memory support has been integrated into
[libmemkind|https://github.com/memkind/memkind], that library is the
*recommended* choice for any new volatile usages, since it combines support for
multiple types of volatile memory into a single, convenient API.
{quote}
> A new memory service of Memkind
> -------------------------------
>
> Key: MNEMONIC-748
> URL: https://issues.apache.org/jira/browse/MNEMONIC-748
> Project: Mnemonic
> Issue Type: New Feature
> Components: Memory-Service
> Affects Versions: 0.18.0
> Reporter: Wang, Gang
> Priority: Minor
>
> [https://memkind.github.io/memkind/]
> The kinds of memory are defined by operating system memory policies that have
> been applied to virtual address ranges. Memory characteristics supported by
> memkind without user extension include control of NUMA and page size
> features. The jemalloc non-standard interface has been extended to enable
> specialized arenas to make requests for virtual memory from the operating
> system through the memkind partition interface. Through the other memkind
> interfaces the user can control and extend memory partition features and
> allocate memory while selecting enabled features.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
