From: bouceklubos@8df170851b19ab991c23c19bba526b63d8659adb <bouceklubos@web>
Date: Fri, 13 Oct 2017 09:54:49 +0000 (+0000)
Subject: Remove per-cpu karc4random project (completed by sephe in Jan 2017)
X-Git-Url: https://gitweb.dragonflybsd.org/ikiwiki.git/commitdiff_plain/82c64b0421bb9fe87db6ae126a8cbc9bc3d4def4

Remove per-cpu karc4random project (completed by sephe in Jan 2017)
---

diff --git a/docs/developer/ProjectsPage.mdwn b/docs/developer/ProjectsPage.mdwn
index a0d8941f..c1ada651 100644
--- a/docs/developer/ProjectsPage.mdwn
+++ b/docs/developer/ProjectsPage.mdwn
@@ -189,10 +189,6 @@ killall recently gained a -T flag to kill all descendents of a tty, bring this f
 ### Tear out condvars
 * Conditional vars -- condvar(9), could be replaced with other locking primitives and our tsleep/wakeup interlock.
 
-### Make karc4random in libkern per-cpu (or at least wrap its own token around it)
-* Verify that it is possible and safe to do this, what care would need to be taken, especially with respect to the random seeding?
-* Pull out locks around calls to karc4rand*
-
 ### Partially rewrite buffer cache
 * Buffer cache buffers map VM pages from the filesystems VM-backed vnodes, the "buffer space" is the maximum amount of virtual space to allocate to these buffers.
 * When the buffer_map KVA space gets fragmented it caused very expensive defrag operations, the buffer_map KVA was recently increased to double the actual buffer space to allow full space utilization in the face of fragmentation and reduce the frequency of defrag operations.