Re: RFR: 8276660: Scalability bottleneck in java.security.Provider.getService() [v2]

2021-11-29 Thread Valerie Peng
On Mon, 29 Nov 2021 23:10:03 GMT, Weijun Wang wrote: >> Valerie Peng has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Updated to use pattern matching with instanceof operator. > > src/java.base/share/classes/java/security/Provider.java li

Re: RFR: 8276660: Scalability bottleneck in java.security.Provider.getService() [v2]

2021-11-29 Thread Valerie Peng
On Tue, 23 Nov 2021 15:02:55 GMT, Weijun Wang wrote: >> Valerie Peng has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Updated to use pattern matching with instanceof operator. > > src/java.base/share/classes/java/security/Provider.java li

Re: RFR: 8276660: Scalability bottleneck in java.security.Provider.getService() [v2]

2021-11-29 Thread Valerie Peng
On Thu, 25 Nov 2021 10:42:14 GMT, Andrey Turbanov wrote: >> Valerie Peng has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Updated to use pattern matching with instanceof operator. > > src/java.base/share/classes/java/security/Provider.jav

Re: RFR: 8276660: Scalability bottleneck in java.security.Provider.getService() [v2]

2021-11-29 Thread Valerie Peng
On Thu, 25 Nov 2021 10:41:32 GMT, Andrey Turbanov wrote: >> Valerie Peng has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Updated to use pattern matching with instanceof operator. > > src/java.base/share/classes/java/security/Provider.jav

Re: RFR: 8276660: Scalability bottleneck in java.security.Provider.getService() [v2]

2021-11-29 Thread Weijun Wang
On Wed, 24 Nov 2021 21:17:34 GMT, Valerie Peng wrote: >> It is observed that when running crypto benchmark with large number of >> threads, a lot of time is spent on the synchronized block inside the >> Provider.getService() method. The cause for this is that >> Provider.getService() method fi

RFR: 8277881 Missing SessionID in TLS1.3 resumption in compatibility mode

2021-11-29 Thread Daniel JeliƄski
All TLS 1.3 handshakes in compatibility mode must send a non-empty SessionID field. Currently TLS1.3 session resumptions are sending empty session ID. This patch fixes that problem. All jdk_core tests passed. The newly added check passes with the patch, fails without it. - Commit