From owner-freebsd-current Mon Jan 18 14:22:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22775 for freebsd-current-outgoing; Mon, 18 Jan 1999 14:22:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22626 for ; Mon, 18 Jan 1999 14:22:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA19128; Mon, 18 Jan 1999 14:18:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901182218.OAA19128@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: Mike Smith , Julian Elischer , Matthew Dillon , current@FreeBSD.ORG Subject: Re: Re2: kernel malloc and M_CANWAIT In-reply-to: Your message of "Mon, 18 Jan 1999 16:47:27 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Jan 1999 14:18:17 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Because you shouldn't panic unless there's no alternative. Panicking > > on resource starvation is just totally lame. > > Ahem: > uipc_mbuf.c: unmodified, readonly: line 268 of 945 [28%] > panic("Out of mbuf clusters"); > uipc_mbuf.c: unmodified, readonly: line 296 of 945 [31%] > panic("Out of mbuf clusters"); > And if the max number of mbuf clusters is{, to become} a sysctl, shouldn't > these just be informative printf()s or something? See my earlier comment about work in progress on just exactly this. Pay attention. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message