From owner-freebsd-hackers Mon Jul 14 16:45:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA22131 for hackers-outgoing; Mon, 14 Jul 1997 16:45:19 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22120 for ; Mon, 14 Jul 1997 16:45:11 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.5/8.8.5) id SAA00363; Mon, 14 Jul 1997 18:45:05 -0500 (EST) From: "John S. Dyson" Message-Id: <199707142345.SAA00363@dyson.iquest.net> Subject: Re: vm_page_alloc_contig again In-Reply-To: <199707142301.AA11182@zephyr.isi.edu> from Anne Hutton at "Jul 14, 97 04:00:04 pm" To: hutton@ISI.EDU Date: Mon, 14 Jul 1997 18:45:04 -0500 (EST) Cc: hackers@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > Hi, > > 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? > vm_page_alloc_contig works best before the system is fully up. It is used to allocate medium sized contiguous chunks at bootup time. > > 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. > We don't have a very reliable method for allocating large amounts of contiguous memory in the kernel. If you don't need contiguous memory, then there are other ways to allocate virtually contiguous memory. The simplest is kernel malloc. The memory will be virtually contiguous, but will not likely be physically contiguous. I don't/can't keep up with all questions... What exactly are you trying to do? John dyson@freebsd.org (Core)