Approaching the limit on PV entries, consider increasing
either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl.
Thomas Hurst
tom.hurst at clara.net
Fri May 16 18:20:47 UTC 2008
* Evren Yurtesen (yurtesen at ispro.net) wrote:
> I guess one good question is, how can one see the number of PV entries
> used by a process? shouldnt these appear in the output of ipcs -a
> command?
No, PV entries are a VM thing, not limited to SysV IPC.
> Another good question is, in many places there is references to
> rebooting after putting a new vm.pmap.shpgperproc value to
> loader.conf. However I just changed this on a running system, has it
> really been changed or was I suppose to reboot?
Looking at the code it should be fine, the limit's just a couple of
integers.
> In either case, I already increased vm.pmap.shpgperproc to 2000 (from
> 200) and still the error occurs, there is not so much load on this
> box, maybe there is a leak somewhere?
What sort of load is there? Do you have a bunch of big processes
sharing significant chunks of memory in any way?
--
Thomas 'Freaky' Hurst
http://hur.st/
More information about the freebsd-stable
mailing list