Thanks a lot for looking at this. The issue seems fixed on my machine.
There are currently several changes being prepared for openssl and I
think I'd rather batch them considering the state of the CI queue but
this will definitely go into Noble. Thanks again.
--
You received this bug
** Patch added: "001-vaes_gcm_avx512.patch"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2030784/+attachment/5754726/+files/001-vaes_gcm_avx512.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in
Hello @adrien-n,
I had Dan Zimmerman take a look at this issue and found a solution.
This is what he shared:
Steps to reproduce:
---
Get Source and apply patch:
git clone https://git.launchpad.net/ubuntu/+source/openssl ubuntu_openssl
cd ubuntu_openssl
git checkout
It might cause performance regressions in production though; would you
be able to document the failing tests here?
I wonder if we would simply have to cherry pick more from 3.2 for these
to pass.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I'm not seeing the issue on 3.2.1. I'm preparing 3.0.13 without the AES
patch and will probably deal with it after the feature freeze at the end
of the month.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
While preparing an update to 3.0.13 for Noble, I started encoutering
testsuite failures.
The cause is the AES patch combined with 3.0.13 (more specifically with the
dupctx patches. The problematic combination looks something like the following:
- AES-GCM-enabled-with-AVX512-vAES-and-vPCLMULQDQ
-
I tested this patch set on a Zen 4 machine too and saw roughly similar
speedups.
And before someone asks: no, I'm not testing that on Via CPUs!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
Thanks a lot for the tests, that's very appreciated.
I ran that on my laptop (11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz)
which quite surprisingly has all these CPU features. Mostly idle,
dynamic CPU governor but no thermal throttling at all (and if there
were, it would probably slow down the
Hi @schopin,
Recommended way to test the relevant code paths would be to use OpenSSL’s
Capability Bits Environment variable. Notes below:
Ubuntu - OpenSSL OPENSSL_ia32cap Environment Variable
OpenSSL Environment variable processor feature bit disable combos for testing.
9 matches
Mail list logo
