From owner-freebsd-hackers Fri Jun 11 5:55:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id 2C0C814F0E for ; Fri, 11 Jun 1999 05:55:13 -0700 (PDT) (envelope-from roger@cs.strath.ac.uk) Received: from cs.strath.ac.uk (scary.dmem.strath.ac.uk [130.159.202.5]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id NAA01783 Fri, 11 Jun 1999 13:55:03 +0100 (BST) Message-ID: <37610728.7640C257@cs.strath.ac.uk> Date: Fri, 11 Jun 1999 13:55:04 +0100 From: Roger Hardiman Organization: Strathclyde University X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org, new-bus-arch@bostonradio.org Subject: KLD bt848 driver and vm_page_alloc_contig Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Is there a way to fix vm_page_alloc_contig() so it can allocate contiguous memory once userland has got up and running and memory has been fragmented/filled. I've finished porting the bt848 driver to the newbus framework. You can load/unload the driver with kldload and kldunload. Great for testing. Load test, unload, recompile, repeat... However, the driver needs about 2 meg of contiguous memory allocating. It must be contiguous as hardware writes directly into it. (same applies to the meteor driver and probably some of the sound card drivers) I can start X, and load the 'bktr' driver. But once I run a few apps, and memory fills up, I can no longer allocate the contiguous memory required. Clearly the kernel would need to swap out user process memory pages to make room for the contigous memory vm_page_alloc_contig() requires. Can this be done? Bye Roger -- Roger Hardiman Strathclyde Uni Telepresence Research Group, Glasgow, Scotland. http://telepresence.dmem.strath.ac.uk 0141 548 2897 roger@cs.strath.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message