From owner-freebsd-current Mon Jan 18 13:09:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11866 for freebsd-current-outgoing; Mon, 18 Jan 1999 13:09:17 -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 NAA11861 for ; Mon, 18 Jan 1999 13:09:14 -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 NAA18722; Mon, 18 Jan 1999 13:05:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901182105.NAA18722@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: Matthew Dillon , Brian Feldman , Mike Smith , current@FreeBSD.ORG Subject: Re: kernel malloc and M_CANWAIT In-reply-to: Your message of "Mon, 18 Jan 1999 12:57:02 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Jan 1999 13:05:24 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > So malloc() will generally not return NULL even in low memory situations > > unless the KVM map fills up, which isn't supposed to happen but can in > > certain severe circumstances. Callers should therefore check for NULL. > > why not just put it in a loop and block on lbolt? > (or call panic) Because you shouldn't panic unless there's no alternative. Panicking on resource starvation is just totally lame. -- \\ 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