GAgavinray·Sep 23, 2022
At least the PMDK (Persistent Memory Development Kit) code works interoperably with both Optane and CXL:
https://github.com/pmem/pmdk
In Understanding the Intel Optane Shutdownpmem
pmdk
C2018–2022
pmem / pmdk · Archived
pmdk
Persistent Memory Development Kit
2Distinct people
2Mentions
0Explicit recommenders
1.4KGitHub stars
What to know before exploring
What it is
Persistent Memory Development Kit
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year2 dated mentions
Observed mentions: 2018-05-31 08:41:33 UTC to 2022-09-23 19:29:56 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sourcesDisclaimer: I work at Intel on PMDK (pmem.io)
It is the game changer that you wish for, since the marshaling logic that you mention is gone. Persistent Memory can be accessed directly through memory mapped file, bypassing the traditional read()/write() I/O paths. Recent file systems have also been modified to a) skip the page cache layer and b) forgo the msync() call that would be otherwise required to synchronize the modified pages. This is what's called DAX (Direct Access [0]). In the place of msync() you can now just use CPU cache flush instructions. These two file system changes entirely eliminate kernel code from the I/O path (apart from the initial page faults).
Persistent Memory Development Kit contains libpmemobj [1], which is almost exactly what you are imagining ;) It's a persistent heap, with transactions for durability. It's n
Read the rest
ot as nice (yet) as your code snippet, but here's C++ example [2] of a persistent queue push:
obj::transaction::exec_tx(pool, [this, &value] {
auto n = obj::make_persistent<Node>(value, nullptr);
if (head == nullptr) {
head = tail = n;
} else {
tail->next = n;
tail = n;
}
});
`make_persistent` is, akin to `make_unique`, a memory allocation of a "Node" class. Once allocated, we can just assign the newly allocated object to a different persistent variable. No kernel code executing, no serialization ;)
[0]- https://www.kernel.org/doc/Documentation/filesystems/dax.txt
[1] - https://github.com/pmem/pmdk
[2] - https://github.com/pmem/pmdk/blob/master/src/examples/libpme...