From owner-freebsd-stable@FreeBSD.ORG Sun Jun 18 02:31:49 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8085E16A479 for ; Sun, 18 Jun 2006 02:31:49 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28C6343D45 for ; Sun, 18 Jun 2006 02:31:49 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.4) id k5I2Vm2w023087; Sat, 17 Jun 2006 21:31:48 -0500 (CDT) (envelope-from dan) Date: Sat, 17 Jun 2006 21:31:48 -0500 From: Dan Nelson To: "Marc G. Fournier" Message-ID: <20060618023148.GJ74191@dan.emsphone.com> References: <20060617164334.K1114@ganymede.hub.org> <20060617165626.V1114@ganymede.hub.org> <20060617200755.GG74191@dan.emsphone.com> <20060617182336.O1114@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060617182336.O1114@ganymede.hub.org> X-OS: FreeBSD 5.5-PRERELEASE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: 6.1: kern.ipc.maxpipekva X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jun 2006 02:31:49 -0000 In the last episode (Jun 17), Marc G. Fournier said: > On Sat, 17 Jun 2006, Dan Nelson wrote: > >In the last episode (Jun 17), Marc G. Fournier said: > >>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 ... > > > >Try also running "sysctl kern.ipc | grep pipe", which will also tell > >you how many pipes are in use, plus some other counters. The > >comment at the top of sys/kern/sys_pipe.c explains how pipes are > >given memory. > > What uses all of these pipes? right now, with 97 jails running: > > kern.ipc.maxpipekva: 25165824 > kern.ipc.pipes: 7038 > kern.ipc.pipekva: 22179840 > kern.ipc.pipefragretry: 0 > kern.ipc.pipeallocfail: 0 > kern.ipc.piperesizefail: 0 > kern.ipc.piperesizeallowed: 1 > > That is an average of 7 pipes per process: > > pluto# ps aux | wc -l > 1326 "fstat | grep pipe" will tell you what processes have them open on what fds. pipes on fds 0, 1 and 2 are probably from shell pipelines. -- Dan Nelson dnelson@allantgroup.com