Date: Tue, 7 Jul 2020 16:36:32 -0600 From: Alan Somers <asomers@freebsd.org> To: Mark Johnston <markj@freebsd.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: Hardware crypto card wanted Message-ID: <CAOtMX2gxgR9ZC=jTcgqLsiuQk0M3gKwLSd3%2BOEj-XmdMwH8eKQ@mail.gmail.com> In-Reply-To: <20200707222408.GA51619@raichu> References: <CAOtMX2jd1zzFAkBiM8MqCsW7n-x-oucpR759gpW02=wQSpF8MA@mail.gmail.com> <20200707222408.GA51619@raichu>
next in thread | previous in thread | raw e-mail | index | archive | help
Yeah, just apply the patch and run the geli tests. The patch add one additional geli test, too. IIUC, geli doesn't use the thread pool when it's using hardware crypto, which is why I think it's important that change be tested both ways. The change is here: https://reviews.freebsd.org/D25587 -Alan On Tue, Jul 7, 2020 at 4:24 PM Mark Johnston <markj@freebsd.org> wrote: > On Tue, Jul 07, 2020 at 03:18:02PM -0600, alan somers wrote: > > I'm working on a change to geli, but I need to test it on a system with a > > hardware crypto card. Not merely one with AES-NI, but one of the old > > fashioned PCI kind that works with crypto(9). Would anybody who runs > > CURRENT on such a machine be willing to test my patch for me? > > I'm finishing work on a new hardware crypto driver and can test if you > like. Do you want to run the existing GELI tests with the patch > applied, or something else? > > I don't quite understand why GELI would care about the distinction, > though. Doesn't GELI use AES-NI via crypto(9) as well? >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2gxgR9ZC=jTcgqLsiuQk0M3gKwLSd3%2BOEj-XmdMwH8eKQ>