summaryrefslogtreecommitdiffstats
path: root/lib/libpthread/thread/thr_create.c
diff options
context:
space:
mode:
authoralc <alc@FreeBSD.org>2003-05-23 19:54:02 +0000
committeralc <alc@FreeBSD.org>2003-05-23 19:54:02 +0000
commit53638c7027cec977f4b8b80b0c575119b1a1af75 (patch)
tree56f394df47cc45b1b10033871b27033c2d57128f /lib/libpthread/thread/thr_create.c
parent3a5ee925b1f041a25eb7425baa290b7c06304ebf (diff)
downloadFreeBSD-src-53638c7027cec977f4b8b80b0c575119b1a1af75.zip
FreeBSD-src-53638c7027cec977f4b8b80b0c575119b1a1af75.tar.gz
Make the maximum number of vnodes a function of both the physical memory
size and the kernel's heap size, specifically, vm_kmem_size. This function allows a maximum of 40% of the vm_kmem_size to be used for vnodes and vm objects. This is a conservative bound based upon recent problem reports. (In other words, a slight increase in this percentage may be safe.) Finally, machines with less than ~3GB of RAM should be unaffected by this change, i.e., the maximum number of vnodes should remain the same. If necessary, machines with 3GB or more of RAM can increase the maximum number of vnodes by increasing vm_kmem_size. Desired by: scottl Tested by: jake Approved by: re (rwatson,scottl)
Diffstat (limited to 'lib/libpthread/thread/thr_create.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud