From owner-freebsd-current@FreeBSD.ORG Tue Jan 20 00:57:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADF9D16A4CE for ; Tue, 20 Jan 2004 00:57:24 -0800 (PST) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id C474943D41 for ; Tue, 20 Jan 2004 00:57:22 -0800 (PST) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id B8BF6530A; Tue, 20 Jan 2004 09:57:21 +0100 (CET) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id B35805308; Tue, 20 Jan 2004 09:56:59 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 2602) id 4550D33C6A; Tue, 20 Jan 2004 09:56:59 +0100 (CET) To: Peter Losher References: <200401191506.07789.Peter_Losher@isc.org> From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) Date: Tue, 20 Jan 2004 09:56:59 +0100 In-Reply-To: <200401191506.07789.Peter_Losher@isc.org> (Peter Losher's message of "Mon, 19 Jan 2004 15:06:07 -0800") Message-ID: User-Agent: Gnus/5.090024 (Oort Gnus v0.24) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on flood.des.no X-Spam-Level: ss X-Spam-Status: No, hits=2.6 required=5.0 tests=RCVD_IN_DYNABLOCK, RCVD_IN_SORBS autolearn=no version=2.61 cc: current@freebsd.org Subject: Re: 'kern.maxpipekva exceeded' messages... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 08:57:24 -0000 Peter Losher writes: > In updating one of our authoritiative name servers to 5.2-REL, we enounte= red=20 > after two days of running, kernel message like: > > kern.maxpipekva exceeded, please see tuning(7). > > appearing to the point to where you couldn't ssh into the box (because ss= hd=20 > died w/ too many files opened). I see so mention of kern.maxpipekva on t= he=20 > tuning man page, and greping only finds kern.ipc entries. > > % sysctl -a | grep pipekva > kern.ipc.maxpipekva: 10485760 > kern.ipc.maxpipekvawired: 5242880 > kern.ipc.pipekva: 131072 > kern.ipc.pipekvawired: 0 > > Are they the same, and if so, what's are the guidelines for increasing th= e=20 > number? yes, the error message is incorrect. here's an excerpt from comment in the kernel sources: * 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. Whenever the amount in use * exceeds half of this value, all new pipes will be created with size * SMALL_PIPE_SIZE, rather than PIPE_SIZE. Big pipe creation will be limit= ed * as well. This value is loader tunable only. * * kern.ipc.maxpipekvawired - This value limits the amount of memory that m= ay * be wired in order to facilitate direct copies using page flipping. * Whenever this value is exceeded, pipes will fall back to using regular * copies. This value is sysctl controllable at all times. * * These values are autotuned in subr_param.c. * * Memory usage may be monitored through the sysctls * kern.ipc.pipes, kern.ipc.pipekva and kern.ipc.pipekvawired. You can set these variables in /boot/loader.conf. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no