Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Retire the MALLOC and FREE macros. They are an abomination unto style(9). | des | 2008-10-23 | 1 | -7/+7 |
| | | | | MFC after: 3 months | ||||
* | malloc.h relies on param.h for a definition of MAXCPU. I guess that there is | scottl | 2005-05-30 | 1 | -0/+1 |
| | | | | | other header pollution that makes this work right now, but it falls over when doing a RELENG_5 -> HEAD upgrade. | ||||
* | /* -> /*- for license, minor formatting changes | imp | 2005-01-07 | 1 | -1/+1 |
| | |||||
* | Use __FBSDID(). | obrien | 2003-06-11 | 1 | -1/+3 |
| | |||||
* | In-kernel crypto framework derived from openbsd. This facility provides | sam | 2002-10-04 | 1 | -0/+189 |
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 |