Bits.reserveMemory

[gustav trede]

Hello,

Is it possible to make the use of Bits.reserveMemory , unreserveMemory
configurable ?.

Usage cases that do not have need for this extra check could benefit from
improved concurrency,
where the gc and allocating threads don't have the risk of fighting around
this static synchronized lock.

A volatile boolean check before entering the lock could do this.

Even low contention usage would benefit from using a cheap read of volatile
boolean compared to a synchronized around multiple memory writes that must
be flushed.


-- 
regards
 gustav trede
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20090822/def23314/attachment.htm>