Date: Sun, 18 Jun 2006 00:38:07 +0400 (MSD) From: Maxim Konovalov <maxim@macomnet.ru> To: "Marc G. Fournier" <scrappy@hub.org> Cc: freebsd-stable@freebsd.org Subject: Re: 6.1: kern.ipc.maxpipekva Message-ID: <20060618003223.J49605@mp2.macomnet.net> In-Reply-To: <20060617172245.C1114@ganymede.hub.org> References: <20060617164334.K1114@ganymede.hub.org> <20060617234931.W41802@mp2.macomnet.net> <20060617172245.C1114@ganymede.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 17 Jun 2006, 17:23-0300, Marc G. Fournier wrote: > On Sat, 17 Jun 2006, Maxim Konovalov wrote: > > > On Sat, 17 Jun 2006, 16:44-0300, Marc G. Fournier wrote: > > > > > > > > Jun 17 16:00:03 pluto kernel: kern.ipc.maxpipekva exceeded; see tuning(7) > > > Jun 17 16:00:04 pluto kernel: kern.ipc.maxpipekva exceeded; see tuning(7) > > > > I thought about removing this reference but then decided that better > > to add a couple of words to tuning(7) man page (and didn't add). > > > > > but I can't seem to find anything in tuning(7) about it ... so, what > > > is it and how do I monitor for it? > > > > kern/sys_pipe.c: > > > > * In order to limit the resource use of pipes, two sysctls exist: > > * > > * kern.ipc.maxpipekva - This is a hard limit on the amount of pageable > > * address space available to us in pipe_map. This value is normally > > * autotuned, but may also be loader tuned. > > * > > * kern.ipc.pipekva - This read-only sysctl tracks the current amount of > > * memory in use by pipes. > > See my other note, but I take it just adding: > > kern.ipc.maxpipekva=25165824 > > and reboot is the wrong thing to do, since the server didn't come back :( Increase KVA_PAGES, see /sys/i386/conf/NOTES for details. -- Maxim Konovalov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060618003223.J49605>