Date: Wed, 20 Jan 2021 00:28:23 +0000 From: bugzilla-noreply@freebsd.org To: geom@FreeBSD.org Subject: [Bug 242747] geli: AMD Epyc+GELI not using Hardware AES Message-ID: <bug-242747-14739-pAQRldVJst@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-242747-14739@https.bugs.freebsd.org/bugzilla/> References: <bug-242747-14739@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242747 --- Comment #30 from Eirik Oeverby <ltning-freebsd@anduin.net> --- (In reply to Alan Somers from comment #29) I see. I only have this in pciconf -lv (this is from 12.2): none19@pci0:34:0:1: class=3D0x108000 card=3D0x14861022 chip=3D0x1486102= 2 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices, Inc. [AMD]' device =3D 'Starship/Matisse Cryptographic Coprocessor PSPCPP' class =3D encrypt/decrypt none40@pci0:162:0:1: class=3D0x108000 card=3D0x14861022 chip=3D0x1486102= 2 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices, Inc. [AMD]' device =3D 'Starship/Matisse Cryptographic Coprocessor PSPCPP' class =3D encrypt/decrypt There seems to be one per CPU socket (the device shows up twice). I don't know if this is indeed covered by the ccp driver, but I can't find = any documentation on it and the discussion https://reviews.freebsd.org/D12723 s= eems to indicate it's not really useful..? Anyway, I'd be happy to test if there's anything meaningful I can do on 12.= 2. I don't have a 13-system on EPYC (yet), but the promise of serious crypto performance might motivate me to change that. That said, our pain is mostly= on handshake (RSA), not stream (AES).. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-242747-14739-pAQRldVJst>