From owner-freebsd-hackers  Mon Jul 14 16:55:38 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA22742
          for hackers-outgoing; Mon, 14 Jul 1997 16:55:38 -0700 (PDT)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22737
          for <hackers@FreeBSD.ORG>; Mon, 14 Jul 1997 16:55:35 -0700 (PDT)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id QAA11304;
	Mon, 14 Jul 1997 16:56:05 -0700 (PDT)
Message-Id: <199707142356.QAA11304@implode.root.com>
To: hutton@ISI.EDU
cc: hackers@FreeBSD.ORG
Subject: Re: vm_page_alloc_contig again 
In-reply-to: Your message of "Mon, 14 Jul 1997 16:00:04 PDT."
             <199707142301.AA11182@zephyr.isi.edu> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Mon, 14 Jul 1997 16:56:04 -0700
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>I was hoping for a response from someone on the core team about the 
>functionality of vm_page_alloc_contig...does it do what it is supposed to do 
>in version 3.0? 
>
>One of the last emails I see on it in the hackers archive suggest it doesn't 
>work as intended - see the included email. The comments in cvsweb on vm 
>revisions also seem unclear as to the status of vm_page_contig_alloc. 

   vm_page_alloc_contig works fine, but it must be used at startup time as
it has no mechanism for doing paging and thus can fail if memory becomes
too fragmented.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project