From owner-freebsd-hackers Sat Sep 21 1: 4:31 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD8AE37B401 for ; Sat, 21 Sep 2002 01:04:29 -0700 (PDT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6DA343E6E for ; Sat, 21 Sep 2002 01:04:28 -0700 (PDT) (envelope-from phoenix@minion.de) Received: from [212.227.126.160] (helo=mrelayng0.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 17sfFW-00066Y-00; Sat, 21 Sep 2002 10:04:22 +0200 Received: from [80.144.35.136] (helo=chronos) by mrelayng0.kundenserver.de with asmtp (Exim 3.35 #1) id 17sfFW-0005sk-00; Sat, 21 Sep 2002 10:04:22 +0200 Received: from phoenix by chronos with local (Exim 3.35 #1 (Debian)) id 17scDZ-0001pD-00; Sat, 21 Sep 2002 06:50:09 +0200 Date: Sat, 21 Sep 2002 06:50:09 +0200 From: Christian Zander To: "M. Warner Losh" Cc: dominic_marks@btinternet.com, jamie@jamiesdomain.org.uk, freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel - Modules and Compiled in Message-ID: <20020921065009.S4788@chronos> Reply-To: Christian Zander References: <001001c25d36$a3672be0$83bf83d5@BONG> <20020915203835.GA3497@gallium> <20020921.004207.103236464.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020921.004207.103236464.imp@bsdimp.com> User-Agent: Mutt/1.3.22.1i X-Operating-System: GNU/Linux [2.4.19][i686] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Sep 21, 2002 at 12:42:07AM -0600, M. Warner Losh wrote: > > this is false. If you load the module from the boot loader there > is no difference between that and having it be actually compiled > into the kernel in terms of resource allocation. > > However, this is true if you intend to load the drivers at some > time later than boot. > Maybe it helps to get an idea of what memory allocation sizes we are talking about for the NVIDIA driver. For every single OpenGL client in the system memory case (no AGP), the resource manager has to allocate ~1MB (in multiple chunks; 258, 1, 8 pages). > Actually, this issues get gross in a hurry, which is why no one > has done it. :-( > There is a similar interface on Linux, the bigphys patch; it is really only useful to set aside larger chunks of contiguous physical memory for special-case drivers rather than for daily life. Allocating dynamically from a static block of memory set aside a boot time would quickly grow into a major pain for this specific driver due to the numerous smaller allocations. This works well enough for AGP memory since all AGP allocations are much larger (258, 2304 pages) and sized in multiples of 1MB. Even in the AGP memory case, several pages of DMA memory need to be allocated from general system memory. -- christian zander zander@minion.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message