走进 AQS 瞧一瞧看一看

并发中有一块很重要的东西就是AQS。接下来一周的目标就是它。

看复杂源码时，一眼望过去，这是什么？不要慌，像剥洋葱一样，一层层剥开（哥，喜欢"扒开"这个词）。

参考资源：

https://www.cnblogs.com/waterystone/p/4920797.html

https://javadoop.com/post/AbstractQueuedSynchronizer#toc4

一概述

大师Doug Lea依赖FIFO（First-in-first-out）等待队列，创建了AQS框架来实现锁和同步器的操作。AQS是LimitLatch，countDownLacth，ReentrantLock，etc 这些类的基础。它们都是继承了AQS类，继承的时候，protected的方法根据业务需要必须重写，也就是tryAcquire，tryRelease，tryAcquireShared，tryReleaseShared，isHeldExclusively中的一部分或是全部。

二AQS结构

1.我们看看AQS的属性：

静态内部类 Node （为什么要写静态内部类，个人觉得，Node是链表结构，在这里作为阻塞队列来使用，只有单独一个地方（AQS中）使用，所以写成静态内部类，也提高了封装性）

// 头结点

private transient volatile Node head;

// 尾结点

private transient volatile Node tail;

// 资源状态，等于0：没有被任何thread占有；大于0：资源已经被其他线程占有

 private volatile int state;

2.Node的内部构造

Node类至关重要，我懒了，贴一下代码，发现里面的注释真的很详细，就不再翻译一遍了。

        /** Marker to indicate a node is waiting in shared mode */
           // 共享模式
        static final Node SHARED = new Node();
        /** Marker to indicate a node is waiting in exclusive mode */
           // 独占模式
        static final Node EXCLUSIVE = null;

        /** waitStatus value to indicate thread has cancelled */
        static final int CANCELLED =  1;
           // 在这里，大家注意一下。waitStatus 值有1，-1，-2，中间越过了0.  
           // 其实，waitStatus 的值，有0 这种情况，初始值为0
        /** waitStatus value to indicate successor's thread needs unparking */
        static final int SIGNAL    = -1;
        /** waitStatus value to indicate thread is waiting on condition */
        static final int CONDITION = -2;
        /**
         * waitStatus value to indicate the next acquireShared should
         * unconditionally propagate
         */
        static final int PROPAGATE = -3;

        /**
         * Status field, taking on only the values:
         *   SIGNAL:     The successor of this node is (or will soon be)
         *               blocked (via park), so the current node must
         *               unpark its successor when it releases or
         *               cancels. To avoid races, acquire methods must
         *               first indicate they need a signal,
         *               then retry the atomic acquire, and then,
         *               on failure, block.
         *   CANCELLED:  This node is cancelled due to timeout or interrupt.
         *               Nodes never leave this state. In particular,
         *               a thread with cancelled node never again blocks.
         *   CONDITION:  This node is currently on a condition queue.
         *               It will not be used as a sync queue node
         *               until transferred, at which time the status
         *               will be set to 0. (Use of this value here has
         *               nothing to do with the other uses of the
         *               field, but simplifies mechanics.)
         *   PROPAGATE:  A releaseShared should be propagated to other
         *               nodes. This is set (for head node only) in
         *               doReleaseShared to ensure propagation
         *               continues, even if other operations have
         *               since intervened.
         *   0:          None of the above
         *
         * The values are arranged numerically to simplify use.
         * Non-negative values mean that a node doesn't need to
         * signal. So, most code doesn't need to check for particular
         * values, just for sign.
         *
         * The field is initialized to 0 for normal sync nodes, and
         * CONDITION for condition nodes.  It is modified using CAS
         * (or when possible, unconditional volatile writes).
         */
        volatile int waitStatus;

        volatile Node prev;
         */
        volatile Node next;

        /**
         * The thread that enqueued this node.  Initialized on
         * construction and nulled out after use.
         */
        volatile Thread thread;

        Node nextWaiter;

接下来，进入到AQS源码分析环节。

概述中提到过下面这几个方法tryAcquire，tryRelease，tryAcquireShared，tryReleaseShared

它们分别是独占锁的获取和释放，共享锁的获取和释放。

这里，我们从独占锁的获取开始讲起。

3.独占锁方法解析

3.1 acquire 方法

    /**
     * Acquires in exclusive mode, ignoring interrupts.  Implemented
     * by invoking at least once {@link #tryAcquire},
     * returning on success.  Otherwise the thread is queued, possibly
     * repeatedly blocking and unblocking, invoking {@link
     * #tryAcquire} until success.  This method can be used
     * to implement method {@link Lock#lock}.
     *
     * @param arg the acquire argument.  This value is conveyed to
     *        {@link #tryAcquire} but is otherwise uninterpreted and
     *        can represent anything you like.
     */
       // 尝试获取锁，tryAcquire放回true，表示成功获取锁，就不会再往下走了。
    public final void acquire(int arg) {
           // 尝试获取锁失败，并且，acquireQueued成功，那么就会进入方法中，执行自我中断
           // 接下来，开始剥洋葱，方法逐个分析解惑
        if (!tryAcquire(arg) &&
            acquireQueued(addWaiter(Node.EXCLUSIVE), arg))
            selfInterrupt();
    }

