Re: RFR: 8352971: Increase maximum number of hold counts for ReentrantReadWriteLock [v2]

2025-04-08 Thread Jean-Noël Rouvignac
On Mon, 7 Apr 2025 13:55:27 GMT, Viktor Klang wrote: >> I'm breaking this change out as a separate improvement, since it will not be >> generally possible to adjust these limits on the j.u.c primitives since they >> might already use a backing `long` to pack in information which needs to be >>

Re: RFR: 8352971: Increase maximum number of hold counts for ReentrantReadWriteLock [v2]

2025-04-08 Thread Viktor Klang
On Tue, 8 Apr 2025 05:12:00 GMT, Jean-Noël Rouvignac wrote: >> Viktor Klang has updated the pull request with a new target base due to a >> merge or a rebase. The incremental webrev excludes the unrelated changes >> brought in by the merge/rebase. The pull request contains two additional >> co

Re: RFR: 8352971: Increase maximum number of hold counts for ReentrantReadWriteLock [v2]

2025-04-07 Thread Viktor Klang
> I'm breaking this change out as a separate improvement, since it will not be > generally possible to adjust these limits on the j.u.c primitives since they > might already use a backing `long` to pack in information which needs to be > updated atomically (would require 128-bit atomics to widen

Re: RFR: 8352971: Increase maximum number of hold counts for ReentrantReadWriteLock [v2]

2025-04-07 Thread Viktor Klang
On Mon, 7 Apr 2025 14:03:13 GMT, Alan Bateman wrote: >> Viktor Klang has updated the pull request with a new target base due to a >> merge or a rebase. The incremental webrev excludes the unrelated changes >> brought in by the merge/rebase. The pull request contains two additional >> commits s

Re: RFR: 8352971: Increase maximum number of hold counts for ReentrantReadWriteLock [v2]

2025-04-07 Thread Alan Bateman
On Mon, 7 Apr 2025 13:55:27 GMT, Viktor Klang wrote: >> I'm breaking this change out as a separate improvement, since it will not be >> generally possible to adjust these limits on the j.u.c primitives since they >> might already use a backing `long` to pack in information which needs to be >>

Re: RFR: 8352971: Increase maximum number of hold counts for ReentrantReadWriteLock [v2]

2025-04-07 Thread Viktor Klang
On Wed, 2 Apr 2025 13:09:01 GMT, Viktor Klang wrote: >> test/jdk/java/util/concurrent/tck/ReentrantReadWriteLock20Test.java line 94: >> >>> 92: next.join(); >>> 93: } catch (InterruptedException ie) { >>> 94: } >> >> I don't think

Re: RFR: 8352971: Increase maximum number of hold counts for ReentrantReadWriteLock

2025-04-05 Thread Alan Bateman
On Thu, 27 Mar 2025 11:30:11 GMT, Alan Bateman wrote: >> I'm breaking this change out as a separate improvement, since it will not be >> generally possible to adjust these limits on the j.u.c primitives since they >> might already use a backing `long` to pack in information which needs to be >

Re: RFR: 8352971: Increase maximum number of hold counts for ReentrantReadWriteLock

2025-04-05 Thread Alan Bateman
On Wed, 26 Mar 2025 16:19:16 GMT, Viktor Klang wrote: > I'm breaking this change out as a separate improvement, since it will not be > generally possible to adjust these limits on the j.u.c primitives since they > might already use a backing `long` to pack in information which needs to be > up

Re: RFR: 8352971: Increase maximum number of hold counts for ReentrantReadWriteLock

2025-04-02 Thread Viktor Klang
On Wed, 2 Apr 2025 09:36:51 GMT, Alan Bateman wrote: >> I'm breaking this change out as a separate improvement, since it will not be >> generally possible to adjust these limits on the j.u.c primitives since they >> might already use a backing `long` to pack in information which needs to be >>

Re: RFR: 8352971: Increase maximum number of hold counts for ReentrantReadWriteLock

2025-03-28 Thread Roger Riggs
On Wed, 26 Mar 2025 16:19:16 GMT, Viktor Klang wrote: > I'm breaking this change out as a separate improvement, since it will not be > generally possible to adjust these limits on the j.u.c primitives since they > might already use a backing `long` to pack in information which needs to be > up

Re: RFR: 8352971: Increase maximum number of hold counts for ReentrantReadWriteLock

2025-03-28 Thread Viktor Klang
On Fri, 28 Mar 2025 16:27:28 GMT, Roger Riggs wrote: >> I'm breaking this change out as a separate improvement, since it will not be >> generally possible to adjust these limits on the j.u.c primitives since they >> might already use a backing `long` to pack in information which needs to be >>

Re: RFR: 8352971: Increase maximum number of hold counts for ReentrantReadWriteLock

2025-03-28 Thread Roger Riggs
On Wed, 26 Mar 2025 16:19:16 GMT, Viktor Klang wrote: > I'm breaking this change out as a separate improvement, since it will not be > generally possible to adjust these limits on the j.u.c primitives since they > might already use a backing `long` to pack in information which needs to be > up

Re: RFR: 8352971: Increase maximum number of hold counts for ReentrantReadWriteLock

2025-03-28 Thread Viktor Klang
On Thu, 27 Mar 2025 11:30:11 GMT, Alan Bateman wrote: >> I'm breaking this change out as a separate improvement, since it will not be >> generally possible to adjust these limits on the j.u.c primitives since they >> might already use a backing `long` to pack in information which needs to be >

Re: RFR: 8352971: Increase maximum number of hold counts for ReentrantReadWriteLock

2025-03-28 Thread Viktor Klang
On Thu, 27 Mar 2025 11:30:11 GMT, Alan Bateman wrote: >> I'm breaking this change out as a separate improvement, since it will not be >> generally possible to adjust these limits on the j.u.c primitives since they >> might already use a backing `long` to pack in information which needs to be >

Re: RFR: 8352971: Increase maximum number of hold counts for ReentrantReadWriteLock

2025-03-27 Thread Alan Bateman
On Wed, 26 Mar 2025 16:19:16 GMT, Viktor Klang wrote: > I'm breaking this change out as a separate improvement, since it will not be > generally possible to adjust these limits on the j.u.c primitives since they > might already use a backing `long` to pack in information which needs to be > up