From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 08:38:27 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 1BDE516A4CE for ; Tue, 27 Jan 2004 08:38:27 -0800 (PST) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68BE743D62 for ; Tue, 27 Jan 2004 08:37:38 -0800 (PST) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id 129EE530A; Tue, 27 Jan 2004 17:37:16 +0100 (CET) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id 344F95308; Tue, 27 Jan 2004 17:37:06 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 2602) id D91D233C6A; Tue, 27 Jan 2004 17:37:05 +0100 (CET) To: Mike Silbersack References: <20040119233546.S39477@odysseus.silby.com> <20040127101910.P4636@odysseus.silby.com> From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) Date: Tue, 27 Jan 2004 17:37:05 +0100 In-Reply-To: <20040127101910.P4636@odysseus.silby.com> (Mike Silbersack's message of "Tue, 27 Jan 2004 10:24:44 -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 16:38:27 -0000 Mike Silbersack writes: > I do not believe that there is a leak. What actually happened is > that between 5.1 and 5.2 I added pipe memory limits, which had not > been present before. Oh! I wasn't aware that the limit did not already exist. > 1. Pipes overallocate memory greatly; I could probably reduce the > memory usage of an idle pipe by 8x or so. My problem is not idle pipes; my problem is that the following system # sysctl kern.ipc.maxpipekva kern.ipc.maxpipekva: 8704000 # sysctl kern.ipc.pipekva kern.ipc.pipekva: 393216 runs out of pipe kva every monday morning when it tries to pipe a level 0 dump through ssh. Is there some way to impose a limit on the memory consumed by a single pipe? I don't care if dump blocks waiting for ssh to push out the data, but I do care about the system crashing shortly after running out of pipe kva. Another problem I have is with a system that runs out of pipe kva when I create a large number of jails. I really need a way to find out where all that memory goes... > If you're interested in working on this right now, I can send you what I > had planned to do for #1, it would be a very small amount of code, > although it would require a bit of testing to ensure that it does not > degrade the performance of pipes by a noticeable amount. That would be nice. I have several systems I can test it on. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no