You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deferred memory reclamation uses a kind of amortized proxy-collector technique,
and together with timestamp based validation provides pure read-only
read transactions
But the version here seems to accept arbitrary reclaimers. Was the proxy-collector not implemented?
The text was updated successfully, but these errors were encountered:
I has been many years since I worked with the original implementation (the implementation in this library is based on one that I created back then). The original implementation by did implement a proxy-collector, but AFAIR it only worked for 32-bit and crashed on 64-bit. The proxy-collector was only used for the table's memory block. because the original implementation was very limited in the supported key/value types (it only supported trivially copyable types of size <= sizeof(void*)).
In my implementation the selected reclamation scheme is used for the table's memory block, as well as for any additional nodes that have to be allocated for non-trivial keys/values. I have considered to allow specification of separate reclaimers for the two cases, but that is not implemented yet.
The original post for the vyukov hashmap mentions a "proxy-collector" used for memory reclamation:
But the version here seems to accept arbitrary reclaimers. Was the proxy-collector not implemented?
The text was updated successfully, but these errors were encountered: