summaryrefslogtreecommitdiffstats
path: root/sys/opencrypto
Commit message (Collapse)AuthorAgeFilesLines
* Bow to the whining masses and change a union back into void *. Retaindillon2003-01-131-4/+4
| | | | | removal of unnecessary casts and throw in some minor cleanups to see if anyone complains, just for the hell of it.
* Change struct file f_data to un_data, a union of the correct structdillon2003-01-121-4/+4
| | | | | | | | | | pointer types, and remove a huge number of casts from code using it. Change struct xfile xf_data to xun_data (ABI is still compatible). If we need to add a #define for f_data and xf_data we can, but I don't think it will be necessary. There are no operational changes in this commit.
* Invoke the driver directly when a request is submitted via crypto_dispatchsam2003-01-091-21/+52
| | | | | | | | | | | | | | | or crypto_kdispatch unless the driver is currently blocked. This eliminates the context switch to the dispatch thread for virtually all requests. Note that this change means that for software crypto drivers the caller will now block until the request is completed and the callback is dispatched to the callback thread (h/w drivers will typically just dispatch the op to the device and return quickly). If this is an issue we can either implement a non-blocking interface in the s/w crypto driver or use either the "no delay" flag in the crypto request or the "software driver" capability flag to control what to do. Sponsored by: Vernier Networks
* correct flags passed when allocation crypto request structures so wesam2003-01-061-2/+2
| | | | don't block and the returned data is zero'd
* manage kernel threads properly; especially shutting them down on module unloadsam2003-01-031-52/+133
| | | | Reviewed by: jhb
* MFS: crypto timing support; purge usercrypto sysctl (just don't configsam2003-01-033-9/+107
| | | | | | | | cryptodev or kldunload cryptodev module); crypto statistcs; remove unused alloctype field from crypto op to offset addition of the performance time stamp Supported by: Vernier Networks
* correct minor # in make_dev callsam2002-11-081-1/+1
| | | | Submitted by: Doug Ambrisko" <ambrisko@verniernetworks.com>
* change load order so module is present before crypto driverssam2002-11-081-1/+1
| | | | Submitted by: Doug Ambrisko" <ambrisko@verniernetworks.com>
* Module-ize the 'core' crypto stuff. This may still need to be compiledmarkm2002-10-162-3/+31
| | | | | | | | | into the kernel by default (if required), but other modules can now depend() on this. Fix inter-module dependancy. Earlier version OK'ed by: sam
* Change iov_base's type from `char *' to the standard `void *'. Allmike2002-10-111-1/+1
| | | | | uses of iov_base which assume its type is `char *' (in order to do pointer arithmetic) have been updated to cast iov_base to `char *'.
* o split crypto_proc into two threads: one for processing requests and onesam2002-10-071-52/+92
| | | | | | for processing callbacks. This closes race conditions caused by locking too many things with a single mutex. o reclaim crypto requests under certain (impossible) failure conditions
* remove CIOGSSESSION (get software session); it was added only for testingsam2002-10-072-4/+1
|
* In-kernel crypto framework derived from openbsd. This facility providessam2002-10-0421-0/+7317
a consistent interface to h/w and s/w crypto algorithms for use by the kernel and (for h/w at least) by user-mode apps. Access for user-level code is through a /dev/crypto device that'll eventually be used by openssl to (potentially) accelerate many applications. Coming soon is an IPsec that makes use of this service to accelerate ESP, AH, and IPCOMP protocols. Included here is the "core" crypto support, /dev/crypto driver, various crypto algorithms that are not already present in the KAME crypto area, and support routines used by crypto device drivers. Obtained from: openbsd
OpenPOWER on IntegriCloud