Date: Thu, 11 Jan 2018 08:24:11 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: cem@freebsd.org Cc: "freebsd-arch@freebsd.org" <arch@freebsd.org> Subject: Re: Ranting about OCF / crypto(9) Message-ID: <52053.1515659051@critter.freebsd.dk> In-Reply-To: <CAG6CVpXdCT2=fdRXe77Q6m0126ZYPa%2Bx4AdH6NZ4Sk-fyztVAg@mail.gmail.com> References: <3790717.UIxaijsHl3@ralph.baldwin.cx> <51883.1515656784@critter.freebsd.dk> <CAG6CVpXdCT2=fdRXe77Q6m0126ZYPa%2Bx4AdH6NZ4Sk-fyztVAg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- In message <CAG6CVpXdCT2=3DfdRXe77Q6m0126ZYPa+x4AdH6NZ4Sk-fyztVAg@mail.gma= il.com> , Conrad Meyer writes: >But, embedding lua or something like lua in the kernel is completely >tangential to the problem of providing a good generic interface for >crypto hardware. Please don't hijack this thread with that >discussion. The problem is not the interface to the crypto hardware, but getting the data to and from the crypto hardware in the first place. You can either drown yourself in special cases (IPSEC, HTTPS, ...) with a "good generic interface for crypto hardware", or you can solve the actual problem, with a A Good Generic Interface For Data Streams. But don't let me distract you with my experience here, I only spent years on it... -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= .
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52053.1515659051>