From owner-freebsd-hackers Fri Jul 28 19:22:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 933F437BB75 for ; Fri, 28 Jul 2000 19:22:12 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e6T2MAS17433; Fri, 28 Jul 2000 19:22:10 -0700 (PDT) Date: Fri, 28 Jul 2000 19:22:10 -0700 From: Alfred Perlstein To: Isaac Waldron Cc: hackers@FreeBSD.ORG Subject: Re: Best way to lock malloc'd memory in kernel Message-ID: <20000728192210.M17222@fw.wintelcom.net> References: <006301bff8fc$98795a00$0100000a@waldron.house> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <006301bff8fc$98795a00$0100000a@waldron.house>; from waldroni@lr.net on Fri, Jul 28, 2000 at 09:30:35PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Isaac Waldron [000728 18:31] wrote: > > > > I'm writing a device driver for plex86 (the FreeMWare virtual machine > > > software), and have a buffer that needs to be non-pageable. It was > malloc'd > > > with the malloc(size, type, flags) kernel malloc function. What's the > best > > > way to make this memory unpageable? > > > > No kernel memory is pageable so it doesn't matter :) > > > > 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 > that holds true for kernel modules as well, because that's what I'm actually > writing. Just a note that you may have to use 'contigmalloc' if you need the memory to be physically contiguous. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message