From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 03:15:38 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 CA0F816A4CE for ; Tue, 27 Jan 2004 03:15:38 -0800 (PST) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4976943D3F for ; Tue, 27 Jan 2004 03:15:22 -0800 (PST) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id F01FF530A; Tue, 27 Jan 2004 12:15:06 +0100 (CET) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id 8855A5308; Tue, 27 Jan 2004 12:14:53 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 2602) id 17E7233C6A; Tue, 27 Jan 2004 12:14:53 +0100 (CET) To: Mike Silbersack References: <20040119233546.S39477@odysseus.silby.com> From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) Date: Tue, 27 Jan 2004 12:14:52 +0100 In-Reply-To: <20040119233546.S39477@odysseus.silby.com> (Mike Silbersack's message of "Mon, 19 Jan 2004 23:37:17 -0600 (CST)") 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: Peter Losher 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, 27 Jan 2004 11:15:38 -0000 Mike Silbersack writes: > Documenting maxpipekva / reducing pipe memory usage is on my to-do list. > Unfortunately, I was unable to complete my changes in time for > 5.2-release; I will try to get them in place soon. We seem to have had a regression in this area since 5.1-RELEASE. Systems that ran fine on 5.1-RELEASE are running out of pipe kva after an upgrade to 5.2-CURRENT. Should we suspect a leak somewhere? DES --=20 Dag-Erling Sm=F8rgrav - des@des.no