From owner-freebsd-current  Mon Mar 20 13:27:22 1995
Return-Path: current-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA06135 for current-outgoing; Mon, 20 Mar 1995 13:27:22 -0800
Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA06121 for <current@FreeBSD.org>; Mon, 20 Mar 1995 13:27:15 -0800
Received: by cs.weber.edu (4.1/SMI-4.1.1)
	id AA03028; Mon, 20 Mar 95 14:20:57 MST
From: terry@cs.weber.edu (Terry Lambert)
Message-Id: <9503202120.AA03028@cs.weber.edu>
Subject: Re: Why does kern_lkm.c use kmem_alloc()?
To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman)
Date: Mon, 20 Mar 95 14:20:56 MST
Cc: current@FreeBSD.org
In-Reply-To: <9503201937.AA27595@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Mar 20, 95 02:37:27 pm
X-Mailer: ELM [version 2.4dev PL52]
Sender: current-owner@FreeBSD.org
Precedence: bulk

> Can anybody explain why kern_lkm.c uses kmem_alloc() to allocate
> memory rather than malloc()?  Is it just because of the kernel
> malloc()'s size limit?  (I'd really like for it to use malloc so that
> I could tell how much memory is occupied by LKMs from `vmstat -m'.)

Contiguous driver buffer space for DMA target.

It can use plain malloc for the structures for the list of allocated
devices, etc. with no trouble, however.


					Terry Lambert
					terry@cs.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.