关于ReaderWriterLockSlim
:
随后在 中获取两个锁同 线程实际上应该抛出 LockRecursionException
(递归策略设置为 NoRecursion
)。
我的观察结果:
LockRecursionException
LockRecursionException
LockRecursionException
LockRecursionException
LockRecursionException
LockRecursionException
LockRecursionException
这种行为是否正确?
最佳答案
A thread in upgradeable mode can downgrade to read mode by first calling the
EnterReadLock
method and then calling theExitUpgradeableReadLock
method. This downgrade pattern is allowed for all lock recursion policies, evenNoRecursion
.
我的理解是,对于写的情况,无论如何进入写锁是从可升级到写模式的正常方式,所以即使在
NoRecursion
的策略下也必须支持。 (对于不可升级的可升级锁似乎没有什么意义:)
关于.net - ReaderWriterLockSlim : acquiring a read lock after an upgradeable lock doesn't throw LockRecursionException,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/14811313/