Paul Khuong: some Lisp🔒 SSL Verified

Table of Contents

• ↓ The basic setup
• ↓ Parameters
• ↓ Invariants
• ↓ Protected versions
• ↓ Reader logic
• ↓ Writer logic
• ↓ Top Alternatives to pvk.ca

6-Month Traffic Trend Estimate

Official Contact & Profiles

Visual representation extracted from pvk.ca

Content Snippets from pvk.ca

"This post describes a reader/writer version management scheme I recently came up with. I find it interesting because it"

"The last point is interesting for the higher level system, since it’s now practical to allocate storage for all protected versions statically… safe memory reclamation (SMR) makes sense even without dynamic storage management!"

"We can always build regular memory reclamation on top of the version tracking, but we can also directly use the bounded set of protected versions to, e.g., implement multi-version read transactions in constant space."

"Even when embedded in vanilla epoch-based memory reclamation, the scheme brings something interesting to the table, since it combines a QSBR fast path with support for sleeping (disabled) readers, thanks to the hazard pointer slow path. The QSBR fast path and its fence-freedom on TSO can be useful even now that we have membarrier(2), e.g., when we want to support short epoch update periods (shorter than every few hundred nanoseconds), or when running on isolated cores."

Key Topics & Focus Areas for pvk.ca:

The basic setup

Parameters

Invariants

Protected versions

Reader logic

Writer logic