3.2 tryAcquire 方法

    /**
     * Attempts to acquire in exclusive mode. This method should query
     * if the state of the object permits it to be acquired in the
     * exclusive mode, and if so to acquire it.
     *
     * <p>This method is always invoked by the thread performing
     * acquire.  If this method reports failure, the acquire method
     * may queue the thread, if it is not already queued, until it is
     * signalled by a release from some other thread. This can be used
     * to implement method {@link Lock#tryLock()}.
     *
     * <p>The default
     * implementation throws {@link UnsupportedOperationException}.
     *
     * @param arg the acquire argument. This value is always the one
     *        passed to an acquire method, or is the value saved on entry
     *        to a condition wait.  The value is otherwise uninterpreted
     *        and can represent anything you like.
     * @return {@code true} if successful. Upon success, this object has
     *         been acquired.
     * @throws IllegalMonitorStateException if acquiring would place this
     *         synchronizer in an illegal state. This exception must be
     *         thrown in a consistent fashion for synchronization to work
     *         correctly.
     * @throws UnsupportedOperationException if exclusive mode is not supported
     */
       // 哇咔咔，这么长注释，不过别着急。慢慢看。
       // 这个方法用来查询对象的state是否允许以独占方式来获取锁，如果可以，尝试获取。
       // 接下里大家会疑问，为什么这个方法里面只有throw这一行代码。因为，这个方法需要在子类继承的时候需要被重写，这个就是设计模式中的模板方法。
       // 同时，这个方法没有被做成abstract方法，因为，子类继承的时候为了自己的需求，只需要实现独占模式的方法或是共享模式的方法即可，不用都去实现。
    protected boolean tryAcquire(int arg) {
        throw new UnsupportedOperationException();
    }

3.3 acquireQueued方法

/**
     * Acquires in exclusive uninterruptible mode for thread already in
     * queue. Used by condition wait methods as well as acquire.
     *
     * @param node the node
     * @param arg the acquire argument
     * @return {@code true} if interrupted while waiting
     */
       // 线程挂起后，被解锁，就是在这个方法里实现的
       // 方法返回结果：等待时，是否被中断
    final boolean acquireQueued(final Node node, int arg) {
           // failed  true：表示没有拿到资源  false：表示成功拿到资源
        boolean failed = true;
        try {
               // interrupted 是否被中断
            boolean interrupted = false;
               // 又一个自旋的使用哦
            for (;;) {
                   // 获取前一个节点Node
                final Node p = node.predecessor();
                if (p == head && tryAcquire(arg)) {
                       // 设置头结点，将原先的头结点与node节点的连接，断开
                    setHead(node);
                    p.next = null; // help GC
                    failed = false;
                    return interrupted;
                }
                   // 获取锁失败，是否应该挂起当前线程
                   // p 是前驱节点，node是当前线程节点
                if (shouldParkAfterFailedAcquire(p, node) &&
                       // 获取锁失败，挂起线程的操作在下面方法里实施
                    parkAndCheckInterrupt())
                    interrupted = true;
            }
        } finally {
            if (failed)
                cancelAcquire(node);
        }
    }

3.3.1 shouldParkAfterFailedAcquire方法

/**
     * Checks and updates status for a node that failed to acquire.
     * Returns true if thread should block. This is the main signal
     * control in all acquire loops.  Requires that pred == node.prev.
     *
     * @param pred node's predecessor holding status
     * @param node the node
     * @return {@code true} if thread should block
     */
       // 这个方法用途：获取锁失败，判断是否需要挂起线程
    private static boolean shouldParkAfterFailedAcquire(Node pred, Node node) {
        int ws = pred.waitStatus;
           // 等待状态 SIGNAL表示前驱节点状态正常，当前线程需要挂起，直接返回true
        if (ws == Node.SIGNAL)
            /*
             * This node has already set status asking a release
             * to signal it, so it can safely park.
             */
               // 这个节点已经让请求release的状态来标识，所以它可以安全的park了
            return true;
        if (ws > 0) {
            /*
             * Predecessor was cancelled. Skip over predecessors and
             * indicate retry.
             */
               // ws大于0的状态1，表示取消了排队。
               // 如果取消了排队，接着再去找前一个，前一个也被取消了，就找前一个的前一个，总会有一个没被取消的。
            do {
                node.prev = pred = pred.prev;
            } while (pred.waitStatus > 0);
            pred.next = node;
        } else {
            /*
             * waitStatus must be 0 or PROPAGATE.  Indicate that we
             * need a signal, but don't park yet.  Caller will need to
             * retry to make sure it cannot acquire before parking.
             */
               // else的情况，就是waitStatus 为0，-2，-3
               // 用CAS将前驱节点状态设为-1（Node.SIGNAL）
            compareAndSetWaitStatus(pred, ws, Node.SIGNAL);
        }
        return false;
    }

