That would be the idea (more or less). After all, the kernel does not have
a crypto API at all in comparison to OpenSSL and 'everyone' is using OpenSSL
as their SSL, etc. library. An OpenCrypt library incorporating OpenSSL and
mcrypt as well as mhash might be perfect for an all-crypto-API system which
could then do the hooks to accelerator cards. The accelerator cards would
have kernel drivers, but the library would do the offloading calls. There
is no reason to kernel-space this work.
----- Original Message -----
From: "Strahm, Bill" <bill.strahm@intel.com>
> I do not see how Open SSL can perform this work. What needs to happen is
an
> inline offload processing. In otherwords, what I want to do is rather
than
> using Open SSL I want to go and pass information off to the NIC driver
that
> will tell the NIC to perform the crypto operation...
>
> I do not see how openSSL can help much with this, other than maybe write
> something into SSL that says, if the NIC supports it, don't do crypto, but
> when the packet goes out the wire, do the perscribed crypto operation
> then...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Aug 15 2000 - 21:00:17 EST