summaryrefslogtreecommitdiff
path: root/sys/uvm/uvm_pdaemon.c
diff options
context:
space:
mode:
authorTed Unangst <tedu@cvs.openbsd.org>2006-05-07 20:06:51 +0000
committerTed Unangst <tedu@cvs.openbsd.org>2006-05-07 20:06:51 +0000
commit4a02f1bb86ffaf58c243035d5c3117d4611db8eb (patch)
tree2d3d10f3a3aef857bc7cecfe6cf9f57e61c4365a /sys/uvm/uvm_pdaemon.c
parent745fde2efc1d5a927b48753f6c63fc546ba876a4 (diff)
remove drain hooks from pool.
1. drain hooks and lists of allocators make the code complicated 2. the only hooks in the system are the mbuf reclaim routines 3. if reclaim is actually able to put a meaningful amount of memory back in the system, i think something else is dicked up. ie, if reclaiming your ip fragment buffers makes the difference thrashing swap and not, your system is in a load of trouble. 4. it's a scary amount of code running with very weird spl requirements and i'd say it's pretty much totally untested. raise your hand if your router is running at the edge of swap. 5. the reclaim stuff goes back to when mbufs lived in a tiny vm_map and you could run out of va. that's very unlikely (like impossible) now. ok/tested pedro krw sturm
Diffstat (limited to 'sys/uvm/uvm_pdaemon.c')
-rw-r--r--sys/uvm/uvm_pdaemon.c5
1 files changed, 1 insertions, 4 deletions
diff --git a/sys/uvm/uvm_pdaemon.c b/sys/uvm/uvm_pdaemon.c
index e011f925412..95b97114504 100644
--- a/sys/uvm/uvm_pdaemon.c
+++ b/sys/uvm/uvm_pdaemon.c
@@ -1,4 +1,4 @@
-/* $OpenBSD: uvm_pdaemon.c,v 1.25 2002/05/24 13:10:53 art Exp $ */
+/* $OpenBSD: uvm_pdaemon.c,v 1.26 2006/05/07 20:06:50 tedu Exp $ */
/* $NetBSD: uvm_pdaemon.c,v 1.23 2000/08/20 10:24:14 bjh21 Exp $ */
/*
@@ -222,9 +222,6 @@ uvm_pageout(void *arg)
uvmexp.pdwoke++;
UVMHIST_LOG(pdhist," <<WOKE UP>>",0,0,0,0);
- /* drain pool resources */
- pool_drain(0);
-
/*
* now lock page queues and recompute inactive count
*/