https://jseigh.wordpress.com/2026/09/07/consequential-concurrent-sequential-rcu/
The name doesn't really mean anything. I was just generalizing something
that's been around forever.* It's simple enough that it must be in use somewhere. I just haven't noticed it. I looked up the linux kernal
seqlock documentation and it specifically says not to use pointers in
seqlock protected data and no idea why that is unless the linux kernel
is doing something weird with memory mapping.
Like seqlock, it is obstruction-free. If you have qsbr (RCU) or ebr,
that would be a better choice. It might be good for libraries where
the memory reclamation is hidden from the application.
* tangentially related to something that I was working on which if far
more perverse but mostly in a solution that is looking for a problem
phase so it probably won't go anywhere.
--- PyGate Linux v1.5.19
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)