harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "史成荣" <icyr...@gmail.com>
Subject Re: [harmony][Thread]
Date Wed, 19 Dec 2007 01:24:39 GMT
在07-12-18,Xiao-Feng Li <xiaofeng.li@gmail.com> 写道:
> Chengrong, locking is expensive, which should be optimized or avoided.
> The fast path acquiring the lock without Java-native border crossing
> can be much fast. It's expected the fast path be executed in most
> cases. This is possible if the code sequence doesn't trigger garbage
> collection or exception, hence no need to bookkeeping the frames.

Does that mean if the code sequence  triggers garbage
collection or exception, the thread requiring or releasing the lock will
first take the fast path, and it must return lock-busy, then it goes to the
slow path and eventually finish the lock operation?

> Thanks,
> xiaofeng
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message