From owner-freebsd-hackers Fri Jul 28 18:31: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from unix.worldpath.net (unix.worldpath.net [206.152.180.10]) by hub.freebsd.org (Postfix) with ESMTP id E8D6737B670 for ; Fri, 28 Jul 2000 18:31:00 -0700 (PDT) (envelope-from waldroni@lr.net) Received: from camry ([208.133.220.153]) by unix.worldpath.net (8.9.3/8.9.3(WPI)) with SMTP id VAA24140 for ; Fri, 28 Jul 2000 21:30:58 -0400 (EDT) Message-ID: <006301bff8fc$98795a00$0100000a@waldron.house> Reply-To: "Isaac Waldron" From: "Isaac Waldron" To: References: Subject: Re: Best way to lock malloc'd memory in kernel Date: Fri, 28 Jul 2000 21:30:35 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 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. Thanks again, Isaac Waldron waldroni at lr dot net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message