Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl.

[Jeremy Chadwick]

On Wed, May 14, 2008 at 11:39:10PM +0300, Evren Yurtesen wrote:
> Approaching the limit on PV entries, consider increasing either the 
> vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl.
> Approaching the limit on PV entries, consider increasing either the 
> vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl.

I've seen this message on one of our i386 RELENG_7 boxes, which has a
medium load (webserver with PHP) and 2GB RAM.  Our counters, for
comparison:

vm.pmap.pmap_collect_active: 0
vm.pmap.pmap_collect_inactive: 0
vm.pmap.pv_entry_spare: 7991
vm.pmap.pv_entry_allocs: 807863761
vm.pmap.pv_entry_frees: 807708792
vm.pmap.pc_chunk_tryfail: 0
vm.pmap.pc_chunk_frees: 2580082
vm.pmap.pc_chunk_allocs: 2580567
vm.pmap.pc_chunk_count: 485
vm.pmap.pv_entry_count: 154969
vm.pmap.shpgperproc: 200
vm.pmap.pv_entry_max: 1745520

-- 
| Jeremy Chadwick                                jdc at parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                  Mountain View, CA, USA |
| Making life hard for others since 1977.              PGP: 4BD6C0CB |