Date: Fri, 16 May 2008 19:20:44 +0100 From: Thomas Hurst <tom.hurst@clara.net> To: Evren Yurtesen <yurtesen@ispro.net> Cc: Jeremy Chadwick <koitsu@FreeBSD.org>, freebsd-stable@freebsd.org Subject: Re: Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl. Message-ID: <20080516182044.GA5921@voi.aagh.net> In-Reply-To: <482BE398.8010203@ispro.net> References: <482B4DEE.3050705@ispro.net> <20080515010347.GA85202@eos.sc1.parodius.com> <482BE398.8010203@ispro.net>
next in thread | previous in thread | raw e-mail | index | archive | help
* Evren Yurtesen (yurtesen@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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080516182044.GA5921>