I'm getting filtered when I try to respond to the original thread. This is an important issue: If a writer holds the lock for a significant time (e.g., refreshing a table from a database), do all would-be readers spin-loop, or is it a hybrid spin-then-sleep solution? We should know this for certain.
Busy-loop is a no-go, at least without some non-default build-time option (or in later releases, a _ex() form of the create API which allows the flavor to be selected).