3.3.2 parkAndCheckInterrupt方法

/**
     * Convenience method to park and then check if interrupted
     *
     * @return {@code true} if interrupted
     */
      // 在shouldParkAfterFailedAcquire返回true的时候，才会执行这个方法，这个方法的作用就是挂起线程
    private final boolean parkAndCheckInterrupt() {
          // 调用park方法，使线程挂起 （使用unpark方法来唤醒线程）
        LockSupport.park(this);
          // 查看线程是否被中断
        return Thread.interrupted();
    }

3.4 addWaiter 方法

    /**
     * Creates and enqueues node for current thread and given mode.
     *
     * @param mode Node.EXCLUSIVE for exclusive, Node.SHARED for shared
     * @return the new node
     */
       // 将Node放进阻塞队列的末尾
    private Node addWaiter(Node mode) {
           // 生成一个node节点，保存当前的线程和占用模式（独占模式或是共享模式）
        Node node = new Node(Thread.currentThread(), mode);
        // Try the fast path of enq; backup to full enq on failure
        Node pred = tail;
           // 查询tail节点是否有值，有值代表的是此链表不为空
        if (pred != null) {
               // node相连接，很简单，就是改变指针指向，可以参考数据结构 链表
            node.prev = pred;
               // compareAndSetTail这个方法的操作就是比较赋值，经典的CAS方法，不明白的可以参照下面资源
               // http://www.cnblogs.com/lihao007/p/8654787.html 
            if (compareAndSetTail(pred, node)) {
                pred.next = node;
                return node;
            }
        }
        enq(node);
        return node;
    }

3.4.1 eng（）方法

/**
     * Inserts node into queue, initializing if necessary. See picture above.
     * @param node the node to insert
     * @return node's predecessor
     */
       // 来到这个方法有两种可能。一是等待线程队列为空，二是其他线程更新了队列
    private Node enq(final Node node) {
           // 又是自旋方法（乐观锁），AQS源码中出现多次，因为需要线程的不安全
        for (;;) {
            Node t = tail;
            if (t == null) { // Must initialize
                if (compareAndSetHead(new Node()))
                    tail = head;
            } else {
                   // 将node放在队列最后，有线程竞争的话，排不上重排
                node.prev = t;
                if (compareAndSetTail(t, node)) {
                    t.next = node;
                    return t;
                }
            }
        }
    }

 独占模式获取锁，就分析到这里了。

4.release独占模式 释放锁

/**
     * Releases in exclusive mode.  Implemented by unblocking one or
     * more threads if {@link #tryRelease} returns true.
     * This method can be used to implement method {@link Lock#unlock}.
     *
     * @param arg the release argument.  This value is conveyed to
     *        {@link #tryRelease} but is otherwise uninterpreted and
     *        can represent anything you like.
     * @return the value returned from {@link #tryRelease}
     */
       // 独占模式下，释放锁 
    public final boolean release(int arg) {
           // tryRelease方法是模板方法，留给子类定义。
        if (tryRelease(arg)) {
            Node h = head;
               // 首先判断阻塞队列是否为空。接下来，判断waitStatus的状态，0的状态是初始化是被赋予的值。只有是非0的状态，才说明head节点后面是有其它节点的。
            if (h != null && h.waitStatus != 0)
                unparkSuccessor(h);
            return true;
        }
        return false;
    }

4.1 unparkSuccessor

/**
     * Wakes up node's successor, if one exists.
     *
     * @param node the node
     */
    private void unparkSuccessor(Node node) {
        /*
         * If status is negative (i.e., possibly needing signal) try
         * to clear in anticipation of signalling.  It is OK if this
         * fails or if status is changed by waiting thread.
         */
        int ws = node.waitStatus;
        if (ws < 0)
            compareAndSetWaitStatus(node, ws, 0);

        /*
         * Thread to unpark is held in successor, which is normally
         * just the next node.  But if cancelled or apparently null,
         * traverse backwards from tail to find the actual
         * non-cancelled successor.
         */
        Node s = node.next;
        if (s == null || s.waitStatus > 0) {
            s = null;
               // 这里，是从队列末尾向前查找没有被取消的节点
               // 这里，我当时对为什么从后向前查找有疑问，后来看了文章明白了。地址：https://javadoop.com/post/AbstractQueuedSynchronizer#toc4
            for (Node t = tail; t != null && t != node; t = t.prev)
                if (t.waitStatus <= 0)
                    s = t;
        }
        if (s != null)
            LockSupport.unpark(s.thread);
    }

 就写到这里了，仍需努力，以后有想法了，慢慢补充，写的不对的地方，欢迎指正，共同探讨。