Re: [PATCH 1/5] locking: Introduce range reader/writer lock

[Davidlohr Bueso]

On Mon, 03 Apr 2017, Jan Kara wrote:

> Or just a plain sequence counter of the lock operations?

So what I dislike about this is that we'd also have to enlarge
the struct range_rwlock_tree. otoh, I'm hesitant to depend on
the tick rate for lock correctness, so perhaps your suggestion
is best.

Thanks,
Davidlohr