聊聊高并发(十七)解析java.util.concurrent各个组件(一) 了解sun.misc.Unsafe类
了解了并發(fā)編程中鎖的基本原理之后,接下來看看Java是如何利用這些原理來實(shí)現(xiàn)各種鎖,原子變量,同步組件的。在開始分析java.util.concurrent的源代碼直接,首先要了解的就是sun.misc.Unsafe類,這個(gè)類可以說的java并發(fā)包的基礎(chǔ),基本上所有的組件都是依賴Unsafe來做底層的同步操作。
?
Unsafe類有100+個(gè)方法,大部分是native方法,可以理解為Java平臺(tái)和底層操作系統(tǒng)直接的橋梁。它封裝了大量的底層操作,比如直接操作內(nèi)存的方法,低級(jí)同步的方法,CAS方法,直接操作Class的方法,直接操作Object的方法等等。有了Unsafe類,就可以像C, C++一樣精確地操作內(nèi)存。當(dāng)然Java的一大優(yōu)點(diǎn)就是可以安全的操作內(nèi)存,所以不提倡開發(fā)者直接使用Unsafe類。JDK本身的類很多都利用了Unsafe來進(jìn)行底層操作。
?
Unsafe和并發(fā)編程相關(guān)的有幾類方法:
1. CAS方法
2. 操作條件隊(duì)列的方法,比如park()讓線程進(jìn)入等待,unpark()喚醒線程
3. 存取volatile變量的方法,比如getBooleanVolatile, putBooleanVolatile
?
首先看看CAS方法,主要是3個(gè)comAndSwapXXX方法
1. compareAndSwapObject提供了對(duì)一個(gè)對(duì)象引用進(jìn)行CAS的能力
2. compareAndSwapInt提供了對(duì)一個(gè)32位整數(shù)進(jìn)行CAS操作的能力
3. compareAndSwapLong提供了對(duì)64位整數(shù)進(jìn)行CAS操作的能力
關(guān)于CAS的概念請(qǐng)看這篇?聊聊高并發(fā)(十二)分析java.util.concurrent.atomic.AtomicStampedReference源碼來看如何解決CAS的ABA問題
?
?public final class Unsafe{
public final native boolean compareAndSwapObject(Object o, long offset,
Object expected,
Object x);
/**
* Atomically update Java variable to <tt>x</tt> if it is currently
* holding <tt>expected</tt>.
* @return <tt>true</tt> if successful
*/
public final native boolean compareAndSwapInt(Object o, long offset,
int expected,
int x);
/**
* Atomically update Java variable to <tt>x</tt> if it is currently
* holding <tt>expected</tt>.
* @return <tt>true</tt> if successful
*/
public final native boolean compareAndSwapLong(Object o, long offset,
long expected,
long x);
..............
}
操作條件隊(duì)列的方法有兩個(gè):
?
1. park(boolean isAbsolute, long time), 這個(gè)方法會(huì)讓當(dāng)前線程進(jìn)入等待,并釋放鎖。Java并發(fā)包里的Condition接口的底層實(shí)現(xiàn)就是利用了Unsafe的park方法來實(shí)現(xiàn)的。第一個(gè)參數(shù)isAbsolute是表示用絕對(duì)時(shí)間還是相對(duì)事件,如果是絕對(duì)時(shí)間,就等待直到time,比如Condition接口的awaitUntil(Date deadline)。isAbsolute為false時(shí),等待一個(gè)時(shí)間間隔
2. unpark(Object thread)喚醒等待的線程,Condition的signal方法就是基于unpark實(shí)現(xiàn)的
?
?/**
* Unblock the given thread blocked on <tt>park</tt>, or, if it is
* not blocked, cause the subsequent call to <tt>park</tt> not to
* block. Note: this operation is "unsafe" solely because the
* caller must somehow ensure that the thread has not been
* destroyed. Nothing special is usually required to ensure this
* when called from Java (in which there will ordinarily be a live
* reference to the thread) but this is not nearly-automatically
* so when calling from native code.
* @param thread the thread to unpark.
*
*/
public native void unpark(Object thread);
/**
* Block current thread, returning when a balancing
* <tt>unpark</tt> occurs, or a balancing <tt>unpark</tt> has
* already occurred, or the thread is interrupted, or, if not
* absolute and time is not zero, the given time nanoseconds have
* elapsed, or if absolute, the given deadline in milliseconds
* since Epoch has passed, or spuriously (i.e., returning for no
* "reason"). Note: This operation is in the Unsafe class only
* because <tt>unpark</tt> is, so it would be strange to place it
* elsewhere.
*/
public native void park(boolean isAbsolute, long time);
存取volatile變量的方法,這些方法讓Unsafe對(duì)象有了直接存取volatile變量的能力。
?
?
?public native Object getObjectVolatile(Object obj, long l);
public native void putObjectVolatile(Object obj, long l, Object obj1);
public native int getIntVolatile(Object obj, long l);
public native void putIntVolatile(Object obj, long l, int i);
public native boolean getBooleanVolatile(Object obj, long l);
public native void putBooleanVolatile(Object obj, long l, boolean flag);
public native byte getByteVolatile(Object obj, long l);
public native void putByteVolatile(Object obj, long l, byte byte0);
public native short getShortVolatile(Object obj, long l);
public native void putShortVolatile(Object obj, long l, short word0);
public native char getCharVolatile(Object obj, long l);
public native void putCharVolatile(Object obj, long l, char c);
public native long getLongVolatile(Object obj, long l);
public native void putLongVolatile(Object obj, long l, long l1);
? public native float getFloatVolatile(Object obj, long l);
??? public native void putFloatVolatile(Object obj, long l, float f);
??? public native double getDoubleVolatile(Object obj, long l);
??? public native void putDoubleVolatile(Object obj, long l, double d);
關(guān)于Unsafe對(duì)象的其他信息,比如如何得到Unsafe對(duì)象,比如如何直接操作內(nèi)存,類似反射機(jī)制存取對(duì)象屬性,請(qǐng)查看這篇Java Magic 4. Part 4: sun.misc,Unsafe
?
?
java.util.concurrent包提供了一個(gè)LockSupport類來封裝了Unsafe對(duì)象,來提供操作條件隊(duì)列的方法。
?
來看一下LockSupport的實(shí)現(xiàn),有幾點(diǎn)比較有意思
1. 利用Unsafe直接操作內(nèi)存來存取對(duì)象的能力來設(shè)置blocker
Unsafe.objectFieldOffset可以獲得某個(gè)字段在對(duì)象所在內(nèi)存的offset,有了這個(gè)offset,就可以通過對(duì)象的引用來找到字段所在的實(shí)際內(nèi)存地址。這種做法在C++中常見,但是在Java中不推薦上層程序使用。
這段代碼的意思是把a(bǔ)rg對(duì)象設(shè)置到Thread的parkBlocker屬性上。
Thread的parkBlocker屬性用來指出當(dāng)前線程是在哪個(gè)對(duì)象上阻塞
?
?public class LockSupport {
private LockSupport() {} // Cannot be instantiated.
// Hotspot implementation via intrinsics API
private static final Unsafe unsafe = Unsafe.getUnsafe();
private static final long parkBlockerOffset;
static {
try {
parkBlockerOffset = unsafe.objectFieldOffset
(java.lang.Thread.class.getDeclaredField("parkBlocker"));
} catch (Exception ex) { throw new Error(ex); }
}
private static void setBlocker(Thread t, Object arg) {
// Even though volatile, hotspot doesn't need a write barrier here.
unsafe.putObject(t, parkBlockerOffset, arg);
}
public class Thread{
?/**
???? * The argument supplied to the current call to
???? * java.util.concurrent.locks.LockSupport.park.
???? * Set by (private) java.util.concurrent.locks.LockSupport.setBlocker
???? * Accessed using java.util.concurrent.locks.LockSupport.getBlocker
???? */
??? volatile Object parkBlocker;
}
2. park方法需要指明鎖對(duì)象,可以看到,park方法先setBlocker標(biāo)記當(dāng)前線程是在哪個(gè)鎖對(duì)象上等待,然后調(diào)用Unsafe的park方法,當(dāng)Unsafe的park方法返回時(shí)表示已經(jīng)退出等待,就把blocker設(shè)置為null.
?
用jstack命令查看過線程狀態(tài)的同學(xué)肯定知道jstack能打印出線程是在哪個(gè)對(duì)象上block,這個(gè)對(duì)象就是這里的blocker
?
?public static void park(Object blocker) {
Thread t = Thread.currentThread();
setBlocker(t, blocker);
unsafe.park(false, 0L);
setBlocker(t, null);
}
?
?
LockSupport的park()和unpark()方法和Object.wait(), notify方法都可以操作線程的等待和喚醒,但是兩者主要有兩個(gè)區(qū)別
1. 面向的主體不同,LockSupport的park, unpark面向的是線程,而Object.wait, nofify面向的是對(duì)象
2. 底層實(shí)現(xiàn)機(jī)制不同,可以看到Object的wait, notify方法也是native方法,Unsafe的park和unpark方法也是native方法,底層實(shí)現(xiàn)不同,Object.notify不能喚醒Unsafe park的線程。
?
?
?public class Object{
public final native void wait(long timeout) throws InterruptedException;
public final native void notify();
public final native void notifyAll();
}
?
總結(jié)
以上是生活随笔為你收集整理的聊聊高并发(十七)解析java.util.concurrent各个组件(一) 了解sun.misc.Unsafe类的全部內(nèi)容,希望文章能夠幫你解決所遇到的問題。
- 上一篇: 聊聊高并发(六)实现几种自旋锁
- 下一篇: 聊聊高并发(二十)解析java.util