From owner-freebsd-current Tue Aug 29 12:24:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom0-080.telepath.com [216.14.0.80]) by hub.freebsd.org (Postfix) with SMTP id 7A62C37B43E for ; Tue, 29 Aug 2000 12:24:47 -0700 (PDT) Received: (qmail 25612 invoked by uid 100); 29 Aug 2000 19:24:06 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14764.3542.322382.773438@guru.mired.org> Date: Tue, 29 Aug 2000 14:24:06 -0500 (CDT) To: obrien@FreeBSD.ORG Cc: Brooks Davis , Greg Lehey , Warner Losh , Maxim Sobolev , Donn Miller , current@FreeBSD.ORG Subject: Re: hints static wiring In-Reply-To: <20000829103024.A5567@dragon.nuxi.com> References: <20000827184037.A22500@Odin.AC.HMC.Edu> <14762.8323.382969.782508@guru.mired.org> <39AA3882.914FC0A0@cvzoom.net> <14762.14890.276820.183791@guru.mired.org> <39AA5DC6.8D73081B@FreeBSD.org> <14762.24829.363032.115605@guru.mired.org> <39AA6699.41E12730@FreeBSD.org> <14762.26659.335.344828@guru.mired.org> <20000829102526.A11422@wantadilla.lemis.com> <20000828182921.A31041@Odin.AC.HMC.Edu> <20000829103024.A5567@dragon.nuxi.com> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien writes: > On Mon, Aug 28, 2000 at 06:29:21PM -0700, Brooks Davis wrote: > > On Tue, Aug 29, 2000 at 10:25:26AM +0930, Greg Lehey wrote: > > > At the very least, there appears to be confusion about how to use the > > > 2. You must have a /boot/device.hints file, and it must contain at > > > least some entries. > > This is more correct. The new world order says that hints are not in the > > kernel, instead they are loaded by the loader at boot time. > I would quite to so far. I know many that will continue to compile > static hints into their kernels until that ability is removed. I suspect I'm going to be one of those people, but let's ask the next question. How do the two approaches compare from a performance standpoint? I figure having them wired in means you avoid parsing them at boot time, which should be faster. How smart is the code about devices with hints that aren't configured in the kernel? Do both methods throw out such data, or do both save it? Basically, which will provide the smallest running kernel, and if it's the same, which will boot fastest? Thanx,