From owner-freebsd-current  Mon Mar 20 13:46:23 1995
Return-Path: current-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA07272 for current-outgoing; Mon, 20 Mar 1995 13:46:23 -0800
Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA07254 for <current@freebsd.org>; Mon, 20 Mar 1995 13:46:16 -0800
Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id NAA26983; Mon, 20 Mar 1995 13:46:03 -0800
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id NAA02245; Mon, 20 Mar 1995 13:46:02 -0800
Message-Id: <199503202146.NAA02245@corbin.Root.COM>
X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol
To: terry@cs.weber.edu (Terry Lambert)
cc: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman), current@FreeBSD.org
Subject: Re: Why does kern_lkm.c use kmem_alloc()? 
In-reply-to: Your message of "Mon, 20 Mar 95 14:20:56 MST."
             <9503202120.AA03028@cs.weber.edu> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Mon, 20 Mar 1995 13:46:01 -0800
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.

   Contiguous? You mean _physically_ contiguous memory? kmem_alloc() has never
tried to return that.

-DG