Re: RFR: 8280494: (D)TLS signature schemes [v5]

2022-01-29 Thread Xue-Lei Andrew Fan
On Sun, 30 Jan 2022 03:06:35 GMT, Bernd wrote: >> Yes. Array copy is a concern of mine, too. Hopefully, the frozen array >> feature could help address the array copy issues in the future. > > Hmm.. I guess the different packages make it really hard to have an internal > optimized getter. What

Re: RFR: 8280494: (D)TLS signature schemes [v5]

2022-01-29 Thread Xue-Lei Andrew Fan
On Sun, 30 Jan 2022 03:03:37 GMT, Bernd wrote: >> If we want to reuse the result, we may have to cache something. It is not >> good to me. The parsing of the signature scheme names actually depends on >> the provider. So at this point, in the Java SE API specification, it is not >> easy to

Re: RFR: 8280494: (D)TLS signature schemes [v5]

2022-01-29 Thread Xue-Lei Andrew Fan
> This update is to support signature schemes customization for individual > (D)TLS connection. Please review the CSR as well: > CSR: https://bugs.openjdk.java.net/browse/JDK-8280495 > RFE: https://bugs.openjdk.java.net/browse/JDK-8280494 Xue-Lei Andrew Fan has updated the pull request increment

Re: RFR: 8280494: (D)TLS signature schemes [v4]

2022-01-29 Thread Bernd
On Sat, 29 Jan 2022 05:31:08 GMT, Xue-Lei Andrew Fan wrote: >> src/java.base/share/classes/javax/net/ssl/SSLParameters.java line 763: >> >>> 761: >>> 762: String[] tempSchemes = signatureSchemes.clone(); >>> 763: for (String scheme : tempSchemes) { >> >> In addition to this loo

Re: RFR: 8280494: (D)TLS signature schemes [v4]

2022-01-29 Thread Xue-Lei Andrew Fan
> This update is to support signature schemes customization for individual > (D)TLS connection. Please review the CSR as well: > CSR: https://bugs.openjdk.java.net/browse/JDK-8280495 > RFE: https://bugs.openjdk.java.net/browse/JDK-8280494 Xue-Lei Andrew Fan has updated the pull request increment

Re: RFR: 8275914: SHA3: changing java implementation to help C2 create high-performance code

2022-01-29 Thread Anthony Scarpino
On Wed, 15 Dec 2021 09:20:38 GMT, Boris Ulasevich wrote: > Background > > The goal is to improve SHA3 implementation performance as it runs up to two > times slower than native (OpenSSL, measured on AMD64 and AArch6464) > implementation. Some hardware provides SHA3 accelerators, but most (AMD