From owner-freebsd-hackers  Thu Feb 27 19:43:07 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA11398
          for hackers-outgoing; Thu, 27 Feb 1997 19:43:07 -0800 (PST)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA11392
          for <hackers@FreeBSD.ORG>; Thu, 27 Feb 1997 19:43:04 -0800 (PST)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
          by alpo.whistle.com (8.8.5/8.8.4) with SMTP
	  id TAA22712; Thu, 27 Feb 1997 19:01:12 -0800 (PST)
Message-ID: <331649F3.167EB0E7@whistle.com>
Date: Thu, 27 Feb 1997 18:58:59 -0800
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: dg@root.com
CC: Joseph Thomas <jpt@msc.edu>, hackers@FreeBSD.ORG
Subject: Re: Assumptions about kmem_malloc()...
References: <199702280129.RAA05746@root.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

David Greenman wrote:
> 
> >       o Other then contigmalloc(), is there a way to malloc contiguous
> >physical memory greater then one page?
> 
>    No; we created vm_page_alloc_contig/contigmalloc specifically for this
> purpose, and it's the only mechanism that exists to do this.
> 
> >               The driver waits to malloc memory until microcode is
> >       downloaded to the NIC (Fore PCA200E). 

someone was saying they already had a driver for this..

you might check on the freebsd-atm list


also, I wonder if we couldn't make a memory de-fragger that could be
kicked off by a process when it knows it's going to need some
contiguous space....