From owner-freebsd-current  Mon Jun 26 20:31:20 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id UAA04515
          for current-outgoing; Mon, 26 Jun 1995 20:31:20 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.1])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA04508
          for <freebsd-current@freefall.cdrom.com>; Mon, 26 Jun 1995 20:31:18 -0700
Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id UAA05934; Mon, 26 Jun 1995 20:31:12 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id UAA17759; Mon, 26 Jun 1995 20:31:41 -0700
Message-Id: <199506270331.UAA17759@corbin.Root.COM>
To: Tom Samplonius <tom@uniserve.com>
cc: John Capo <jc@irbs.com>,
        freebsd-current <freebsd-current@freefall.cdrom.com>
Subject: Re: mb_map full with GATEWAY and maxusers 64! 
In-reply-to: Your message of "Mon, 26 Jun 95 19:02:44 PDT."
             <Pine.BSF.3.91.950626190027.582M-100000@haven.uniserve.com> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Mon, 26 Jun 1995 20:31:40 -0700
Sender: current-owner@FreeBSD.org
Precedence: bulk

>
>On Mon, 26 Jun 1995, John Capo wrote:
>
>> I agree with Tom here.  But, it seems to me that there is an
>> underlying problem of some sort.  Why do I have to allow for 4Megs
>> of mbuf clusters to service some unknown transient event.  Once
>> this memory is in the mbuf map, its there forever.
>
>  Running out mbufs doesn't kill your system.  It just means that you 
>drop a few packets.  Only if it happens continuously is it a problem

   Prior to 2.0.5R, it did kill the system.

-DG