From owner-freebsd-hackers  Wed Nov  4 10:06:49 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA04139
          for freebsd-hackers-outgoing; Wed, 4 Nov 1998 10:06:49 -0800 (PST)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04132
          for <freebsd-hackers@FreeBSD.ORG>; Wed, 4 Nov 1998 10:06:47 -0800 (PST)
          (envelope-from xroot@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id KAA01814;
	Wed, 4 Nov 1998 10:07:46 -0800 (PST)
Message-Id: <199811041807.KAA01814@implode.root.com>
To: Reinier Bezuidenhout <Reinier.Bezuidenhout@KryptoKom.DE>
cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Malloc in the kernel 
In-reply-to: Your message of "Wed, 04 Nov 1998 18:47:55 +0100."
             <199811041747.SAA05132@borg.kryptokom.de> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Wed, 04 Nov 1998 10:07:46 -0800
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>If I want to malloc really large space in the kernel, say from
>2k up to 1M or maybe more .... wat parameter should 'n 
>give to malloc ??
>
> malloc(1000, ????, M_WAITOK);
>
>? M_DEVBUF 
>
>if it is possible :)

   None of the above since allocations that large will likely be fatal if
the kmem_map is even a little fragmented. You could do it at system startup
time, however. Anyway, the type is not important.

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message