From owner-freebsd-arch Fri Feb 23 9:44:14 2001 Delivered-To: freebsd-arch@freebsd.org Received: from sandman.sandgate.com (sandman.sandgate.com [38.161.139.2]) by hub.freebsd.org (Postfix) with ESMTP id DC48F37B4EC for ; Fri, 23 Feb 2001 09:44:07 -0800 (PST) (envelope-from wainer@sandgate.com) Received: from vectra (sandman.sandgate.com [38.161.139.2]) by sandman.sandgate.com (8.11.1/8.11.1) with SMTP id f1NHi2Q06417; Fri, 23 Feb 2001 12:44:03 -0500 (EST) From: "Sue Wainer" To: "Freebsd-Arch" Cc: "Jon Wells" Subject: Memory Alloation from kernel loadable driver Date: Fri, 23 Feb 2001 12:44:02 -0500 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0002_01C09D96.4CAC0110" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0002_01C09D96.4CAC0110 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit I have a pci driver which is loaded using kldload. It is allocating a no. of pages by calling vm_page_alloc_contig. This convention is used by other pci drivers, though not necessarily loadable ones. On machines without much memory, or ones with more memory but having done compilations prior to kldloading, contigmalloc1 gets stuck in a continuous loop looping from the first "goto again1." There is a comment above configmalloc1 which might imply that this contiguous allocation does not work after initialization. For locked-down memory, what allocation routines should loadable drivers be calling? Is there any source of documentation of memory allocation which could be of value? Thanks. Sue Wainer wainer@sandgate.com ------=_NextPart_000_0002_01C09D96.4CAC0110 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I have a pci driver = which is=20 loaded using kldload. It is allocating a no. of pages by calling=20 vm_page_alloc_contig.
This convention is = used by=20 other pci drivers, though not necessarily loadable = ones.
 
On machines without = much=20 memory, or ones with more memory but having done compilations prior to=20 kldloading,
contigmalloc1 gets = stuck in a=20 continuous loop looping from the first "goto again1." There is a=20 comment
above configmalloc1 = which might=20 imply that this contiguous allocation does not work after=20 initialization.
 
For locked-down = memory, what=20 allocation routines should loadable drivers be calling? Is = there any=20 source of
documentation of = memory=20 allocation which could be of value?
 
Thanks.
 
Sue = Wainer
wainer@sandgate.com <= /FONT>
 
 
------=_NextPart_000_0002_01C09D96.4CAC0110-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message