From owner-freebsd-stable@FreeBSD.ORG Wed Jun 25 18:03:17 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7676237B401 for ; Wed, 25 Jun 2003 18:03:17 -0700 (PDT) Received: from smtp1.home.se (smtp1.home.se [213.214.194.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DF3744003 for ; Wed, 25 Jun 2003 18:03:16 -0700 (PDT) (envelope-from sandos@home.se) Received: from sandos sandos@home.se [130.243.95.28]Novell NetWare; Thu, 26 Jun 2003 03:02:16 +0200 Message-ID: <000b01c33b7e$bc37fdd0$0000fea9@sandos> From: =?iso-8859-1?Q?John_B=E4ckstrand?= To: Date: Thu, 26 Jun 2003 03:03:20 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: Mbuf Clusters on 4.8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jun 2003 01:03:17 -0000 Ive been googling quite a bit now for problems with running out of mbuf clusters. Im basically sending a 30k datachunk down 1000-4000 connections, but 1000 is more than enough to quickly fill upp 8192 mbuf clusters. I also tried setting maximum amount of mbuf clusters to 65536, but that only made the box hard-wire 86MB of 96MB RAM, making it just as unsuable as a dead machine. Of course, when the machine runs out of mbuf clusters, it dies. I also found this with google: "Finally, the fact that FreeBSD 3.x panics when it runs out of mbuf clusters is a well-known problem. The solution is to not let it run out of mbuf clusters by configuring a sufficient number for them." >From this it sounds as it is a problem that should be fixed, but it obviously isnt in 4.8. Is this behaviour now considered acceptable? And if so, doesnt this make FreeBSD extremely easy to kill using a simple DOS-attack? Is this "fixed" in any way on 5.1? --- John Bäckstrand