[master] Withdrawn: 8304341: [Lilliput] Use fixed-size lock-stack

Roman Kennke rkennke at openjdk.org
Mon Jul 17 10:51:28 UTC 2023


On Thu, 16 Mar 2023 12:12:30 GMT, Roman Kennke <rkennke at openjdk.org> wrote:

> Until now, we used to have a variable-sized lock-stack: when pushing an object to it and capacity is exceeded, it would re-allocate a new stack and use that. However, experiments show that the lock-stack very rarely exceeds 5 slots (I have not yet found a workload that does actually exceed it). It makes sense to make the lock-stack a fixed-size array: it makes addressing the lock-stack simpler and more efficient and it increases the likelyhood of the lock-stack being in CPU cache. If the lock-stack is ever exceeded, we would not do stack-locking at all, but instead inflate the monitor and use that.
> 
> This is already integrated in the related upstream PR: https://github.com/openjdk/jdk/pull/10907
> 
> Testing:
>  - [x] tier1
>  - [ ] tier2

This pull request has been closed without being integrated.

-------------

PR: https://git.openjdk.org/lilliput/pull/81


More information about the lilliput-dev mailing list