From owner-freebsd-hackers Fri Jul 28 18:53: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 3CFDC37BB28 for ; Fri, 28 Jul 2000 18:52:41 -0700 (PDT) (envelope-from darius@guppy.dons.net.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id LAA50611; Sat, 29 Jul 2000 11:22:16 +0930 (CST) (envelope-from darius@guppy.dons.net.au) Received: (from darius@localhost) by guppy.dons.net.au (8.9.3/8.9.3) id LAA03793; Sat, 29 Jul 2000 11:22:06 +0930 (CST) (envelope-from darius) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <006301bff8fc$98795a00$0100000a@waldron.house> Date: Sat, 29 Jul 2000 11:22:06 +0930 (CST) From: "Daniel O'Connor" To: Isaac Waldron Subject: Re: Best way to lock malloc'd memory in kernel Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Jul-00 Isaac Waldron wrote: > Thanks! I didn't realize that, I suppose I should have RTFM'ed a bit more > before asking, but I just kind of assumed (we all know what that does) that > memory malloc'd in kernel mode was pageable. I guess I should ask whether Yes, well it would be nice to have some kernel memory pageable but.. > that holds true for kernel modules as well, because that's what I'm actually > writing. Yes, writing a module is no different than writing for static kernel code. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message