From owner-freebsd-isp Tue Sep 24 22:30:56 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA03828 for isp-outgoing; Tue, 24 Sep 1996 22:30:56 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA03803 for ; Tue, 24 Sep 1996 22:30:53 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id WAA05649; Tue, 24 Sep 1996 22:31:57 -0700 (PDT) Message-Id: <199609250531.WAA05649@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Jim Shankland cc: freebsd-isp@freebsd.org, robseco@wizard.teksupport.net.au Subject: Re: mb_map full In-reply-to: Your message of "Tue, 24 Sep 1996 09:30:24 PDT." <199609241630.JAA13814@saguaro.flyingfox.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 24 Sep 1996 22:31:57 -0700 Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >David Greenman writes: > >> The kmem_map full panic was the result of a mis-calculation of >> the size of the map in 2.1R. The calculation didn't account for >> the mb_map being a submap of it, and thus large mb_maps would >> leave little space left over for the [much more important] >> kmem_map. This was fixed in post-2.1 with the following commit: >[ ... ] > >Thanks for the information. But does making the kmem_map larger, >as you described, eliminate the panic, or just make it less Yes, it eliminates the panic. >likely? In other words, is the kmem_map now sized so that it >can never possibly fill up? mbufs, for example (not clusters), >still come out of the kmem_map, and I don't know of any a priori >upper bound on the number of mbufs that can be consumed. It Yes, there is a limit on the allocations that will prevent them from consuming the entire map. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project