From owner-freebsd-hackers Thu Oct 9 20:50:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA20364 for hackers-outgoing; Thu, 9 Oct 1997 20:50:03 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA20334 for ; Thu, 9 Oct 1997 20:49:57 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id NAA00721; Fri, 10 Oct 1997 13:17:04 +0930 (CST) Message-Id: <199710100347.NAA00721@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: mdean cc: freebsd-hackers@freebsd.org Subject: Re: free() in device drivers In-reply-to: Your message of "Thu, 09 Oct 1997 20:11:25 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Oct 1997 13:17:04 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > If I do a malloc (p, M_DEVBUF, M_NOWAIT); > > then find a problem in my attach routine, can I do a free(p, M_DEVBUF) to > recover that memory? No. In fact, the memory will remain allocated over even cold reboots, and you will have to open the system, identify which SIMM the memory was allocated on, remove it and wrap it in aluminium foil for half an hour to discharge the DRAM capacitors and clear the allocation. mike