[Midnightbsd-cvs] src [8774] trunk/sys/kern/subr_blist.c: remove reference to the rlist code from comments.
laffer1 at midnightbsd.org
laffer1 at midnightbsd.org
Sun Sep 25 22:57:23 EDT 2016
Revision: 8774
http://svnweb.midnightbsd.org/src/?rev=8774
Author: laffer1
Date: 2016-09-25 22:57:23 -0400 (Sun, 25 Sep 2016)
Log Message:
-----------
remove reference to the rlist code from comments.
Modified Paths:
--------------
trunk/sys/kern/subr_blist.c
Modified: trunk/sys/kern/subr_blist.c
===================================================================
--- trunk/sys/kern/subr_blist.c 2016-09-26 02:56:30 UTC (rev 8773)
+++ trunk/sys/kern/subr_blist.c 2016-09-26 02:57:23 UTC (rev 8774)
@@ -52,14 +52,10 @@
* radix tree should be able to operate well no matter how much
* fragmentation there is and no matter how large a bitmap is used.
*
- * Unlike the rlist code, the blist code wires all necessary memory at
- * creation time. Neither allocations nor frees require interaction with
- * the memory subsystem. In contrast, the rlist code may allocate memory
- * on an rlist_free() call. The non-blocking features of the blist code
- * are used to great advantage in the swap code (vm/nswap_pager.c). The
- * rlist code uses a little less overall memory than the blist code (but
- * due to swap interleaving not all that much less), but the blist code
- * scales much, much better.
+ * The blist code wires all necessary memory at creation time. Neither
+ * allocations nor frees require interaction with the memory subsystem.
+ * The non-blocking features of the blist code are used in the swap code
+ * (vm/swap_pager.c).
*
* LAYOUT: The radix tree is layed out recursively using a
* linear array. Each meta node is immediately followed (layed out
More information about the Midnightbsd-cvs
mailing list