src/sys/dev/random/yarrow.h, branch release/6.3.0 FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F6.3.0 2004-04-09T15:47:10Z Reorganise the entropy device so that high-yield entropy sources 2004-04-09T15:47:10Z Mark Murray markm@FreeBSD.org 2004-04-09T15:47:10Z urn:sha1:e7806b4c0eb398aba8b6e8ddeda96e6ddd9305ae can more easily be used INSTEAD OF the hard-working Yarrow. The only hardware source used at this point is the one inside the VIA C3 Nehemiah (Stepping 3 and above) CPU. More sources will be added in due course. Contributions welcome! Staticise the random_state array. 2002-01-10T00:09:21Z Mike Smith msmith@FreeBSD.org 2002-01-10T00:09:21Z urn:sha1:5390e1bc8fe871d8ca5ddcd288d918b1c538b4b5 Reviewed by: markm Very large makeover of the /dev/random driver. 2001-03-10T12:51:55Z Mark Murray markm@FreeBSD.org 2001-03-10T12:51:55Z urn:sha1:02c986ab5491cfc84666b5ce658dd7b3508b6b93 o Separate the kernel stuff from the Yarrow algorithm. Yarrow is now well contained in one source file and one header. o Replace the Blowfish-based crypto routines with Rijndael-based ones. (Rijndael is the new AES algorithm). The huge improvement in Rijndael's key-agility over Blowfish means that this is an extremely dramatic improvement in speed, and makes a heck of a difference in its (lack of) CPU load. o Clean up the sysctl's. At BDE's prompting, I have gone back to static sysctls. o Bug fixes. The streamlining of the crypto stuff enabled me to find and fix some bugs. DES also found a bug in the reseed routine which is fixed. o Change the way reseeds clear "used" entropy. Previously, only the source(s) that caused a reseed were cleared. Now all sources in the relevant pool(s) are cleared. o Code tidy-up. Mostly to make it (nearly) 80-column compliant. Make a big improvement to entropy-harvesting speed by not having any 2001-02-11T16:21:35Z Mark Murray markm@FreeBSD.org 2001-02-11T16:21:35Z urn:sha1:d70736850e33be1a1210eeabcdb8f49f135ff25c locks (only atomic assigns) in the harvest ringbuffer. Remove NOBLOCKRANDOM as a compile-time option. Instead, provide 2001-01-14T17:50:15Z Mark Murray markm@FreeBSD.org 2001-01-14T17:50:15Z urn:sha1:b79ad7e6425665aa15a2b684fb309b9809dc736b exactly the same functionality via a sysctl, making this feature a run-time option. The default is 1(ON), which means that /dev/random device will NOT block at startup. setting kern.random.sys.seeded to 0(OFF) will cause /dev/random to block until the next reseed, at which stage the sysctl will be changed back to 1(ON). While I'm here, clean up the sysctls, and make them dynamic. Reviewed by: des Tested on Alpha by: obrien Major speedup to /dev/random and the kernel thread that reseeds it. 2000-12-02T18:40:16Z Mark Murray markm@FreeBSD.org 2000-12-02T18:40:16Z urn:sha1:84d4f509f028145ca2f9519734a32a2acabfcfb9 There is no more TAILQ fifo to harvest the entropy; instead, there is a circular buffer of constant size (changeable by macro) that pretty dramatically improves the speed and fixes potential slowdowns- by-locking. Also gone are a slew of malloc(9) and free(9) calls; all harvesting buffers are static. All-in-all, this is a good performance improvement. Thanks-to: msmith for the circular buffer concept-code. Greatly improve the boot-up unblocking time of the entropy device. 2000-11-25T19:13:29Z Mark Murray markm@FreeBSD.org 2000-11-25T19:13:29Z urn:sha1:50636159236da07a17f6a05b05e3787ff1c4cd51 More comment changing. Keep documentation in one place. 2000-11-25T18:00:54Z Mark Murray markm@FreeBSD.org 2000-11-25T18:00:54Z urn:sha1:caccf5c4004d8518d62fb40b38d53133af4c4bcb Correct a comment. This represents a very minor policy change of my 2000-11-25T17:58:11Z Mark Murray markm@FreeBSD.org 2000-11-25T17:58:11Z urn:sha1:24242537f876d200ddb557b23a343e86dc3e4e1c intentions with this code. Stop explicitly using nanotime(9) and use the new get_cyclecounter(9) 2000-11-25T17:09:01Z Mark Murray markm@FreeBSD.org 2000-11-25T17:09:01Z urn:sha1:e73a42f8fb107ecee0fa96a7af9d64073a0072f1 call instead. This makes a pretty dramatic difference to the amount of work that the harvester needs to do - it is much friendlier on the system. (80386 and 80486 class machines will notice little, as the new get_cyclecounter() call is a wrapper round nanotime(9) for them).