summaryrefslogtreecommitdiffstats
path: root/sys/kern/kern_rwlock.c
diff options
context:
space:
mode:
authortedu <tedu@openbsd.org>2006-05-07 20:06:50 +0000
committertedu <tedu@openbsd.org>2006-05-07 20:06:50 +0000
commit194d7cef06328561d0c3f9f1b776d93722b48a39 (patch)
tree514c0966ee9aba5996781e3b5e4ffdddd718dc43 /sys/kern/kern_rwlock.c
parentOops, correct import this time. (diff)
downloadwireguard-openbsd-194d7cef06328561d0c3f9f1b776d93722b48a39.tar.xz
wireguard-openbsd-194d7cef06328561d0c3f9f1b776d93722b48a39.zip
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/kern/kern_rwlock.c')
0 files changed, 0 insertions, 0 deletions