non-fair ReentrantReadWriteLock write and read lock priorities

Asked Mar 10 '17 at 15:36

Active Mar 13 '17 at 13:02

Viewed 36 times

If I understand correct if I use fair mode

read and write locks doesn't have priorities and all locks will be acquired on order of the requesting by other threads. After write request receiving - if

But I am not sure about non-fair mode. As written in concurrency in practice it is some sort of random.

But I am not fully inderstand this.

If I understand correct most profit of usage RWL that readers can read in parallel.

But Lets imagine that we have a lot of read operations. Lets say several threads constantly hold read lock(single read is not long but two neighbours read always overlaps). And sometimes write operation occures.

Does write operations will be executed eventually?

edited Mar 13 '17 at 13:02

asked Mar 10 '17 at 15:36

gstackoverflow

36,709
117
359
710

1

This says it best: _In other words, it is conceivable that one thread might be continuously starved because other threads always manage to arbitrarily get the lock instead of it._ – Sotirios Delimanolis Mar 10 '17 at 16:45
@Sotirios is it might be or it isguaranteed? – gstackoverflow Mar 13 '17 at 07:59
@Sotirios, marked topic is not duplicate. – gstackoverflow Mar 13 '17 at 08:20
_might be_ means _might be_. – Sotirios Delimanolis Mar 13 '17 at 14:36

non-fair ReentrantReadWriteLock write and read lock priorities

0 Answers0