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) but I can't seem to find anything in tuning(7) about it ... so, what is it and how do I monitor for it? thanks ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
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. -- Maxim Konovalov
On Sat, 17 Jun 2006, 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) > > but I can't seem to find anything in tuning(7) about it ... so, what is it > and how do I monitor for it?More on this: # sysctl -a | grep pipekva kern.ipc.maxpipekva: 16777216 kern.ipc.pipekva: 15122432 and I just rebooted the server ... so obviously I've been living on the edge ... not sure what to increase it to, since not sure what it affects, so will wait on responses ... thx ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664