本文共 13666 字,大约阅读时间需要 45 分钟。
ReentrantReadWriteLock是Lock的另一种实现方式,我们已经知道了ReentrantLock是一个排他锁,同一时间只允许一个线程访问,而ReentrantReadWriteLock允许多个读线程同时访问,但不允许写线程和读线程、写线程和写线程同时访问。相对于排他锁,提高了并发性。在实际应用中,大部分情况下对共享数据(如缓存)的访问都是读操作远多于写操作,这时ReentrantReadWriteLock能够提供比排他锁更好的并发性和吞吐量。
读写锁内部维护了两个锁,一个用于读操作,一个用于写操作。所有 ReadWriteLock实现都必须保证 writeLock操作的内存同步效果也要保持与相关 readLock的联系。也就是说,成功获取读锁的线程会看到写入锁之前版本所做的所有更新。
ReentrantReadWriteLock支持以下功能:
1)支持公平和非公平的获取锁的方式;
2)支持可重入。读线程在获取了读锁后还可以获取读锁;写线程在获取了写锁之后既可以再次获取写锁又可以获取读锁;
3)还允许从写入锁降级为读取锁,其实现方式是:先获取写入锁,然后获取读取锁,最后释放写入锁。但是,从读取锁升级到写入锁是不允许的;
4)读取锁和写入锁都支持锁获取期间的中断;
5)Condition支持。仅写入锁提供了一个 Conditon 实现;读取锁不支持 Conditon ,readLock().newCondition() 会抛出 UnsupportedOperationException。
示例一:利用重入来执行升级缓存后的锁降级
1 class CachedData { 2 Object data; 3 volatile boolean cacheValid; //缓存是否有效 4 ReentrantReadWriteLock rwl = new ReentrantReadWriteLock(); 5 6 void processCachedData() { 7 rwl.readLock().lock(); //获取读锁 8 //如果缓存无效,更新cache;否则直接使用data 9 if (!cacheValid) {10 // Must release read lock before acquiring write lock11 //获取写锁前须释放读锁12 rwl.readLock().unlock();13 rwl.writeLock().lock(); 14 // Recheck state because another thread might have acquired15 // write lock and changed state before we did.16 if (!cacheValid) {17 data = ...18 cacheValid = true;19 }20 // Downgrade by acquiring read lock before releasing write lock21 //锁降级,在释放写锁前获取读锁22 rwl.readLock().lock();23 rwl.writeLock().unlock(); // Unlock write, still hold read24 }25 26 use(data);27 rwl.readLock().unlock(); //释放读锁28 }29 }
示例二:使用 ReentrantReadWriteLock 来提高 Collection 的并发性
通常在 collection 数据很多,读线程访问多于写线程并且 entail 操作的开销高于同步开销时尝试这么做。
1 class RWDictionary { 2 private final Mapm = new TreeMap (); 3 private final ReentrantReadWriteLock rwl = new ReentrantReadWriteLock(); 4 private final Lock r = rwl.readLock(); //读锁 5 private final Lock w = rwl.writeLock(); //写锁 6 7 public Data get(String key) { 8 r.lock(); 9 try { return m.get(key); }10 finally { r.unlock(); }11 }12 public String[] allKeys() {13 r.lock();14 try { return m.keySet().toArray(); }15 finally { r.unlock(); }16 }17 public Data put(String key, Data value) {18 w.lock();19 try { return m.put(key, value); }20 finally { w.unlock(); }21 }22 public void clear() {23 w.lock();24 try { m.clear(); }25 finally { w.unlock(); }26 }27 }
ReentrantReadWriteLock 也是基于AQS实现的,它的自定义同步器(继承AQS)需要在同步状态(一个整型变量state)上维护多个读线程和一个写线程的状态,使得该状态的设计成为读写锁实现的关键。如果在一个整型变量上维护多种状态,就一定需要“按位切割使用”这个变量,读写锁将变量切分成了两个部分,高16位表示读,低16位表示写。
域
ReentrantReadWriteLock含有两把锁readerLock和writerLock,其中ReadLock和WriteLock都是内部类。
1 /** Inner class providing readlock */2 private final ReentrantReadWriteLock.ReadLock readerLock;3 /** Inner class providing writelock */4 private final ReentrantReadWriteLock.WriteLock writerLock;5 /** Performs all synchronization mechanics */6 final Sync sync;
写锁的获取与释放(WriteLock)
写锁是一个可重入的独占锁,使用AQS提供的独占式获取同步状态的策略。
(一)获取写锁
1 //获取写锁 2 public void lock() { 3 sync.acquire(1); 4 } 5 6 //AQS实现的独占式获取同步状态方法 7 public final void acquire(int arg) { 8 if (!tryAcquire(arg) && 9 acquireQueued(addWaiter(Node.EXCLUSIVE), arg))10 selfInterrupt();11 }12 13 //自定义重写的tryAcquire方法14 protected final boolean tryAcquire(int acquires) {15 /*16 * Walkthrough:17 * 1. If read count nonzero or write count nonzero18 * and owner is a different thread, fail.19 * 2. If count would saturate, fail. (This can only20 * happen if count is already nonzero.)21 * 3. Otherwise, this thread is eligible for lock if22 * it is either a reentrant acquire or23 * queue policy allows it. If so, update state24 * and set owner.25 */26 Thread current = Thread.currentThread();27 int c = getState();28 int w = exclusiveCount(c); //取同步状态state的低16位,写同步状态29 if (c != 0) {30 // (Note: if c != 0 and w == 0 then shared count != 0)31 //存在读锁或当前线程不是已获取写锁的线程,返回false32 if (w == 0 || current != getExclusiveOwnerThread())33 return false;34 //判断同一线程获取写锁是否超过最大次数,支持可重入35 if (w + exclusiveCount(acquires) > MAX_COUNT) //36 throw new Error("Maximum lock count exceeded");37 // Reentrant acquire38 setState(c + acquires);39 return true;40 }41 //此时c=0,读锁和写锁都没有被获取42 if (writerShouldBlock() ||43 !compareAndSetState(c, c + acquires))44 return false;45 setExclusiveOwnerThread(current);46 return true;47 }
从源代码可以看出,获取写锁的步骤如下:
1)判断同步状态state是否为0。如果state!=0,说明已经有其他线程获取了读锁或写锁,执行2);否则执行5)。
2)判断同步状态state的低16位(w)是否为0。如果w=0,说明其他线程获取了读锁,返回false;如果w!=0,说明其他线程获取了写锁,执行步骤3)。
3)判断获取了写锁是否是当前线程,若不是返回false,否则执行4);
4)判断当前线程获取写锁是否超过最大次数,若超过,抛异常,反之更新同步状态(此时当前线程以获取写锁,更新是线程安全的),返回true。
5)此时读锁或写锁都没有被获取,判断是否需要阻塞(公平和非公平方式实现不同),如果不需要阻塞,则CAS更新同步状态,若CAS成功则返回true,否则返回false。如果需要阻塞则返回false。
writerShouldBlock() 表示当前线程是否应该被阻塞。NonfairSync和FairSync中有不同是实现。
1 //FairSync中需要判断是否有前驱节点,如果有则返回false,否则返回true。遵循FIFO2 final boolean writerShouldBlock() {3 return hasQueuedPredecessors();4 }5 6 //NonfairSync中直接返回false,可插队。7 final boolean writerShouldBlock() {8 return false; // writers can always barge9 }
(二)释放写锁
1 //写锁释放 2 public void unlock() { 3 sync.release(1); 4 } 5 6 //AQS提供独占式释放同步状态的方法 7 public final boolean release(int arg) { 8 if (tryRelease(arg)) { 9 Node h = head;10 if (h != null && h.waitStatus != 0)11 unparkSuccessor(h);12 return true;13 }14 return false;15 }16 17 //自定义重写的tryRelease方法18 protected final boolean tryRelease(int releases) {19 if (!isHeldExclusively())20 throw new IllegalMonitorStateException();21 int nextc = getState() - releases; //同步状态减去releases22 //判断同步状态的低16位(写同步状态)是否为0,如果为0则返回true,否则返回false.23 //因为支持可重入24 boolean free = exclusiveCount(nextc) == 0; 25 if (free)26 setExclusiveOwnerThread(null);27 setState(nextc); //以获取写锁,不需要其他同步措施,是线程安全的28 return free;29 }
读锁的获取与释放(ReadLock)
读锁是一个可重入的共享锁,采用AQS提供的共享式获取同步状态的策略。
(一)获取读锁
1 public void lock() { 2 sync.acquireShared(1); 3 } 4 5 //使用AQS提供的共享式获取同步状态的方法 6 public final void acquireShared(int arg) { 7 if (tryAcquireShared(arg) < 0) 8 doAcquireShared(arg); 9 }10 11 //自定义重写的tryAcquireShared方法,参数是unused,因为读锁的重入计数是内部维护的12 protected final int tryAcquireShared(int unused) {13 /*14 * Walkthrough:15 * 1. If write lock held by another thread, fail.16 * 2. Otherwise, this thread is eligible for17 * lock wrt state, so ask if it should block18 * because of queue policy. If not, try19 * to grant by CASing state and updating count.20 * Note that step does not check for reentrant21 * acquires, which is postponed to full version22 * to avoid having to check hold count in23 * the more typical non-reentrant case.24 * 3. If step 2 fails either because thread25 * apparently not eligible or CAS fails or count26 * saturated, chain to version with full retry loop.27 */28 Thread current = Thread.currentThread();29 int c = getState();30 //exclusiveCount(c)取低16位写锁。存在写锁且当前线程不是获取写锁的线程,返回-1,获取读锁失败。31 if (exclusiveCount(c) != 0 &&32 getExclusiveOwnerThread() != current)33 return -1;34 int r = sharedCount(c); //取高16位读锁,35 //readerShouldBlock()用来判断当前线程是否应该被阻塞36 if (!readerShouldBlock() &&37 r < MAX_COUNT && //MAX_COUNT为获取读锁的最大数量,为16位的最大值38 compareAndSetState(c, c + SHARED_UNIT)) {39 //firstReader是不会放到readHolds里的, 这样,在读锁只有一个的情况下,就避免了查找readHolds。40 if (r == 0) { // 是 firstReader,计数不会放入 readHolds。41 firstReader = current;42 firstReaderHoldCount = 1;43 } else if (firstReader == current) { //firstReader重入44 firstReaderHoldCount++;45 } else {46 // 非 firstReader 读锁重入计数更新47 HoldCounter rh = cachedHoldCounter; //读锁重入计数缓存,基于ThreadLocal实现48 if (rh == null || rh.tid != current.getId())49 cachedHoldCounter = rh = readHolds.get();50 else if (rh.count == 0)51 readHolds.set(rh);52 rh.count++;53 }54 return 1;55 }56 //第一次获取读锁失败,有两种情况:57 //1)没有写锁被占用时,尝试通过一次CAS去获取锁时,更新失败(说明有其他读锁在申请)58 //2)当前线程占有写锁,并且有其他写锁在当前线程的下一个节点等待获取写锁,除非当前线程的下一个节点被取消,否则fullTryAcquireShared也获取不到读锁59 return fullTryAcquireShared(current);60 }
从源代码可以看出,获取读锁的大致步骤如下:
1)通过同步状态低16位判断,如果存在写锁且当前线程不是获取写锁的线程,返回-1,获取读锁失败;否则执行步骤2)。
2)通过readerShouldBlock判断当前线程是否应该被阻塞,如果不应该阻塞则尝试CAS同步状态;否则执行3)。
3)第一次获取读锁失败,通过fullTryAcquireShared再次尝试获取读锁。
readerShouldBlock方法用来判断当前线程是否应该被阻塞,NonfairSync和FairSync中有不同是实现。
1 //FairSync中需要判断是否有前驱节点,如果有则返回false,否则返回true。遵循FIFO 2 final boolean readerShouldBlock() { 3 return hasQueuedPredecessors(); 4 } 5 final boolean readerShouldBlock() { 6 return apparentlyFirstQueuedIsExclusive(); 7 } 8 //当head节点不为null且head节点的下一个节点s不为null且s是独占模式(写线程)且s的线程不为null时,返回true。 9 //目的是不应该让写锁始终等待。作为一个启发式方法用于避免可能的写线程饥饿,这只是一种概率性的作用,因为如果有一个等待的写线程在其他尚未从队列中出队的读线程后面等待,那么新的读线程将不会被阻塞。10 final boolean apparentlyFirstQueuedIsExclusive() {11 Node h, s;12 return (h = head) != null &&13 (s = h.next) != null &&14 !s.isShared() &&15 s.thread != null;16 }
fullTryAcquireShared方法
1 final int fullTryAcquireShared(Thread current) { 2 /* 3 * This code is in part redundant with that in 4 * tryAcquireShared but is simpler overall by not 5 * complicating tryAcquireShared with interactions between 6 * retries and lazily reading hold counts. 7 */ 8 HoldCounter rh = null; 9 for (;;) {10 int c = getState();11 //如果当前线程不是写锁的持有者,直接返回-1,结束尝试获取读锁,需要排队去申请读锁12 if (exclusiveCount(c) != 0) {13 if (getExclusiveOwnerThread() != current)14 return -1;15 // else we hold the exclusive lock; blocking here16 // would cause deadlock.17 //如果需要阻塞,说明除了当前线程持有写锁外,还有其他线程已经排队在申请写锁,故,即使申请读锁的线程已经持有写锁(写锁内部再次申请读锁,俗称锁降级)还是会失败,因为有其他线程也在申请写锁,此时,只能结束本次申请读锁的请求,转而去排队,否则,将造成死锁。18 } else if (readerShouldBlock()) {19 // Make sure we're not acquiring read lock reentrantly20 if (firstReader == current) {21 //如果当前线程是第一个获取了写锁,那其他线程无法申请写锁22 // assert firstReaderHoldCount > 0;23 } else {24 //从readHolds中移除当前线程的持有数,然后返回-1,然后去排队获取读锁。25 if (rh == null) {26 rh = cachedHoldCounter;27 if (rh == null || rh.tid != current.getId()) {28 rh = readHolds.get();29 if (rh.count == 0)30 readHolds.remove();31 }32 }33 if (rh.count == 0)34 return -1;35 }36 }37 if (sharedCount(c) == MAX_COUNT)38 throw new Error("Maximum lock count exceeded");39 if (compareAndSetState(c, c + SHARED_UNIT)) {40 //示成功获取读锁,后续就是更新readHolds等内部变量,41 if (sharedCount(c) == 0) {42 firstReader = current;43 firstReaderHoldCount = 1;44 } else if (firstReader == current) {45 firstReaderHoldCount++;46 } else {47 if (rh == null)48 rh = cachedHoldCounter;49 if (rh == null || rh.tid != current.getId())50 rh = readHolds.get();51 else if (rh.count == 0)52 readHolds.set(rh);53 rh.count++;54 cachedHoldCounter = rh; // cache for release55 }56 return 1;57 }58 }59 }
(二)释放读锁
1 public void unlock() { 2 sync.releaseShared(1); 3 } 4 5 public final boolean releaseShared(int arg) { 6 if (tryReleaseShared(arg)) { 7 doReleaseShared(); 8 return true; 9 }10 return false;11 }12 13 protected final boolean tryReleaseShared(int unused) {14 Thread current = Thread.currentThread();15 //更新计数16 if (firstReader == current) {17 // assert firstReaderHoldCount > 0;18 if (firstReaderHoldCount == 1)19 firstReader = null;20 else21 firstReaderHoldCount--;22 } else {23 HoldCounter rh = cachedHoldCounter;24 if (rh == null || rh.tid != current.getId())25 rh = readHolds.get();26 int count = rh.count;27 if (count <= 1) {28 readHolds.remove();29 if (count <= 0)30 throw unmatchedUnlockException();31 }32 --rh.count;33 }34 //自旋CAS,减去1<<1635 for (;;) {36 int c = getState();37 int nextc = c - SHARED_UNIT;38 if (compareAndSetState(c, nextc))39 // Releasing the read lock has no effect on readers,40 // but it may allow waiting writers to proceed if41 // both read and write locks are now free.42 return nextc == 0;43 }44 }
(java并发锁ReentrantReadWriteLock读写锁源码分析)http://blog.csdn.net/prestigeding/article/details/53286756
《Java并发编程的艺术》
from: