Commit 6e4f6dfa authored by Guido Trotter's avatar Guido Trotter
Browse files

locking design: explain use of async mode

Before we were discussing this possible future feature, and its
drawbacks, but not its usefulness. This patch corrects this.

Reviewed-by: iustinp
parent 164a5bcb
......@@ -155,10 +155,12 @@ operations such as:
- Try to acquire one of these lock sets and return the first one you were
able to get (or after a timeout) (select/poll like)
Keep in mind, though, that any operation using the first operation, or setting
a timeout for the second one, is susceptible to starvation and thus may never
be able to get the required locks and succeed. Considering this providing/using
these operations should not be among our first priorities
These operations can be used to prioritize operations based on available locks,
rather than making them just blindly queue for acquiring them. The inherent
risk, though, is that any code using the first operation, or setting a timeout
for the second one, is susceptible to starvation and thus may never be able to
get the required locks and complete certain tasks. Considering this
providing/using these operations should not be among our first priorities.
Locking granularity
~~~~~~~~~~~~~~~~~~~
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment