patch-2.3.44 linux/mm/vmscan.c

• Lines: 37
• Date: Fri Feb 11 08:38:35 2000
• Orig file: v2.3.43/linux/mm/vmscan.c
• Orig date: Thu Feb 10 17:11:23 2000

diff -u --recursive --new-file v2.3.43/linux/mm/vmscan.c linux/mm/vmscan.c
@@ -457,12 +457,11 @@
  * The background pageout daemon, started as a kernel thread
  * from the init process. 
  *
- * This basically executes once a second, trickling out pages
- * so that we have _some_ free memory available even if there
- * is no other activity that frees anything up. This is needed
- * for things like routing etc, where we otherwise might have
- * all activity going on in asynchronous contexts that cannot
- * page things out.
+ * This basically trickles out pages so that we have _some_
+ * free memory available even if there is no other activity
+ * that frees anything up. This is needed for things like routing
+ * etc, where we otherwise might have all activity going on in
+ * asynchronous contexts that cannot page things out.
  *
  * If there are applications that are active memory-allocators
  * (most normal use), this basically shouldn't matter.
@@ -479,7 +478,7 @@
 	/*
 	 * Tell the memory management that we're a "memory allocator",
 	 * and that if we need more memory we should get access to it
-	 * regardless (see "__get_free_pages()"). "kswapd" should
+	 * regardless (see "__alloc_pages()"). "kswapd" should
 	 * never get caught in the normal page freeing logic.
 	 *
 	 * (Kswapd normally doesn't need memory anyway, but sometimes
@@ -492,9 +491,6 @@
 
 	while (1) {
 		/*
-		 * Wake up once a second to see if we need to make
-		 * more memory available.
-		 *
 		 * If we actually get into a low-memory situation,
 		 * the processes needing more memory will wake us
 		 * up on a more timely basis.