LockSupport源码探索

本文详细介绍了Java并发包中的LockSupport类,该类提供了基本的线程阻塞原语,用于创建锁和其他同步类。通过示例代码展示了如何使用LockSupport.park和LockSupport.unpark方法实现线程间的协调。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

public class LockSupport
extends java.lang.Object
Basic thread blocking primitives for creating locks and other synchronization classes.
This class associates, with each thread that uses it, a permit (in the sense of the Semaphore class). A call to park will return immediately if the permit is available, consuming it in the process; otherwise it may block. A call to unpark makes the permit available, if it was not already available. (Unlike with Semaphores though, permits do not accumulate. There is at most one.)
Methods park and unpark provide efficient means of blocking and unblocking threads that do not encounter the problems that cause the deprecated methods Thread.suspend and Thread.resume to be unusable for such purposes: Races between one thread invoking park and another thread trying to unpark it will preserve liveness, due to the permit. Additionally, park will return if the caller's thread was interrupted, and timeout versions are supported. The park method may also return at any other time, for "no reason", so in general must be invoked within a loop that rechecks conditions upon return. In this sense park serves as an optimization of a "busy wait" that does not waste as much time spinning, but must be paired with an unpark to be effective.
The three forms of park each also support a blocker object parameter. This object is recorded while the thread is blocked to permit monitoring and diagnostic tools to identify the reasons that threads are blocked. (Such tools may access blockers using method getBlocker.) The use of these forms rather than the original forms without this parameter is strongly encouraged. The normal argument to supply as a blocker within a lock implementation is this.
These methods are designed to be used as tools for creating higher-level synchronization utilities, and are not in themselves useful for most concurrency control applications. The park method is designed for use only in constructions of the form:
while (!canProceed()) { ... LockSupport.park(this); }
where neither canProceed nor any other actions prior to the call to park entail locking or blocking. Because only one permit is associated with each thread, any intermediary uses of park could interfere with its intended effects.
Sample Usage. Here is a sketch of a first-in-first-out non-reentrant lock class:

  class FIFOMutex {
    private final AtomicBoolean locked = new AtomicBoolean(false);//锁,true代表已经被某个线程获取了锁
    private final Queue<Thread> waiters
      = new ConcurrentLinkedQueue<Thread>();

    public void lock() {
      boolean wasInterrupted = false;//记录线程是否曾经被中断过
      Thread current = Thread.currentThread();
      waiters.add(current);//把当前线程入队列,入队后当前线程可能在队头也可能不在队头

      // Block while not first in queue or cannot acquire lock//不是在队头或者无法获得锁(用!locked.compareAndSet(false, true)来实现),则block当前线程
      while (waiters.peek() != current ||
             !locked.compareAndSet(false, true)) {
         LockSupport.park(this);//block当前线程
         if (Thread.interrupted()) // ignore interrupts while waiting//因为 LockSupport.park(this);可能会因为线程被中断而马上返回,而线程的中断需要被上层调用代码感知,所以要做这个判断。interrupted()方法判断完是否中断后,会马上重置中断状态,即将中断状态设置为false.
           wasInterrupted = true;//发现线程曾经被中断,则马上标志线程被中断,wasInterrupted后续还有用,用来重新恢复线程中断状态,即是让线程中断状态为true
      }

      waiters.remove();//删除队头元素,即在队列中删除当前线程自己
      if (wasInterrupted)          // reassert interrupt status on exit
         current.interrupt();//恢复中断状态,即让中断状态为true
    }

    public void unlock() {
      locked.set(false);//锁,为false,代表某个线程放弃了锁,当前锁可用
      LockSupport.unpark(waiters.peek());//peek()方法只是查看队头元素,并不删除。 LockSupport.unpark(waiters.peek());意思是将队头的线程解开阻塞状态,让它从lock()方法的LockSupport.park(this);这行继续执行下去
    }
  }
资源下载链接为: https://pan.quark.cn/s/22ca96b7bd39 在当今的软件开发领域,自动化构建与发布是提升开发效率和项目质量的关键环节。Jenkins Pipeline作为一种强大的自动化工具,能够有效助力Java项目的快速构建、测试及部署。本文将详细介绍如何利用Jenkins Pipeline实现Java项目的自动化构建与发布。 Jenkins Pipeline简介 Jenkins Pipeline是运行在Jenkins上的一套工作流框架,它将原本分散在单个或多个节点上独立运行的任务串联起来,实现复杂流程的编排与可视化。它是Jenkins 2.X的核心特性之一,推动了Jenkins从持续集成(CI)向持续交付(CD)及DevOps的转变。 创建Pipeline项目 要使用Jenkins Pipeline自动化构建发布Java项目,首先需要创建Pipeline项目。具体步骤如下: 登录Jenkins,点击“新建项”,选择“Pipeline”。 输入项目名称和描述,点击“确定”。 在Pipeline脚本中定义项目字典、发版脚本和预发布脚本。 编写Pipeline脚本 Pipeline脚本是Jenkins Pipeline的核心,用于定义自动化构建和发布的流程。以下是一个简单的Pipeline脚本示例: 在上述脚本中,定义了四个阶段:Checkout、Build、Push package和Deploy/Rollback。每个阶段都可以根据实际需求进行配置和调整。 通过Jenkins Pipeline自动化构建发布Java项目,可以显著提升开发效率和项目质量。借助Pipeline,我们能够轻松实现自动化构建、测试和部署,从而提高项目的整体质量和可靠性。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值