From owner-freebsd-stable@FreeBSD.ORG Sat Jun 17 20:07:58 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 94CD816A47C for ; Sat, 17 Jun 2006 20:07:58 +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 45FB743D49 for ; Sat, 17 Jun 2006 20:07:58 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.4) id k5HK7tKG051428; Sat, 17 Jun 2006 15:07:55 -0500 (CDT) (envelope-from dan) Date: Sat, 17 Jun 2006 15:07:55 -0500 From: Dan Nelson To: "Marc G. Fournier" Message-ID: <20060617200755.GG74191@dan.emsphone.com> References: <20060617164334.K1114@ganymede.hub.org> <20060617165626.V1114@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060617165626.V1114@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: Sat, 17 Jun 2006 20:07:58 -0000 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. -- Dan Nelson dnelson@allantgroup.com